Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
Fixing your Scrum

Fixing your Scrum

Your Scrum has all the meetings and none of the results. Here is where it quietly broke.
by Ryan Ripley 2020 200 pages
4.32
125 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Treat Scrum as a learning loop, not a renamed project plan

Scrum reveals reality. Scrum is a framework for complex work, not a fixed sequence of steps. Its events and artifacts create regular chances to make work visible, inspect what is happening, and adapt based on evidence. A 500-page company manual that dictates every move can preserve old command-and-control habits while merely giving them Scrum labels. The framework itself is intentionally small; teams choose supporting practices to fit their situation.

Keep the feedback frequent. A working product increment gives customers and stakeholders something concrete to assess. Their responses help the team test assumptions, reduce the risk of building the wrong thing, and decide what to do next. Scrum does not solve organizational problems automatically. It makes them harder to hide, then gives people recurring opportunities to address them.

Analysis

What's valuable here is the distinction between a framework and a recipe. In complex work, the plan is a hypothesis, and feedback is the mechanism that corrects it. This resembles adaptive control systems, which adjust their actions as new measurements arrive. The framework's simplicity also makes misuse visible: ceremonies can continue while learning stops. Still, empiricism needs trustworthy evidence and room to act on it. A team that receives customer feedback but lacks authority to change direction is not adapting; it is merely collecting data.

Make small failures safe to expose before they become expensive

Surface trouble early. The book describes a workplace where people hid minor mistakes for fear of blame, while management celebrated dramatic late-night rescues. That pattern rewards firefighting over prevention. Scrum's regular planning, daily coordination, review, and retrospective are intended to reveal problems while they are still manageable. A missed assumption in a small piece of work can be corrected; the same assumption left unspoken can distort an entire product.

Values shape behavior. Scrum names commitment, focus, openness, respect, and courage as guides for difficult moments. Openness makes problems discussable; respect makes disagreement safer; courage helps people say what is not working. Teams can use these values in retrospectives by asking where they helped, where they were absent, and what specific behavior to try next.

Analysis

This connects closely to psychological safety, the shared belief that a group can take interpersonal risks without being humiliated. Safety is not comfort at all costs: it makes candid accountability possible. Small failures become useful only when the team can distinguish learning from negligence and act on what it learns. The book's emphasis on values is strongest when values are translated into observable conduct, such as raising a risk early or asking for help, rather than treated as attractive words on a wall.

Give one empowered product owner the whole product, not a committee

Unify product decisions. A retailer with seven development teams and four product owners saw priorities collide, decisions stall, and the product pull in competing directions. Its website later crashed near Cyber Monday. The lesson is not that one person should work alone, but that one accountable product owner should make final product decisions after listening to customers, stakeholders, and developers.

Authority must be real. A part-time or proxy product owner may maintain a backlog without controlling scope, budget, or value decisions. That leaves developers to guess what matters and stakeholders waiting for answers. The product owner needs time, access to relevant information, and authority to order work. A clear product vision, linked to measurable outcomes, gives the team a reason for its work and a basis for deciding whether the product is succeeding.

Analysis

A single decision-maker can reduce coordination costs, but concentration of authority is useful only when paired with broad input and visible reasoning. This is a product-level version of the distinction between consultation and consensus: many perspectives inform the choice, while one role remains accountable for making it. The model works best when the product owner has access to customers and financial context. Otherwise, singular ownership can become a bottleneck or simply give one person unchecked assumptions.

Keep the backlog lean, ordered, and detailed only near the work

One evolving source. A product backlog is the changing, ordered set of work and ideas for a product. The book recounts an audience member whose backlog item had lingered for nine years. Such stale entries can make an old wish look like a current commitment. Keep one backlog for the product, including bugs and technical work, and remove items that no longer matter. An old item can return if evidence makes it relevant again.

Match detail to distance. Near-term items need enough clarity for a team to consider them in a sprint. Work months away can remain rough, because customer needs and technical understanding may change. Ordering matters more than assigning a pile of identical top priorities: the sequence should express what is most valuable to pursue next. Estimates support conversations and forecasts, not promises of certainty.

Analysis

This is a practical application of option value: keeping distant ideas vague preserves the ability to change course without throwing away extensive specification work. A single ordered list also exposes trade-offs that separate team backlogs can conceal. Yet deletion should not become an arbitrary age rule. Some infrequent regulatory or maintenance needs may stay dormant for good reasons. The stronger test is whether an item still has a credible connection to product value, risk, or obligation.

Build cross-functional teams that finish together, not specialist queues

Organize around delivery. A health-insurance project split people into teams for databases, services, infrastructure, and front-end work. Four months passed without integrated code, and the project was eventually canceled, costing 60 jobs. When the organization regrouped people into cross-functional teams, each able to deliver an end-to-end increment, collaboration and visible progress improved markedly, though the project was still defunded.

