What Does a Product Owner even Do?
Many times, this sums up our job.
You get thrown into the left-hand side of pure chaos.
"Now you fix it."
You take chaos as input and are expected to produce compelling software.
How do you even start tackling this?
The SCRUM Guide Does Not Help
The SCRUM guide stays very vague about the Product Owner role.
It does not define the day-to-day tasks and concrete steps necessary to tackle the Product Owner challenges.
In the original SCRUM guide, the Product Owner is even called the 'pig' of the Product Backlog... That does not help.
All SCRUM visualizations also start from the already defined backlog but shy away from HOW this backlog came to be.
This is the real work of the Product Owner.
What steps do you need to take to define this backlog of work?
The Product Process Guides you in the Necessary Steps
The Product Process charts out all the steps you need to take to create a compelling software product.
All your tasks as a Product Owner.
To take Chaos as input and produce a concrete, clear, and well-defined backlog as output.
The Product Process helps you:
-
In understanding where you are now and what to do next;
-
In understanding which Agile/Lean/Product technique to use when;
-
In understanding the gaps in your Product Owner knowledge. And therefore, improve.
Product is Hard... Do Not Get Lost
Translate assumptions into Hypothesis...
Perform (scientifically rigorous) experiments...
