Stakeholder Traceroute

Stakeholder Traceroute

Posted by richard | June 13, 2016 | Misc, Scrum, Team Services, TFS

I’m always amazed at how difficult and even impossible it can be for stakeholders to get their ideas into some product backlogs.

I’ve started asking teams to run a stakeholder traceroute. In other words, walk me through the process that a user might go through in order to get a good idea (not necessarily a bug) in front of the Product Owner. Here is an example …

tracert

The good news is that I still meet teams who value their stakeholder’s opinions and will give them (near) direct access to their product backlog. Oh, and if you are using Microsoft Team Foundation Server or Team Services, you can add as many stakeholders as you want. Free.

Add a comment

*Please complete all fields correctly

Related Blogs

Posted by richard | March 15, 2017
Create a Professional Scrum process
Visual Studio Team Services' customization capabilities are to a point now where I can write this blog post ... as a rebuttal to any earlier post of my own. Since...
Posted by richard | September 30, 2016
Wassup Team Room?
According to Microsoft's official definition, Team Rooms, like chat rooms, "provide teams with a space to discuss work in progress, ask questions, share status, and clarify issues that arise." Sounds...
Posted by richard | August 15, 2016
Ordering the Product Backlog by ROI
The Scrum Guide says that the Product Owner is the sole person responsible for managing the Product Backlog and that Product Backlog management includes ordering items in the Product Backlog...