Lean and Agile are like a fast car, it helps you iterate faster, but it does not give you a clear vision and strategy.
Most companies run into Product Diceases:
- Strategic Swelling: The product tries to do too much for too many users – unfocused efforts, weak value proposition.
- Obsessive Sales Disorder (OSD): Features delivered for individual customers – fragmented product, distracted engineers.
- Narcissus Complex: Looking inwards and focusing on our own needs – disconnected from customer needs.
- Hypermetricemia: Obsession with metrics and analytics – incremental product improvement, stuck in local maxima.
And have Digital Pollution: Collateral damage from our products.
A good vision is not a short slogan or BHAG. Your vision should articulate:
- Who: Whose world are you changing?
- What: What does their world look like today?
- Why: Why does their world need to change?
- When: When will you know that you’ve arrived?
- How: How are you going to change it for them?
Product Strategy (RDCL):
- Real Pain Points – What do businesses need in the oasis?
- Design – What does our solution look like?
- Capabilities – How do we enable those capabilities?
- Logistics – How do we deliver it?
Radical Product helps you define and communicate what you are building and why.
Lean and Agile help you execute, learn and iterate under uncertainty.
- Lean Canvas
- Impact Mapping
- Product Vision Board
- Story Mapping + MoSCoW
A nice article on how to better balance your backlog by using backlog quadrants can be found here: https://robertvanlieshout.medium.com/how-to-better-balance-your-backlog-56ef8d099bcd
To conduct the workshop, follow these steps:
- In 30-minute cycles,
- The PO presents the next PBIs that aren’t Ready to the team. (up to 5 minutes)
- The Development Team decomposes into sub-teams of 3-4 people.
- Each sub-team selects one of the next PBIs and gets it Ready. (15-20 minutes)
- Use User Stories, 3 Cs, INVEST, your Definition of Ready, etc. to guide you.
- If Readiness is blocked by an impediment outside the Scrum team, the sub-team makes a concrete plan for what they will do to get the PBI Ready before the next Sprint Planning or Backlog Refinement meeting.
- Merge back into whole group, the full Scrum team.
- Sub-teams present their work to the whole group. (5-10 minutes)
- Take a break (5 minutes)
Read the original article here: https://kasperowski.com/how-to-a-great-product-backlog-refinement-workshop/
Scrum is a practical framework to build products, provided you identify in advance what to build. But even after a successful product discovery phase, you may struggle to make the right thing in the right way if your product backlog is not up to the job. Garbage in, garbage out – as the saying goes. The following article points at 28 of the most common product backlog anti-patterns – including the product backlog refinement process – that limit your Scrum team’s success.
Read the complete article here: https://age-of-product.com/28-product-backlog-anti-patterns/