arlene trimbleAssistant IT Director| Local GovernmentAlamo, Ca, United States
How do you demonstrate or show value in your agile projects? What tools do you use? Saving Changes...
Sort By:
Lawrence CooperCreator, Lean-Agile Strategy| AdaptiveOrg Inc.Kanata, Ontario, Canada
Interesting way to phrase the question. Every project is supposed to deliver value otherwise it should not be done. Applying agile thinking allows us to deliver demonstrable value sooner by delivering the highest value things first in short iterations/sprints.
If the intended question is "what is the value of using Agile in your projects" then the answer to that one is that it increases transparency, visibility, adaptability, and significantly reduces or eliminates many forms of project risk as compared to traditional approaches.
There are numerous agile practices, frameworks and techniques that need to understood before worrying about software tools that support agile portfolios and projects (if that was the second part of your question). Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Value is a subjective matter. Stakeholder analysis (full process) is a must in this case. That is the key to demostrate value. In the company I am working we are using a framework that was created by me. But you can see MoV or MoP frameworks that can be used as a point of reference just in case those frameworks do not fit for your needs. Remember: value is a subjective matter that can be transform into objective once. Saving Changes...
Lawrence CooperCreator, Lean-Agile Strategy| AdaptiveOrg Inc.Kanata, Ontario, Canada
Absolutely value is subjective, or as Simon Sinek said in Start with Why "Money is a perfectly legitimate measurement of goods sold or services rendered. But it is no calculation of value...Value is a feeling, not a calculation. It is perception.”
That is the form of value to which I am referring. MoV has a good start to that but most of its suggested techniques are focused on the monetary definition. Outcomes mapping has its roots in medicine with Florence Nightingale and focuses on the other kind of value.
Nightingale was arguably the first person who figured out that you need to start with framing the result you want to achieve (the why) to determine what you should do, how you should do it, when you should it, and where you should do it. That`s the essence of outcomes mapping - which by the way was left out of MoV as a possible technique.
You should always start with why you want to do something as it will lead you to articulate the outcomes that would be achieved if you did. From there you can identify the benefits that would accrue if those outcomes were achieved. Likewise you can also sort out the order in which you need to deliver and which projects you need to stand up which defines the portfolio you need to execute.
This value focus means that not all results (outcomes) and benefits have to be realized for value to have to be perceived as having been delivered. Projects create outputs - how they are used create outcomes. We often confuse the two. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Fully agree with @Lawrence. That is because I have used MoV or MoP with modifications. For me (and for some researchers that have been worked on this from years in some places like the MIT) people who think that something valuable is related to money are missing a lot. But I mentioned, if for some stakeholders that is the case (value is related to money) then that is value. Saving Changes...
Lawrence CooperCreator, Lean-Agile Strategy| AdaptiveOrg Inc.Kanata, Ontario, Canada
Sergio great to hear from like-minded people. BTW I was the Mentor for PRINCE2 Agile and am currently writing a paper for AXELOS on the effects of agile thinking on their PPM Suite of Guidance which of course includes MoV and MoP. Saving Changes...
