Devops, Docker, and Sprints
In early 2000 tech companies considered 1 to 2 application deployments per month to be considered agile. They spent time developing tools and processes but not focusing on frequent updates to their customers. Today the speed of development has exponentially increased and to be competitive at any level aligning the development process with business operations all the way through to the customer needs to be a single end-to-end process for everyone.
“We see Docker as a groundbreaking technology that actually enables the DevOps approach to development.”
From an infrastructure perspective, docker allows applications to become a unit of infrastructure and it packages an entire application into containers so that the implementation is greatly simplified. By setting up your development team to work in the context of these containers and deliver code into GitHub repositories for example the mental load to think about deployment processes is offloaded and automated. This greatly increases the productivity of developers so they can remain focused on business logic and deliver new features to your customers.
For startups the cycle of iteration is almost a daily process and changes to both the business model and direction occur rapidly that can negatively impact your team. Deployment pipelines like the above give consistency to your team and a competitive advantage in the agility of your team to deploy new features when the time comes.
Many times startups sacrifice luxuries like a deployment pipeline because it can be time consuming to setup properly and dangling scripts between team members are used to get the job done. But with docker containers this game changing technology really democratizes the way teams operate from large organizations to one man teams.
If you haven’t considered these processes start thinking about them soon because slow iterations can kill your SaaS business.