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
Rethinking Agile

Rethinking Agile

Why Agile Teams Have Nothing To Do With Business Agility
Why faster teams can leave the business slower, and how to fix the delays that matter.
by Klaus Leopold 2018 134 pages
4.30
500+ ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Agile teams cannot make a business agile when the system stays slow

The local fix failed. A company reorganized 600 IT employees into cross-functional product teams, trained them in Agile methods, and gave teams room to choose how they worked. After a year, more than 80 percent met the new requirements: visible work, regular meetings, and retrospectives. Yet the business goal, faster delivery to market, was slipping further away. The teams had changed; the way the organization selected, coordinated, and delivered work had not.

Agility is a company capability. The book’s central distinction is that team agility improves work inside a team, while business agility depends on the whole route from an idea to customer value. A highly efficient team cannot compensate for slow approvals, crowded queues, or poorly managed handoffs elsewhere.

Analysis

The case is a useful antidote to the tendency to treat organizational change as a collection of team-level interventions. Systems theory makes the same point: the performance of connected parts depends on their relationships, not simply on the quality of each part. The distinction also sharpens accountability. Teams can own their workflow, but leaders own the conditions that determine what enters it and how work crosses boundaries. One caution: the case illustrates a pattern, not proof that team-level Agile is ineffective. Its value lies in asking whether local improvements reach customers.

Measure customer delivery, not whether teams adopted the rituals

Adoption is not impact. The company tracked Scrum teams’ throughput, meaning completed work per period, and Kanban teams’ cycle time, the elapsed time from starting a task to finishing it. Scrum throughput rose at first, then flattened and began to decline. Kanban cycle time improved by less than 1 percent. Because teams had been reorganized, the company lacked strong before-and-after team comparisons. Project cycle time offered a more useful business-level measure, and it showed delivery taking longer after the transformation began.

Track the goal directly. The initiative aimed to shorten time-to-market, so measuring meeting attendance or board usage could not establish success. Metrics are feedback, not trophies: compare results with a baseline, and connect them to the customer or business outcome the change is meant to improve.

Analysis

This is a practical lesson in measurement design. A leading indicator, such as whether teams hold retrospectives, can show that an intervention is happening. It cannot establish that the intervention produces value. Outcome measures answer a harder question, but they also require care: project duration can shift because of changing project size, market conditions, or staffing. The strongest evaluation combines process signals with business outcomes and makes limitations visible. That approach avoids both ritual compliance and the opposite mistake of attributing every movement in a business metric to one transformation.

Optimize the handoffs, because value is created between teams

Dependencies survived the reorganization. Product teams were intended to be self-sufficient, but their boards repeatedly showed work stalled while waiting for another team, a service, or a decision. Some products required several teams, and products also depended on one another. Cross-functional staffing reduced certain dependencies; it could not erase every connection in a 600-person IT organization.

Coordinate what remains. The author argues for reducing unnecessary dependencies and actively managing the rest. A team can improve its own speed while creating a bottleneck for another group. The book illustrates this with a keyboard: striking one letter’s key faster does not finish a meaningful message. The relevant unit is the complete path through which coordinated work becomes a product, not the performance of one isolated team.

Analysis

The handoff focus connects to a broad finding in operations: delays and rework often accumulate at interfaces, where ownership, timing, or information is unclear. It also changes the meaning of collaboration. Friendly relationships matter, but dependable coordination requires shared visibility and decisions about sequence and capacity. There is a useful limit to the argument: not every dependency deserves elimination or elaborate governance. Some are necessary, and managing all of them equally can become its own source of overhead. The practical question is which connections materially affect customer delivery.

Map the whole journey from idea approval to customer release

The visible board was incomplete. Teams initially mapped development as if it were the whole value stream, the full sequence of steps that turns an idea into something customers can use. Asking what happened before development revealed idea triage, business cases, and approval committees. Asking what happened after revealed integration, acceptance testing, and release. Some decisions occurred only quarterly or annually; releases and acceptance tests happened just four times a year.

