- What is devops? What is continuous delivery?
- Challenges for devops
- Misaligned organizations
- Collaboration between development and operations
- Holistic software systems
- Poly-skilled team members
- Cross-functional teams
- Benefits of the devops approach
- Learning about problems earlier
- Less-complex problems
- Less time fixing problems
- Business value
- Deliver features more often
- More-stable systems
- Software is always ready to release
- How devops and continuous delivery work
- Change organizational structure
- Make processes continuous
- Continually improve
- Tools and components
- Continuous integration
- Infrastructure automation
- Static analysis
- Tool catalog
- The future of devops and continuous delivery
- Key takeaways
- About Paul Duvall
- About GigaOM Pro
How is it that companies like Netflix, Amazon, Etsy, and Facebook regularly deliver new features to their users (in some cases, several times per day) while other companies must wait months or more to release software updates? The answer is that the companies listed here, like many others, have changed how they deliver software by dismantling the traditional silos that stifle collaboration and progress. Their
development and operations teams are working together and learning from each other through what is now know as “devops,” an industry buzzword that arose to describe a philosophy that many progressive companies and startups had long been practicing.
Some of these companies probably never called their “devops.” They were just working collaboratively to meet business demand. As they did, they began considering leaner and more-innovative approaches for releasing software more quickly and more often.
This report describes the nascent topics of devops and continuous delivery while enumerating the challenges IT organizations are seeking to remedy by adopting these approaches. Aimed at technology executives and directors and those responsible for delivering features and stable software systems to their users, the report covers the benefits of a devops mindset, which encourages communication and collaboration by obliterating the silos that impede projects. Additionally, it cites the value provided to the business itself, how the approach works, and some of the components and tools that are used on projects to deliver new features to users in a stable environment. Finally, it touches on the concept that the future will involve less friction and more value from tools and infrastructure that support this approach.