Paweล‚ Huryn
Paweล‚ Huryn

@PawelHuryn

13 Tweets Apr 01, 2023
We need to fix #Scrum. It doesn't help PMs enough.
I'm a PSPO III. I've been working in Scrum for 8+ years.
What hurts me the most is that Scrum ignores PM and treats it as a black box.
Here are my 7 ideas on how to fix Scrum: ๐Ÿงต
#productmanagement #prodmgmt #Agile
Before we dive in, some may say, "Scrum is purposely incomplete."
To me, it's like focusing on the engine and ignoring that it is part of the car. There are also other issues.
So here they are:
1. Add Product Vision
You can't lead people without vision. Vision statements are aspirational and communicate concisely where the product hopes to go and what it hopes to achieve in the long term.
Product Vision gives the team purpose.
2. Add Product Strategy
You need a product strategy aligned with the business strategy. Product strategy defines:
- customer segments and their needs\jobs
- value proposition
- differentiators
- tradeoffs
- competitors
- market
- how it will create value for the business
Product Strategy helps you decide what to do next (outcomes) and in which order.
It also provides empowered teams with the strategic context so that they can make better decisions.
3. Add Product Discovery
According to @cagan, "at least half of our ideas are just not going to work" (Inspired). Thus, learning only by delivering results in colossal waste and rework.
We need two streams running in parallel:
- Product Discovery answers when the question "what to build." It results in a validated Product Backlog.
- Product Delivery aims to build it
See "Dual-Track Development" by @jeffpatton jpattonassociates.com
4. Add Release, Measure, and Learn loop
Sprint Review is not enough. You can't reliably measure the outcomes before people start using the product "for real."
Hence, we must release, measure the results, and learn from those measurements.
5. Explicitly mention experiments in the Product Backlog
Experiments are a special type of work that doesn't result in Increments of value.
Their goal is to validate the riskiest hypotheses and, consequently, reduce the risks.
6. Information & evidence when Scrum is effective
12 years after the first version of the SG was published, we could be talking about randomized control trials, scientific papers, etc.
Instead, we keep talking and exchanging opinions, and we struggle with absurds like SAFe.
7. Remove immutability
The SG should encourage experimentation and going beyond the framework to pursue value creation.
The Scrum Master should be focused on increasing the team's effectiveness, not "(โ€ฆ) establishing Scrum as defined in the SG
You can't focus on both.
- - -
Like this thread?
See my full article: medium.com
I might be wrong. I care about starting the discussion and getting your feedback.
Do you agree? Disagree? What are your thoughts?
If you like this thread:
1. Follow me: @PawelHuryn
2. RT the tweet below

Loading suggestions...