Waiting counts as time. Flow efficiency is the share of total cycle time spent on active work rather than waiting. The book notes that it is often below 10 percent in organizations. Speeding up development alone has little effect when most elapsed time is spent waiting for a decision, a handoff, or a release window.

Analysis

Mapping the full journey is powerful because people tend to optimize the portion they can see and control. The concept of flow efficiency makes hidden delay discussable without blaming individual workers. It also points toward a useful diagnostic: distinguish active work from queue time, then investigate the largest waits. A low percentage does not automatically mean every approval is wasteful. Reviews may protect safety, legal compliance, or strategic coherence. The goal is not to remove controls indiscriminately, but to make their purpose explicit and shorten delays that do not buy meaningful protection.

Limit initiatives where delays are actually created

Team limits cannot clear a portfolio jam. Work in process, or WIP, is work that has started but is not yet complete. Teams in the case limited stories and tasks, while managers continued launching initiatives faster than the organization finished them. The result resembled an airport where arrivals exceed departures: eventually, congestion blocks movement.

Use the queueing relationship. Little’s Law relates average cycle time to average WIP divided by average throughput. In the book’s illustration, a system completing five items a day has an average two-day cycle time with ten items in the system, but a 20-day cycle time with 100. Limits should therefore be placed at the level whose delay matters. If initiative delivery is slow, manage the number of active initiatives, not only team tasks.

Analysis

The queueing perspective explains why starting more work can feel productive while making completion slower. It also makes prioritization an economic choice: work left unfinished cannot yet produce its intended benefit. Little’s Law is a relationship among averages, not a promise that every individual task will follow the same timeline. Demand variability, task size, and bottlenecks matter too. Still, the direction is hard to ignore: when throughput is constrained, adding more work to the queue increases the time work spends waiting. The managerial challenge is to say no, or not yet, transparently.

Make the transformation pull-based, not a scheduled rollout

The change contradicted its goal. The company wanted adaptability but organized its transformation as an 18-month project with planned milestones. Teams had some choice in their methods, yet the rollout itself largely pushed a prescribed change through the organization. The author argues that a change process should already embody the way of working it seeks to establish: adapt through observation, feedback, and incremental decisions rather than assuming a fixed plan will install a new mindset.

Do not confuse the method with the purpose. Daily meetings, boards, and cross-functional teams are possible tools, not evidence that customers receive value sooner. Nor does a new organizational chart create better flow by itself. The book warns against copying structures such as Spotify’s team labels without first understanding the business problem those arrangements were designed to address.

Analysis

This principle echoes adaptive management: when the route is uncertain, small experiments produce information that a long-range plan cannot supply in advance. It also distinguishes disciplined learning from improvisation. A flexible transformation still needs goals, decision rights, and boundaries; otherwise, experimentation can become drift. The strongest version of the argument is not that planning is useless, but that plans should remain revisable as evidence arrives. Likewise, methods can provide valuable defaults, especially for inexperienced teams. They become harmful when compliance displaces the question of whether work is reaching customers more effectively.

Use three organizational altitudes to locate the real leverage

Look at the right level. The book calls its diagnostic model Flight Levels: a way to view work at different organizational scopes, not a hierarchy, maturity scale, or prescribed structure. At the operational level, teams manage their own workflow. At the coordination level, representatives manage the end-to-end work of a product or service across teams. At the strategic portfolio level, leaders select and limit initiatives in line with strategy and available capacity.

Match the problem to the view. A small quality issue may be handled by one team. Repeated delays between teams call for cross-team coordination. Too many initiatives or misalignment with strategy require portfolio decisions. The model encourages visualizing work, limiting it, using feedback, and making improvements at whichever scope has the leverage to change the result.

Analysis