Share the outcome. In Scrum, the team is collectively accountable for a usable increment, not only for completing each person's specialty. Testers should not wait until the end while developers work ahead; team members can collaborate, reduce work in progress, and help clear bottlenecks. The book recommends small teams, typically three to nine people, while recognizing that the necessary skills depend on the product and its definition of done.

Analysis

The shift from specialist queues to end-to-end teams reflects a broader systems principle: optimizing each stage separately can worsen total flow. Work waits at handoffs, and responsibility gets blurred precisely where integration risk is highest. Cross-functional teams reduce those boundaries, but they do not instantly create every needed skill. Organizations need to support learning, staffing, and technical practices that make shared ownership feasible, rather than simply renaming old departments as teams.

Let the Scrum Master remove barriers without becoming the team's boss

Serve, do not command. A Scrum Master helps the team and organization understand Scrum, facilitates collaboration, coaches the values, and works to remove impediments. The role is not task assignment, status collection, board maintenance, or rescuing everyone personally. The book calls out the superhero Scrum Master, who solves every problem and leaves the team dependent, and the Scrum secretary or janitor, who handles administrative tasks instead of enabling better work.

Make service inspectable. When unsure whether an intervention helps, ask the team. Journaling can reveal whether the Scrum Master mostly gives directions or asks useful questions. Some problems belong to the team to solve; others exceed its authority and require organizational action. A visible impediment list can help distinguish the two and keep unresolved barriers from disappearing into hallway conversations.

Analysis

This role requires restraint as much as action. Coaching is not passive, especially when organizational rules block delivery, but solving every local difficulty can deprive a team of practice and ownership. The useful test is whether an intervention increases the group's future capacity to act. That principle resembles capacity-building approaches in education and leadership. It also requires humility: asking the team for feedback can expose that a well-intended facilitator has become a source of dependency.

Help managers replace busywork metrics with customer outcomes and evidence

Address management's actual concerns. Managers still have important responsibilities in Scrum: setting organizational goals, aligning work, supporting people, and removing systemic obstacles. Scrum Masters should learn what leaders need to understand, then explain progress in terms they can use, such as cost, risk, delivery, and customer value, rather than relying on Scrum vocabulary alone.

Challenge utilization thinking. A company in the book assigned people across more than 100 simultaneous projects to keep them busy. Mapping projects to organizational goals revealed that many did not support a stated goal. The authors also describe teams manipulating estimates and charts to satisfy productivity tracking while real delivery stalled. Frequent task switching and individual utilization can look efficient while delaying completed work. Transparent outcomes and customer feedback offer a better basis for discussion.

Analysis

This is a useful bridge between team autonomy and organizational governance. Leaders need information, but measures shape behavior: when a dashboard rewards activity, people learn to optimize the dashboard. This is a familiar Goodhart-style problem, where a proxy loses value once it becomes a target. The answer is not to reject measurement. It is to choose measures that illuminate flow, quality, and outcomes, then interpret them in context rather than using them as individual performance weapons.

Plan around a sprint goal, not a packed list of tasks

Choose an outcome. Sprint planning asks what the team should build and how it can begin. Its result is a sprint goal, a forecast of selected work, and an initial plan. A goal such as adding digital payment options gives the team a shared purpose and allows scope to be adjusted if the work proves harder than expected. A vague goal such as finishing the sprint backlog gives no meaningful direction.

Respect the time box. Sprints last a month or less and should keep a consistent duration. Extending a sprint to finish one more item delays feedback and hides the reason work did not finish. Specialized design, testing, or hardening sprints often reveal that quality or integration has been postponed. Instead, do the full path toward a usable increment within each sprint, and use difficulties as evidence about what needs to improve.

Analysis

A goal provides a stable direction while leaving room to revise the route. That balance is valuable in uncertain work: rigid plans break when assumptions fail, while goals without constraints can dissolve into vague aspiration. The sprint time box makes the learning cycle tangible. However, a short cadence is not automatically better in every setting; the right length depends on how long the product can safely go without feedback and whether the team can produce a meaningful increment.

Let developers own the sprint plan and daily coordination

Keep the plan alive. The sprint backlog is the development team's working plan for the current sprint. It can change as the team learns, but the sprint goal remains its anchor. In one company, management required developers to account for every hour, and teams learned to make burndown charts look right while little reached production. The chart measured apparent activity, not useful progress.

Make coordination collaborative. The Daily Scrum is a 15-minute planning conversation for developers, not a report to the Scrum Master. The team inspects its work, spots stuck items, and decides how to coordinate over the next day. A physical or digital board can make progress and bottlenecks visible. Cycle time, the elapsed time from starting an item to finishing it, can help reveal delays, such as a code review taking five days in a two-week sprint.

