Oct 11, 2018 1:58 PM
Replying to Joseph Toth
...
Lenka -
I have actually been having this discussion on my current assignment as well.
Regardless of an AGILE --or-- WATERFALL project delivery, my advice would be to make sure that you had a clearly defined scope that itemized what was included in the overall set of project deliverables. Your question regarding how to "...ensure that the deliverables will create benefits as intended? " is what I've named " value realization ". This typically is NOT something generally covered within the scope of a project. Consider the construction of a home. You will be able to prove to the new homeowner that HVAC has been properly installed & tested, however, you will not be around to help vet whether or not this HW installation will deliver the expense savings as was advertised. "Why...?" Because that aspect of the project was NOT in the contract / plan for delivery. Likewise, if that type of deliverable was not included in the SCOPE DOCUMENT of your project, as an element of "value realization", would not be something the PROJECT TEAM would end up having to confirm.
"Value realization" within the scope of the project would be something like: " reduction of keystrokes by 50% "; "record imaging error quality reduction of 50%"; # servers retired. This can be measured AND validated thru testing.
"Value realization" outside of the scope of the project would be things like: "revenue generation"; " cost reduction "; "increase of market share"; "efficiency"; "product quality"; adoption rate, etc. Typically, these aspects of project / product value would come from the business side. NOTE: I have not personally experienced ( nor have awareness ) of any organization that attempted to follow-up on this aspect of a proposed scope / business case document.
In summary, the role of the PM in delivering project / product "value" is defined by what is included within the approved scope statement. Inclusion / exclusion of these types of success factors will ultimately come down to the cost associated with the LOE needed from select project team members to hang around LONGER until those metrics are validated. If NOT included within the scope of the project, it is up to the project owner to make sure that what has now been built meets its intended need.
Hope my response helps address your question.....