The value of this model is less its labels than the question it forces: where does the constraint live, and who can change it? That resembles multilevel analysis in organizational research, where individual, team, and institutional explanations can all be relevant but should not be collapsed into one. The model also discourages reflexively reorganizing teams when a decision-making bottleneck sits above them. Its flexibility is an advantage, though it leaves implementation choices open. Organizations still need to define who participates, what decisions belong at each scope, and how information travels between them.

Bring executives and business teams into the same delivery loop

Connect decisions to delivery. The company shortened its upstream process from five stages to two: an approximate business case and a wait for approval. Rough concepts could be assessed every two weeks, subject to available capacity, instead of waiting for infrequent committee decisions. Business representatives also joined product discussions and retrospectives, giving them earlier visibility into progress and problems.

Make strategy a working system. Strategic portfolio management means deciding which initiatives to pursue, when to start them, and whether they are producing the intended result. The company used a shared strategy board to connect initiatives with business measures, and adjusted the cadence of leadership decisions so choices could be made in context rather than as isolated approvals. This helped reduce the divide between business groups that requested work and IT teams that delivered it.

Analysis

The integration of business and delivery teams addresses a common information problem: decision makers can approve work without seeing its operational consequences, while implementers may lack the context behind priorities. Short feedback cycles make those costs easier to surface. The book’s emphasis on approximate estimates also reflects a useful distinction between precision and decision usefulness. Still, faster approval is not automatically better if decisions become impulsive or strategy is unstable. A shared portfolio view helps only when leaders are willing to defer, stop, or reorder work rather than treating every attractive idea as an immediate commitment.

Judge agility by market outcomes, not activity or output

The recovery took years. Three years after the initial attempt was redirected, average initiative completion was seven months faster, more than twice as fast as before. The company estimated that earlier delivery avoided about 10 million euros in annual delay costs. Revenue growth, previously around 2 to 4 percent, reached roughly 25 percent in one reported year; profit tripled over three years, and market capitalization rose from 3.4 billion to 7.1 billion euros.

Results have several causes. Faster decisions, more experimentation, earlier customer feedback, and improved coordination all contributed, but the author does not claim the transformation alone caused every financial change. The deeper measure of agility is whether the organization learns what customers value and delivers it sooner. More features or initiatives are not wins if the market does not need them.

Analysis

The results make the argument concrete, while the causal caution is essential. Revenue, profit, and market value are influenced by strategy, competition, and economic conditions as well as operating practices. A credible evaluation therefore asks both whether delivery changed and whether customers or the business benefited. The section also points beyond speed: experimentation and feedback can improve the choice of what to build, not merely the pace of production. Faster delivery of the wrong product is still waste. Agility is best understood as a capacity to make and revise consequential bets with shorter delays.

Analysis

The book’s strongest move is to shift the unit of analysis from the Agile team to the path that carries an idea through an organization. Its case study gives this argument a narrative: a serious, well-funded transformation appears successful by adoption measures, yet the business gets slower. The mismatch exposes a category error. Teams can improve their local routines while executive choices, upstream approvals, cross-team dependencies, and release schedules continue to govern the customer’s actual wait.

The central logic combines systems thinking with flow management. Work moves through connected stages; congestion, waiting, and handoffs influence delivery more than isolated effort. WIP limits matter because limiting work at the wrong scope cannot relieve the constraint that determines end-to-end time. The Flight Levels model provides a practical way to ask whether an issue belongs to team execution, cross-team coordination, or strategic selection. Crucially, it is presented as a lens rather than an organizational template, avoiding the very cargo-cult behavior the book criticizes.

The book is especially persuasive when it separates activity from outcomes and encourages leaders to examine the entire value stream. Its cautions are equally important: quantitative relationships such as Little’s Law describe averages, while real systems contain variation; performance results do not prove that one intervention caused financial improvement; and some approvals or dependencies protect legitimate interests. The author’s best prescription is therefore diagnostic rather than doctrinaire: make work visible, trace delays, limit the work at the consequential level, and learn from feedback.

