Isn't Agile really just a series of small experiments to build experience and learning

The State of Agile Report (Version One) consistently shows that the reason why most agile projects fail,  is lack of experience. Knowledge will only get you so far, we need to apply that knowledge and gain experience through learning.

I’ve had to learn the hard why what works and what doesn’t work through 15 years experience in implementing agile across a number of project sand organisations. Whilst  knowledge is a good foundation, implementing agile and scrum is hard so applying that knowledge and contextualizing it  to the organisation is critical and learning through experimenting is invaluable.
After all , isn’t Agile really just a series of small experiments that incrementally build our learning.
Each Agile project and  its products and processes are is different in terms of goals and contexts. A single
framework or approach  cannot be assumed for all projects or products.  There are no silver bullets to guarantee 100% success, however we can experiment within constraints to reduce risks and learn quickly and ensure we pivot quickly when the dynamics of the context change or we learn through  empiricism that we need to adapt our  thinking .
Developing software for the space shuttle is not the same as to developing software for a video game or mobile app. Agile teams are often exposed to  a diversity of complex problems to solve and this makes an Agile approach to product  development inherently experimental  as we constantly gain experience with each development problem and project. Knowledge emerges through experience in work practices, often being defined  and addressed as issues evolve throughout the project.
Capturing these learnings and actively identifying improvements and applying them to the next Sprint will help build capability and experience , ensure incremental improvements will help  team to learn and leverage successes.

Leave a Reply

Related Posts:

“Netiquette” for online meetings for remote and distributed teams

As with face-2-face meetings, online meetings also have an etiquette (“Netiquette”) to make them effective. One of the 12 principles of the agile manifesto suggests face-to-face is the best option but in today’s world of social distancing and WFH, it is no longer an option.

Here are the guidelines we have found useful for having for online meetings with distributed


22 Stances of a Scrum Master

The Scrum Master doesn’t remove impediments from the team. Their job encompasses 22 wider stances for supporting the team to self-organise to remove impediments themselves, coaching the Product Owner and coaching the wider organisation.


Does agility go out the window when we work remotely?

Many organisations are making guidance on what tools to use for remote teams in response to COVID-19. The situation isn’t a tools problem. This is a people problem – how can people, who are social creatures, successfully work remotely without physical interaction?


Copyright © Zen Ex Machina® and ™ (2019) All rights reserved. ABN 93 153 194 220

search previous next tag category expand menu location phone mail time cart zoom edit close