Aha! Moments in Agility
Live in your inbox every Sunday to help you build valuable software sooner
AMIA: #24
Reading Time: ~ 3 minutes
You're a Scrum Master, and you're all about metrics. But let's cut through the noise:
Are those numbers making an impact on your Product Manager?
Are you solving real problems or just ticking boxes?
The Problem with Story Points
You present your metrics, and your Product Manager gives you that look. You know the one.
Reality Check: To them, it's just static.
Why?: Because it doesn't address their real concerns or ambitions.
Example: Imagine telling your Product Manager that you've completed 20 story points, but you can't say when the new feature will be ready for marketing to promote. Frustrating, right?
Inside the Mind of a Product Manager
What's keeping your Product Manager up at night?
Delivering tangible value
Speed to market
Efficient resource allocation
Curiosity: They're keen on innovation, team efficiency, and customer reactions.
Question: Are you adding to their knowledge or just adding to the noise?
Aligning Metrics with Stakeholder Needs
You've got your metrics, but do they align with what your Product Manager values?
Focus on outcomes, not activities
Address risk in terms of business impact
Release Dates: They need to align other business functions like marketing, sales, and change management.
Example: Instead of saying "We've reduced technical debt," say "We've improved load times, which will boost customer retention."
Actionable Steps for Scrum Masters
Ready to pivot?
Shift the conversation to user outcomes. For example, discuss how faster load times will improve user experience.
Change your check-in cadence to focus on these outcomes and business impact.
Reformat your risk discussion to business implications, not just technical hurdles.
Provide realistic release dates to help Product Managers align other business functions by adopting the Zero Estimate System. It's not just about ditching the guesswork; it's about establishing a channel of clear, accountable communication that neither you nor your stakeholders will have to second-guess later.
Example: Instead of saying "We’ve 23 story points left," say "We're 85% confidence that we can complete the work by March 15th or earlier.”
When you’re ready…
I can help you in 3 ways:
Check out the resources list
Forecast timelines like a Pro in under 1 minute - Zero Estimate System
Fix the root cause of bugs & defects in your team - Root Cause Analysis Template
Book One on One coaching with me - Become a go-to Scrum Master in your organization.
Find me on LinkedIn and introduce yourself :)