Why the Product Owner needs to negotiateIf your team is using "INVEST" as part of your Definition of Ready, backlog items should be negotiable - but why should they be negotiable if you don't want to negotiate?
In a recent post, I discussed what "user stories" actually mean, so I'll skip on full repetition.
When you work with stories, then you're talking about someone who has a problem and an interest in having a solution. On purpose, we refrain from equating problem and solution for a while - because if people knew the best solution for their problem, they probably wouldn't have it anymore.
Negotiate the approachThere is always more than one way to deal with a problem. Common strategies are:
- Accept (do nothing)
- Avoid (create a work-around)
- Ameliorate (reduce the impact)
- Cover (make it invisible to the user)
- Resolve (eliminate it once for all)
Descending from 1-5:
- User pain decreases
- User effort decreases
- Delay increases
- Engineering complexity increases
- Engineering effort increases
Negotiate a compromize
Negotiate the solution
The PO, central negotiator
- Separate people and problems
- Focus on shared interests
- Create options
- Use objective criteria