Innovation Trends

A Modern Take on the Agile Manifesto

illustrations-for-agile-manifesto-01When the Agile Manifesto was published in 2001 there was no such thing as an iPhone, Google had a total of 4 products and Wikipedia was brand new. The way we work and communicate via technology has shifted massively and yet our interpretation of the manifesto hasn’t changed in over a decade.

The manifesto has been great for engineers, but has presented some real challenges for business analysts and other stakeholders in the application development process. The problems that the manifesto addressed all those years ago still exist. Many of these problems have been amplified by drastic changes in the product delivery landscape:

  • Time to market has dramatically shortened and complexity has increased
  • Information is available and abundant but continues to go undocumented or get lost
  • Communication gaps widen due to geographically dispersed teams and department differences
  • Customer needs require iterative communication yet continue to go unmet

On Wednesday, April 23 at 10:00 AM PDT I’ll be presenting a webinar sharing my perspective on why and how I think we should reconsider the Agile Manifesto. I’ll cover the four key tenets of Agile and provide my recommendations for modernizing your approach based on new technologies and mindsets around collaboration, social integration and complex systems engineering to find balance for everyone involved. Please join me, register for the webinar, and share your thoughts about taking a modern approach to the Agile Manifesto by leaving a comment or connecting with me on Twitter.

I also recommend taking a look at Jama’s Modern Product Delivery page to learn more about the biggest challenges facing companies bringing products to market. You’ll find a Forrester Consulting report, an infographic and more.