Put your backlog on steroids

by Alexander Helleboogh & Nelis Boucké at Wemanity

Product backlog

The goal of the product backlog is Aligning stakeholders

Classical product backlog representation ooks like a spreadsheet and is not useful to align different kind of stakeholders

Parabole: House building

• architerctural view is useful for the architect and contractor
• architectural view electric is useful for the architect and the electrician
• 3D sketch is usefull for the final customer and the carpenter

they adapt the communication material (artifacts) to the audience

Software architect

• UML 2.0 Class Diagram: Software dev
• UML 2.0 Interface Diagram: Network
• …

3 concepts

• stakeholder
• concern
• view

Workshop

In team of 4-5 find some stakeholder.

For each stakeholder gather concerns

Finaly pickup one stakeholder you want to work with and propose a vue, think about applicability and advice

Canvas

Canvas to fill in:

canvas

Share

Every group share is view with other groups, moving to one group at a time

Gather sharing and conclusion

• Use less info = more focus
  • less metrics
  • less precise info (not dd/m/yyyy but simply Q1/YYYY, Q2/YYYY ….)
• Automate!!!
  • microsoft solution
  • jira integration with google spreadsheet
• co-create with the stakeholder
  • have a workshop session where the stakeholder build up their dashboard
• Don’t go wild!

the worth (evalution vs value chain graph) & the season view

for more info on worth view see also http://blog.gardeviance.org/2016/09/