Просмотр новости
Найдите то, что Вас интересует
Спутники
РН
SpaceX
Роскосмос
NASA
СпутникиРНSpaceXРоскосмосNASA
Image
Most Scrum Teams I work with are good at delivery. They have a stable Sprint cadence, a clear Definition of Done, and they deliver a usable Increment every Sprint. The Sprint Review runs on time and stakeholders nod along.And yet, when I ask Product Owners in class how many of last quarter's Product Backlog items measurably moved an outcome, the room goes quiet.That silence is what this post is about. Scrum is built on empiricism and lean thinking. A team can apply empiricism thoroughly to how it builds and hardly at all to what it builds. When that happens, every gain in delivery speed multiplies work nobody needed.To help teams see this gap, I built a free, 10-question Product Discovery Maturity Assessment. This post explains what it measures, why it's structured the way it is, and what to do with your result. There's also a video walkthrough below if you'd rather score along while you watch.
Two diamonds, one Scrum TeamThe assessment uses the Double Diamond, introduced by the UK Design Council in 2005. It describes two cycles of widening and then narrowing.The first diamond is about the problem. You discover, exploring widely what is really going on for customers, and then you define, converging on the problem worth solving. The second diamond is about the solution. You develop, exploring solution options, and then you deliver, converging on what actually works.Put simply, the first diamond asks "are we building the right thing?" and the second asks "are we building the thing right?"A word of caution for this community: the Double Diamond is not a phase plan to bolt onto Scrum. Scrum has no discovery phase, no design phase and no hand-off to a separate discovery team. Discovery and validation are work the Scrum Team does inside its Sprints. That work shows up in the Product Backlog as experiments, hypotheses and questions to answer, alongside the features being built. The diamonds are a lens for inspecting whether both kinds of work are really happening, not a sequence to follow.For the same reason, the assessment adds a fifth area: continuous rhythm. A team that does discovery once, at kickoff, is running a mini-waterfall with Sprints attached. Empiricism needs a steady flow of evidence, not a single upfront batch.What the ten questions look atThere are two questions per area, and each is answered by choosing the statement that best describes how your team works today.Discover. How does the team explore problems before committing to solutions, and how much direct customer contact do the Developers themselves have? Watch for this pattern: the Product Owner talks to customers and relays what they said. That is a relay race, not team learning.Define. How does the team decide which problem is worth solving, and how does it converge from many findings to one clear problem? The weakest answer is not a caricature. It reads "priorities mostly arrive from leadership, sales or the biggest customer," because that is honestly how many Product Backlogs are ordered.Develop. Does the team compare several solution options, or build the first reasonable idea? Does it test ideas before building them? Mature teams test all four product risks: value, usability, feasibility and viability. Internal opinion does not count as testing; stakeholders are not users.Deliver. What evidence is required before a solution goes out to everyone, and how does the team know a release actually worked? This connects directly to Evidence-Based Management. "Did we ship on time?" measures output. Mature teams set outcome targets before release, so success can't be redefined after the numbers arrive.Continuous rhythm and evidence hygiene. How often does discovery happen, and how does the team treat AI-generated insights? The AI question is deliberately designed so that using more AI does not raise your score. The lowest score goes to treating AI summaries or synthetic-user output as if they were customer evidence, which ranks below not using AI at all. The highest score goes to teams that use AI to widen and speed up discovery, and then validate anything that drives a decision with real users. AI shifts the bottleneck from producing insight to verifying it. Accountability for what goes into the Product Backlog stays with the Product Owner.Reading your resultA score of 10 to 17 means Output Factory: the team builds on request with little exploration. 18 to 24 means Project Discovery: discovery happens, but as an upfront phase that fades under delivery pressure. 25 to 32 means Dual-Track Discovery: discovery and delivery work happen in parallel. In Scrum terms, that means the same team and the same Product Backlog, not two teams handing work over a wall. 33 to 40 means Continuous Discovery: evidence gathering is a weekly habit.There's one guardrail. If any single area scores 4 or less across its two questions, you can't be in the Continuous stage. Continuous discovery with a broken phase isn't continuous.The check that matters most: the wrong-half trapNow the part your total won't tell you. Add up questions 5 to 8 (the second diamond) and compare them with questions 1 to 4 (the first). If the second diamond beats the first by four points or more, the team is in what I call the wrong-half trap.Here is why this happens so often in Scrum Teams. Delivery work is visible: Sprint Reviews, burn-downs and Increments all make it tangible. Discovery work is quiet and slow, and easy to postpone for one more Sprint. Over time the team gets steadily better at building things right while the question of whether to build them at all goes unanswered.The overall score can hide this completely. When I tested the assessment, a team that scored the minimum on every first-diamond question and the maximum on every second-diamond question still came out as a respectable "Dual-Track." That average looked healthy, but the team had no discovery practice at all. This is why the online version flags the trap separately rather than folding it into one number.If you're in the trap, don't try to deliver faster. Fix the first diamond first.What to do with your result on MondayWhatever your stage, a few moves fit directly into Scrum events you already run.Take it as a whole Scrum Team, not alone. Ask the Product Owner, a couple of Developers and anyone doing design work to take the assessment separately, then compare results in a Sprint Retrospective. The question where you disagree most is usually where discovery broke down, because each person assumed someone else was doing it. The online tool has a "Copy my result" button to make sharing easy.Put learning in the Product Backlog. If discovery work isn't in the Product Backlog, it isn't transparent, and if it isn't transparent it can't be inspected. Write the riskiest assumption behind your next big item as a Product Backlog item with a clear question and a pass/fail signal.Change what Sprint Review inspects. Alongside "here is what we built," add "here is what we learned, and here is the outcome it moved or didn't." That one change starts moving a team from output toward outcome.Bring Developers into customer conversations. Even one short customer call per Sprint, joined by a Developer, changes the quality of refinement discussions noticeably.Going deeper: Professional Product Discovery and ValidationThe gaps this assessment reveals are exactly what the Scrum.org Professional Product Discovery and Validation (PPDV) class is designed to close. It's a one-day, hands-on class. You practice turning assumptions into testable hypotheses, designing experiments, and fitting discovery and validation into the way your Scrum Team already works. Many teams have a strong second diamond and an underused first one; this class is about building that first diamond.I teach PPDV as a Professional Scrum Trainer. If your result showed a wrong-half trap or a weak Discover or Define score, it's the most direct next step I can recommend. Try it and tell me your scoreTake the free Product Discovery Maturity Assessment. It takes about five minutes, runs entirely in your browser, and needs no sign-up. Then share your stage in the comments, and tell me whether your team fell into the wrong-half trap. I'd especially like to hear from teams that climbed out of it, and what they changed first.
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | 5 Things the Product Owner Shouldn’t Be Doing | 0 | 16.4 | 29-09-2026 |
| 2 | O que sabemos agora que não sabíamos no início da Sprint? | 0 | 10.22 | 04-09-2026 |
| 3 | Nobody Owns Whether it Worked. | 0 | 8.63 | 29-09-2026 |
| 4 | AI on Top of a Dysfunctional System (1): The Product Backlog | 0 | 5.29 | 20-09-2026 |
| 5 | Your Team Isn't Slow. Your Handoffs Are. | 0 | 8.51 | 22-09-2026 |
| 6 | Which Class Should You Arrange Next? | 0 | 9.78 | 07-09-2026 |
| 7 | KI auf einem dysfunktionalen System (1): Das Produkt-Backlog 🇩🇪 | 0 | 8.42 | 24-09-2026 |
| 8 | ‘Batches’ in Scrum | 0 | 13.56 | 24-09-2026 |
| 9 | Scrum's Protocol Is Easy to Copy. Its Agenda Is Not. | 0 | 14.4 | 27-09-2026 |
| 10 | 🎉 Published: Scrum Team Magazine - October 2026 - Issue #2 | 0 | 15.71 | 30-09-2026 |