Grooming in
MANDAROON
Part 2 – Middle 30%
(Mitigating Risk)
In Part 2, backlog prioritization will begin to flip. With the MVP built, sequential necessity will be less important. Risk mitigation will take precedence, eventually making way for as much attention to business value (BV) as possible.
2a. Info Panel Notes & Analytics
Here, some of the more technically challenging features are prioritized.
[slide-anything id=”1863″]
2b. Collaborator Feature
The app’s business value is limited without the ability to collaborate, so it will provide BV. Implementing collaboration functionality will be a complex task, so RU is involved. It must also exist before other key features can be introduced, so SN is at play.
[slide-anything id=”1867″]
2c. Collaborator Notes & Ratings
With collaborator linkages in place, we can now start adding collaboration-based features. In Part 2, where the emphasis is on mitigating risk on items with significant BV, we begin with collaborator rating … and the infrastructure necessary to get us there (namely, collaborator notes).
[slide-anything id=”1873″]
End of Part 2
This concludes Part 2, the middle 30% of items in the backlog. These examples clearly represent far fewer than 30% of app stories; they are given just as examples of what types of stories would be handled at this phase. As expected, most stories were included here to mitigate the risk/uncertainty (RU) they represent. Those without RU as their rationale were included because the app architecture could not hold the RU features without them (e.g., you can’t rate collaborators’ notes without first having a collaborators’ notes page).