by Nathan Wilson | June 13, 2013 | Comments Off on Apocalypse Now?
Apocalypse is often thought of as the end of the world in popular movies and literature. This is not it’s only meaning. Apocalypse is the Greek work for uncovering or revealing what has been hidden. In ancient texts including the bible, it often referrers to the end of one age and the beginning of the next.
To carry this metaphor to software development I think that I have seen at least three horsemen of the apocalypse in the last year:
- The Microsoft VisualStudio 2012 launch event where Microsoft talked about agile as much as their products.
- Gartner publishes “The End of the Waterfall as We Know It” (subscription required) declaring that the long term waterfall project model does not work.
- IBM’s Innovate conference this month where the focus was on DevOps which they defined as continuous development and delivery.
Agile is now mainstream and it has shifted from a grassroots revolution of developers to a management driven push to make IT departments more responsive. Those of us who have been involved in agile for a while can be forgiven for wondering if agile can survive the shift.
The way forward is to leverage this high level attention to push for the changes outside of the development teams that agile requires. Businesses know that they need IT to change, now is the time to explain how small short projects and better engagement between development and their customers can enable the responsiveness that the business needs.
View Free, Relevant Gartner Research
Gartner's research helps you cut through the complexity and deliver the knowledge you need to make the right decisions quickly, and with confidence.Read Free Gartner Research
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.