Analysis

Ownership and transparency need to travel together. Autonomy without visible work can leave stakeholders guessing; visibility without autonomy becomes surveillance. This tension appears in modern software teams as much as in other knowledge work. Flow measures such as cycle time can help identify process delays, but they are not a complete account of value or complexity. The daily conversation matters because it turns the board from a reporting surface into a shared instrument for changing the plan.

Define done as releasable, and protect quality under deadline pressure

Make completeness explicit. The Definition of Done is the team's shared standard for a completed increment. It may include reviewed code, passing automated tests, integration, and deployment to a staging environment. Without it, a developer may call a feature finished because it works locally, while the product owner expects something ready to release. Clear criteria reduce that mismatch and expose missing skills or organizational dependencies.

Do not borrow quality from tomorrow. Skipping tests to hit a date creates unfinished work and technical debt, which can make future changes slower and riskier. A team facing a deadline can negotiate scope or split work into smaller valuable pieces rather than pretending incomplete work is done. A hardening sprint is not a substitute for testing and integration throughout development.

Analysis

A shared completion standard is a coordination device, not merely a quality checklist. It makes promises legible across developers, product owners, and stakeholders. The insistence on releasability is especially powerful because it links technical work to real feedback. There is a practical caveat: teams may begin below that standard because of legacy systems or missing infrastructure. The honest response is to make the gap visible and improve capability, not to relabel unfinished work as complete.

Use sprint reviews to redirect the product with stakeholders

Review the whole picture. A sprint review is a working session to inspect the increment and discuss what should happen next, not simply a demonstration. Stakeholders can reveal operational needs, market changes, and risks the team has not seen. In a nonprofit project, the product owner excluded stakeholders to avoid scope growth. When they finally saw the work, they raised basic questions about currencies, mobile access, and system integration. The project was canceled after months of effort.

Be transparent about progress. Invite the people whose jobs, budgets, or customers are affected. Explain the product vision, sprint goal, current increment, impediments, and relevant forecasts. Do not present unfinished work as complete or skip the review because the sprint went badly. An uncomfortable conversation can correct direction sooner than silence.

Analysis

The review functions as a boundary-spanning meeting: people with different knowledge compare what the team made with what the surrounding organization needs. That can expose assumptions invisible inside the team. Its value depends on honest framing and genuine participation, not on a polished presentation. Stakeholder feedback should inform product choices without becoming a queue of competing demands; the product owner still has to make coherent decisions about value and order.

Make retrospectives produce one or two visible experiments

Improve the work system. The retrospective gives the whole Scrum team a private forum to examine collaboration, quality, and working practices. The book's examples show how vague suggestions such as writing better code or collaborating more can conceal specific problems. Ask what is causing the difficulty, then choose a small change that can be tried and reviewed.

Follow through visibly. Teams should attend consistently, avoid turning the event into a blame session, and limit commitments to one or two achievable improvements. Treat them as real work, make them visible during the sprint, and check whether they were attempted. Formats such as the Starfish Retrospective help teams identify what to start, stop, do more, do less, or keep. If the team feels too busy to reflect, examine what created that pressure.

Analysis

The retrospective is a compact learning cycle for the team's own operating system. Small experiments make improvement concrete and reduce the risk of turning discussion into ritual. This resembles experimental design: name a change, observe what happens, and decide whether to keep it. The team's privacy matters because candid critique can be costly in hierarchical settings. Yet privacy should not become insulation from organizational causes; systemic barriers must still be translated into requests or experiments beyond the team's control.

Analysis

Fixing Your Scrum is a practical troubleshooting guide organized around roles, events, and artifacts. Its central argument is that Scrum's visible mechanics are not the source of value by themselves. The value comes from short feedback loops, real authority at the team level, technical quality, and a culture where people can reveal what is happening. The recurring stories make organizational dysfunction concrete: specialist teams cannot integrate, a backlog item survives for nine years, and teams can produce immaculate charts while delivering little.

The book's strongest contribution is its attention to incentives. Many anti-patterns are not individual failures but sensible adaptations to a system that rewards utilization, punishes bad news, or reserves decisions for distant authorities. The proposed remedies therefore range beyond meeting technique. A product owner needs actual decision power, developers need end-to-end skills, and managers need credible evidence about outcomes. Scrum is presented as a way to expose these mismatches, not as a magic switch that removes them.

The guidance also depends on a normative ideal: small, cross-functional teams can deliver useful increments frequently. That is a valuable design target, but implementation varies. Legacy architecture, regulatory controls, vendor dependencies, and operational risk can make release readiness difficult. In such settings, a team can still use short inspection cycles, but it should be precise about what is genuinely releasable and which constraints need organizational investment. The framework's roles should guide accountability rather than become rigid job descriptions.

