Scrumboard Request management

How to distinguish stakeholders' demands and stories

Consistency is key to product adoption.

Users are surrounded with interfaces and only the most consistent, appealing, intuitive and efficient products stay alive.

What is required to reach it?

What you don't need is to flood your backlog with the ideas of your stakeholders, usually in form of solution and potentially orthogonal to your product.

What you need is focus and creativity to identify the underlying problem and then correctly integrate a functional solution into a new feature that will end up in a valuable use case for your users.

What you need is to keep control of what your product does and how it does it.

How? Give a try to request management

How does it work?

1 Only the Product Owner can create stories

That is the first thing: the Product Owner owns the product backlog. So it is his job to define the aspects of the stories and how it answers to a given need.

2 The stakeholders create requests

Requests management allows any of your stakeholders to create demands on your product by logging a request.

3 The Product Owner analyzes the request

That is the whole point: the PO figures out the fundamental need underlying the request and design the most adapted solution in terms of story.

4 The Product Owner manages the request

The answer to a request can be to reject it if it is not a fit in the product, to create one or several stories to implement it or even to link stories already present in the backlog.

5 The requester follows the implementation

Once stories are created, the lifecycle of the request is aligned with the stories linked to it: it is automatically set to "done" when all stories are done.