Almost a year ago, TeraThink and Dominion Consulting merged. It seems like a good time to look back on what we have achieved.
Just because this is going to be hard is not a reason to not do it.
While I know it’s a double negative, it turns out it was exactly the right statement to make early and often. We got here relatively innocently – a casual, almost easy, conversation between entrepreneurs about the future of our respective companies. However, accurately predicting how the next year or so would go would have been impossible. We knew the merger was going to be difficult and complicated, sure, but it played out to be much more than that.
The pursuit of a successful merger and integration is an exercise of incredible loads of work, constant distraction, some elation, occasional frustration (insert sarcastic emoji here), and every other emotion in between. I can genuinely state that the process of closing the deal and then integrating these two great companies was both – one of the most difficult, and one of the most rewarding achievements of my career. Recognizing that the merger trend in our industry is not slowing down, we wanted to share a few of our key lessons learned and critical success factors from our experience with this merger.
I’ve been speaking a lot about content services of late. At TeraThink, we are a big believer that good content services are a solid foundation for excellent user experience. This is why I’ve been focused on dispelling some of the hype around content services. One of the reasons I, and TeraThink, have been trying to push past the hype is because we are actively using content services to deliver solutions at scale.
Along the way, we’ve been trying to share some of our lessons. James Fintel shared what we’ve learned about building content services agilely using Kanban. What I wanted to share was some of our lessons on the delivery of content services to a government agency.
Here at Terathink, we are working with a large government agency constructing a content services platform. This platform allows content generated by benefit applications to be shared and reused across the organization’s disparate IT applications. We are doing this through the use of application programming interfaces, or APIs.
Our agile development team manages our work using a Kanban approach, from requirements gathering to the deployment of the API to a production environment. We have honed our use of Kanban to most effectively manage the work required to take a user request to functional reality.