The book is most persuasive when it treats practices as experiments and least persuasive when a recommended rule risks sounding universal. Metrics, board formats, and team sizes can be useful or harmful depending on purpose and context. Its deeper test is more durable: does a practice increase transparency, learning, quality, and the ability to make timely decisions? That question keeps Scrum from collapsing into either ceremony or doctrine.

Summary in 30 Seconds
Scrum is a learning loop that exposes problems early, not a renamed project plan. Give one product owner real authority over a single ordered, lean backlog. Build small cross-functional teams that deliver a releasable increment each sprint, anchored by a sprint goal rather than a task pile. Never trade quality for deadlines; negotiate scope instead. Replace utilization and hour-tracking metrics with customer outcomes. Retrospectives should yield one or two visible experiments.
Contains spoilers

Last updated:

Report Issue

Review Summary

4.32 out of 5
Average of 125 ratings from Goodreads and Amazon.

Fixing Your Scrum receives overwhelmingly positive reviews, with readers praising its practical approach to addressing common Scrum issues. Many reviewers highlight the book's valuable insights for both new and experienced Scrum Masters. The comprehensive overview of Scrum dysfunctions and solutions is frequently mentioned. Readers appreciate the anti-pattern examples, actionable advice, and emphasis on Scrum values. The book is recommended for entire Scrum teams and stakeholders, with many considering it a must-read for those involved in Scrum practices.

Your rating:
4.66
104 ratings
Want to read the full book?

Glossary

Empirical process control

Learning through observed results

A way to guide work by using experience and evidence rather than assuming every step can be planned in advance. In Scrum, transparency makes work understandable, inspection helps people assess results, and adaptation changes the plan when new information appears. The approach is intended for complex work where important facts emerge during development.

Definition of done

Shared completion standard

A clear description of the qualities required for work to count as complete. It helps developers, product owners, and stakeholders share an understanding of the increment's state. Criteria may include testing, integration, code review, and deployment readiness. The team uses and improves the definition as its capabilities and product needs develop.

Sprint goal

Purpose of the sprint

A single objective that explains why the team is working on the current sprint. It gives developers a shared direction for coordinating work and helps the product owner and team discuss scope when plans change. The selected work can evolve, but the goal remains the central reference point during that sprint.

Product backlog refinement

Preparing future work

Ongoing collaboration between the product owner and development team to add detail, estimate, order, or break down product backlog items. Refinement helps prepare near-term work for sprint planning, while distant ideas can remain less specific. It is an activity that teams arrange to suit their needs, rather than a separate required Scrum event.

15% Solutions

Find a manageable next step

A group exercise in which participants identify what they can personally change, with the resources and authority already available to them. Rather than asking how to transform an entire organization at once, it focuses discussion on a limited action that can move conditions in a better direction. The book uses it to help Scrum Masters choose practical change efforts.

Fist of Five

Quick confidence check

A facilitation technique in which people show one to five fingers to indicate their support or confidence in a proposal. Low scores invite discussion about reservations, while higher scores indicate stronger alignment. The purpose is not simply to count votes, but to surface concerns that might otherwise remain unspoken.

Starfish Retrospective

Sort improvement opportunities

A retrospective format that organizes team observations into five categories: Start, Stop, More, Less, and Keep. Participants suggest practices to adopt or discontinue, identify what deserves greater or lesser emphasis, and preserve what is working. The team then discusses patterns and selects specific changes to try.

Cynefin Framework

Distinguish problem contexts

A framework referenced in the book to help people discuss different kinds of work and uncertainty. Its domains distinguish situations where cause and effect are clear, require expertise, emerge through interaction, or are chaotic. The book uses the framework to explain why software development often needs experimentation and adaptation instead of exhaustive upfront planning.

About the Author

Ryan Ripley is the author of "Fixing Your Scrum: Practical Solutions to Common Scrum Problems." He is an experienced Scrum practitioner and trainer who has gained recognition for his expertise in the field. Ripley's approach to Scrum focuses on addressing real-world challenges faced by teams implementing the framework. His writing style is noted for its clarity and practicality, offering actionable solutions to common issues. Ripley's work reflects a deep understanding of Scrum principles and values, emphasizing their importance in successful implementation. His insights are drawn from extensive experience working with various teams and organizations, making his advice relevant and applicable across different contexts.

Download PDF

To save this Fixing your Scrum summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.34 MB     Pages: 18

Download EPUB

To read this Fixing your Scrum summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.41 MB     Pages: 22
Want to read the full book?
Follow
Listen
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 24,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
1M+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...