To better understand Agile, let’s look at it’s origins. The Agile Manifesto says:
“Manifesto for Agile Software Development
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.”
I write about:
balancing consulting practices with project management to
imagine perfect outcomes and a perfect journey to get there
that leaves the organization and its people better than we found them.
So, when I read the Agile Manifesto, it says to me that:
- A way to find a perfect journey to a perfect outcome is to focus on the people and how they will work together more than on the processes and tools. The perfect journey is the interactions that produce ideas and results, not a perfectly followed process.
- Working software is more important than comprehensive documentation because a team working one step at a time can better express what it understands via a working product than a complete document. We often complete documents to lock things down and drive out risk. Opportunities for growth come from trying things and learning from them. I think documentation is important, it just has to be in step with product building, not way out in front of it.
- Customer collaboration is more important than contract negotiation because it values seeking what can go right over what can go wrong. Collaboration leads to a commitment to leave an organization better as a result of our efforts. The contract focuses on a commitment to do something for consideration from someone. It protects against risk, but can drive out opportunities it if becomes the focus. The focus needs to be on how people collaborate to improve the organization.
- Responding to change is more important than following a plan because the plan is only a tool that helps you know when things are changing. I think you have to have a plan that covers all the steps in your perfect journey to the perfect outcome. But, you also have to understand that part of a perfect journey is recognizing its unpredictability and learning to respond to discovery.
I think that Agile will be useful applied to portfolio management as well as software development. The PMI standard for portfolio management says that ‘portfolio management is a framework that provides the means to translate the organizational strategy into a portfolio of strategic and operational initiatives. It manages the actualization of those initiatives through the use of organizational resources.’
Agile suggests that the organizational resources are its people. People pursue the organization’s desired strategic (perfect) outcomes by working together and with its customers to discover the best mix of opportunities for improvement. These opportunities are pursued incrementally so that each completed step delivers progress toward the objectives and a clearer understanding of the next step.
I like the mix of Agile, portfolio management, and the other side of risk. Writing about it gets me a little closer to using it productively. Let me know if you think it all fits together.
Thanks for reading.
Copyright 2013, Glenn Briskin and “The Other Side of Risk”