The broader leadership implication is that agility cannot be delegated as a team makeover. Executives shape the demand placed on the system, the cadence of decisions, and the conditions under which teams can deliver. A business becomes more adaptable when its strategy, coordination, and execution can respond to evidence together. Methods are useful when they support that capability, but the customer-facing result remains the test.

Summary in 30 Seconds
Team-level improvements cannot overcome slow approvals, crowded queues, and stalled handoffs across an organization. Measure the full time from idea to customer delivery, since active work often accounts for less than 10 percent of elapsed time. More unfinished initiatives mean longer waits: a system completing five items daily averages two days with ten items underway, but 20 days with 100. Limit work where delays form, coordinate across teams, and use customer outcomes to guide decisions.
Contains spoilers

Last updated:

Report Issue

Review Summary

4.30 out of 5
Average of 500+ ratings from Goodreads and Amazon.

Rethinking Agile receives positive reviews for its insights on business agility. Readers appreciate the book's focus on optimizing entire value streams rather than just individual teams. The case study format and visual presentation make complex concepts accessible. Many reviewers highlight the book's emphasis on management involvement and the importance of looking beyond traditional agile methods. Some criticize the lack of new information or practical examples. Overall, readers find it a valuable resource for understanding and implementing true business agility.

Your rating:
4.65
68 ratings
Want to read the full book?

Glossary

Flight Levels

Views of organizational work

A model for examining work at different scopes without treating those scopes as a hierarchy or a maturity ranking. The operational level concerns team workflow, the coordination level concerns work across teams in a value stream, and the strategic portfolio level concerns choosing and limiting initiatives. It helps locate where an improvement can have the greatest effect.

Flow Efficiency

Active time divided by elapsed time

The share of an item’s total cycle time spent on active work rather than waiting. A low figure indicates that much of the elapsed time is spent queued, blocked, or awaiting decisions. The concept helps distinguish the time spent doing work from the total time a customer waits for the result.

WIP limits

Caps on unfinished work

Limits on the amount of work allowed to be active in a system at one time. By preventing too many items from being started simultaneously, WIP limits can reduce task switching, expose bottlenecks, improve predictability, and shorten average cycle time. Their value depends on applying them at the level where the desired improvement is needed.

Little's Law

A relationship among flow averages

A queueing relationship stating that average cycle time equals average work in process divided by average throughput, for a stable system. In the book, it explains why a larger queue produces longer average waits when the completion rate stays constant. It describes averages and should not be read as a precise prediction for every individual item.

Strategic Portfolio Management

Choosing and limiting initiatives

The organizational work of deciding which products, projects, and strategic initiatives should proceed, in what sequence, and whether they align with strategy and available capacity. It makes current and proposed work visible so leaders can assess new ideas alongside existing commitments, rather than approving initiatives one at a time without considering the system-wide load.

Option Pool

Work waiting outside active delivery

A place to hold possible work before it enters the active system. Keeping items in an option pool makes it possible to preserve future choices without counting every candidate as work already in progress. When capacity becomes available, decision makers can select the next appropriate item instead of starting everything at once.

About the Author

Klaus Leopold is an expert in business agility and Kanban methodologies. He is known for developing the "Flight Levels" concept, which provides a framework for implementing agility across different organizational levels. Klaus Leopold has written several books on agile practices and business transformation. His work focuses on helping organizations move beyond team-level agility to achieve broader business agility. Leopold is recognized for his practical approach to implementing agile principles and his ability to explain complex concepts in an accessible manner. He frequently speaks at conferences and conducts workshops on Kanban and business agility. Leopold's consulting work has helped numerous companies improve their processes and achieve better business outcomes.

Download PDF

To save this Rethinking Agile summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.30 MB     Pages: 15

Download EPUB

To read this Rethinking Agile 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.36 MB     Pages: 18
Want to read the full book?
Follow
Listen2 mins
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...