Guides · Prioritize for value
Prioritize work for customer value
GAO's adoption best practice is that work is prioritized to maximize value for the customer: rank-order the highest-value requirements first, so that if funding ends, the customer still benefits from what has already been completed. If the highest-value work is not done first, a stop in funding can leave the customer without the thing they actually needed. This is a field practice about ordering work by value, not a prioritization-tool sales page.
the GAO Agile Assessment Guide is cited here as the September 2020 Exposure Draft, not as a later final edition.
the GAO Agile Assessment Guide, "Best practice: Work is prioritized to maximize value for the customer." "If the highest value requirements are not completed first, the customer may be left without necessary functionality. The best practice is to rank order requirements with those of the highest value being completed first so that if funding ends, the customer will still benefit from the work that has been completed to date." "A user story defines who needs the requirement and why." "The user story’s focus is on the value delivered to the customer, often defines who the customer is, what is being developed for that customer, and why there is a need for the functionality."
How value is set, in the same chapter. "The product owner determines the business value of each user story in consultation with the developers by refining the size, defining the criteria for acceptance, and establishing when the user story will be considered to be done. The value of a user story should be reevaluated based on the current needs of the organization to ensure the greatest return on investment." For the guide's purposes, "user story" describes "a small segment of work that can be completed in a single iteration and is determined by the product owner and developers," even when a program uses other terms such as product backlog items. Each story should have "enough detail to allow developers to estimate the user story’s complexity, but not so much information that there is little room for discussion… around the intent of the user story."
INVEST is the guide's own box of characteristics of a quality user story, spelled on the opened page as Independent, Negotiable, Valuable (or vertical), Estimable, Small, and Testable. Those six words are used here as the guide names them. They are not treated as a GAO-invented law of nature, and the expansions in the box are not reconstructed from memory.
What GAO actually says
Rank-order highest value first. A story says who and why. The product owner determines business value with the developers, via size, acceptance criteria, and a definition of done — and reevaluates value as needs change. Enough detail to estimate, not so much that discussion dies. This page does not invent a house scoring model or a client ROI.
What is a definition of done is the shared-test sibling. Working software in Agile development and What is a minimum viable product are the delivery-test siblings. Each wave ends with a check is the house essay.
The first conversation still ends with a yes, a no, or a better idea, at Start. The dashboard remains "opening soon."
The useful next step is to rank the next increment by value, and to reevaluate that ranking as needs change. If something on this page is wrong, write to us.