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
AGILE in Practice

AGILE in Practice

Practical Use-cases on Project Management Methods including Agile, Kanban and Scrum
Cut support-ticket lead time from 25 days to 10 by changing how work enters and moves.
by Sudipta Malakar 2021 314 pages
5.00
1 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Use Scrum for bounded delivery, Kanban for changing demand, and hybrids deliberately.

Fit the work first. Scrum organizes product development into timeboxed iterations, making it useful when a team can agree on a near-term goal and deliver a tested increment. Kanban suits work that arrives unpredictably, such as application support tickets whose priorities shift daily. Scrumban combines elements of both, including pull-based work and selected Scrum routines, for teams that need structure without fixed sprint commitments.

Pull beats prediction. In manufacturing Kanban, a downstream work area signals that it needs another fixed quantity. Replenishment can come from in-house production, an outside supplier, or a stock transfer. In SAP, an empty-container signal can trigger the corresponding order or movement. By contrast, Material Requirements Planning calculates quantities and dates in advance, then pushes work through production.

Analysis

The useful question is not which method is superior, but how demand behaves. A team handling incidents is not managing the same kind of work as a team building a planned product release. Choosing a framework around that difference prevents rituals from becoming a substitute for diagnosis. The caution is that method labels can conceal local constraints: compliance, customer access, and technical dependencies may matter more than whether work is called Scrum or Kanban.

Cap active work before speeding people up; flow improves when finishing wins.

Make congestion visible. In the aviation support case, teams handling more than 80 applications faced rework, conflicting assignments, and urgent tickets that got stuck behind too many open tasks. They mapped the workflow, displayed work on a Kanban board, limited work-in-progress, and let people pull tasks instead of having a lead assign them. The team kept its active load small, around three or four items for five or six people, and treated blockers as urgent work to resolve.

Reported gains were concrete. Average ticket lead time fell from about 25 business days to 10. The case also reported less rework and approximately $19,000 in monthly labor-cost savings in 2017. These figures describe one team's results, not a guaranteed return from installing a board.

Analysis

Limiting work is a capacity decision, not a demand to work harder. When several tasks wait for the same specialist or customer decision, adding more starts can increase congestion rather than delivery. A board helps because it reveals where work is stalled, but visibility alone cannot remove a bottleneck. The team still needs authority to reprioritize, resolve dependencies, or renegotiate what it has promised.

Change management behavior, not just team rituals, to make agility real.

Culture sets the ceiling. The book argues that transformations often fail not because Scrum itself is defective, but because an organization keeps its old command-and-control habits while adopting Agile vocabulary. Middle managers can either help teams self-organize and remove impediments, or continue assigning work, hiding information, and making decisions for them. The author cites a survey that identified cultural conflict, limited Agile experience, weak management support, resistance to change, and poor customer or product-owner availability as major adoption obstacles.

Change in increments. Begin by making current problems visible, agree on a value-oriented direction, and test changes with pilots. Involve leaders and teams, learn from each cycle, and adjust. A transformation is not a rollout date. It is a sustained shift in how decisions, feedback, and responsibility move through the organization.

Analysis

This reframes transformation as a change in power and information, not a training campaign. If managers remain responsible for every task assignment, teams cannot develop the autonomy the new process expects. At the same time, labeling managers as obstacles is too simple: role changes can create genuine uncertainty, so coaching and clear decision boundaries matter. A pilot is valuable when it tests those organizational conditions, rather than merely showing that a team can hold meetings.

Track flow and customer outcomes, never turn team metrics into employee scores.

Measure for a decision. The book defines a useful metric by three questions: what is measured, how it is measured, and why the result matters. Teams can track lead time, throughput, defects, code quality, and work-in-progress. A Cumulative Flow Diagram shows how much work sits in different workflow states over time. If one band grows wider, a bottleneck may be forming; if incoming work outpaces completed work, the backlog is expanding.

Keep metrics in their lane. Velocity helps a team forecast its own future capacity; it is not a fair basis for comparing teams or judging individuals. The author similarly warns against tracking employee time as a performance score. Metrics should help teams test whether a process change improves quality, delivery, or customer satisfaction, not reward people for producing more activity.

Analysis

A metric is useful when it changes a decision. Flow measures can expose delay that individual effort reports miss, especially when a task waits in a queue rather than being actively worked. But measurement can distort behavior if leaders attach rewards to a narrow target. A shorter cycle time, for example, is not an improvement if it comes at the cost of quality or pushes difficult requests aside. Pair speed measures with outcome and quality checks.

Keep Scrum events tied to decisions, working increments, and visible follow-through.

Give each event a job. A daily Scrum should help the team coordinate toward its sprint goal and surface impediments, not become a long status report to a manager. A sprint review lets customers and stakeholders inspect the actual product and respond; it is more than a presentation. A retrospective examines how the team worked and produces a small number of improvements that are tracked, rather than a wish list that disappears after the meeting.

Keep the operating basics intact. Teams need a prioritized product backlog, an available product owner, stable timeboxes, and an agreed definition of done. Planning is still necessary in Agile, but detail can be refined as the team learns. Design and documentation are also not forbidden; they should be appropriate to the work, including regulatory or operational needs.

Analysis

The events are valuable as feedback mechanisms, not because a calendar says they must happen. A review without a customer cannot reliably validate whether the increment is useful; a retrospective without tracked actions cannot show whether the team learned. The same distinction applies to daily meetings: identifying a problem is not the same as solving it, so follow-up conversations should involve only the people needed. Discipline is useful when it protects purpose, not when it preserves ceremony for its own sake.

Adopt practices your culture can sustain, then raise the maturity bar.

Assess before prescribing. The Kanban Maturity Model, or KMM, maps more than 130 practices to organizational maturity levels. Its purpose is to guide adoption, not award a high score. Teams assess current practices and cultural values, identify barriers to the next level, and create a practical improvement route. The book warns against overreaching: introducing advanced practices before the supporting values and capabilities exist can provoke resistance and make the changes short-lived.

Use assessment as a conversation. The Agile self-assessment similarly rates practices such as visible work, customer participation, sustainable pace, testing, and retrospectives. Its goal is to identify areas for improvement, not to maximize a score. Involving the whole team, including customer representatives where relevant, makes the results more useful than a checklist completed by management alone.

Analysis

Maturity models can turn vague ambitions into a sequence of observable changes. Their strongest use is diagnostic: they help a group ask what it can support now and what capability is missing. Their danger is treating the level as a label for people or departments. A low score may reflect unclear authority, unavailable customers, or funding constraints, not a lack of effort. The assessment should lead to a specific experiment, not a ranking exercise.

Bring customers into the work early enough to prevent expensive surprises.

Feedback beats assumption. In the author's insurance-software example, teams discussed designs with the product owner, demonstrated components while developing them, and accepted a story only when its acceptance criteria were met. The team worked in 15-day sprints and reported completing 90 percent of stories in sprints, with some reaching 100 percent. Business value shaped backlog order, and customer feedback could correct misunderstandings before release.

Adapt the channel to the customer. A law-enforcement customer may have little time for lengthy documents or meetings. The case recommends concise stories, sharply prioritized requests, brief presentations, and deliberate efforts to reach the right stakeholder. It also describes a small feature release before the usual sprint cadence as a way to build engagement. The principle is not to avoid communication, but to make it precise and workable.

Analysis

Customer participation is not a courtesy added to delivery; it is part of how a team discovers whether it is building the right thing. Frequent demonstrations shorten the distance between a mistaken interpretation and its correction. Yet availability is a real constraint, especially in security-sensitive or operational settings. Teams need a reliable decision-maker and concise feedback channels, rather than assuming that more meetings automatically create better collaboration.

Make resilience visible through portfolio priorities, dependency capacity, and deliberate slack.

Look beyond one team. Portfolio or upstream Kanban makes strategic initiatives, priorities, and cross-team dependencies visible to both leaders and delivery teams. The book finds that weak implementations often become reporting boards: work-in-progress limits are ignored, ownership is unclear, and teams face constant interruptions. Stronger efforts involve senior leaders, shared board rules, training, and multiple levels of work, from strategic planning to execution.

Reserve capacity honestly. One example uses a partner team's historical weekly output to offer three levels of capacity: 15 items treated as highly dependable, 26 as its average, and 44 as a rare peak. The point is to make dependency commitments reflect observed delivery, not optimism. The book also argues that resilience needs some operational slack, clear priorities, and responsibility close to the problem, especially during crises.

Analysis

Resilience is a property of the connections between teams, not just the stamina of individuals. A portfolio view can explain why a local team is waiting and help leaders make trade-offs across services. Historical capacity bands also communicate uncertainty more honestly than a single promised number. However, buffers should be designed, not treated as idle waste: the organization needs to know what risk the reserve protects against and when it is appropriate to use it.

Analysis

This is a field guide rather than a single, tightly argued theory. It combines implementation stories, maturity checklists, ceremony advice, SAP production procedures, and a large exam-question section. The central thread is that Agile methods only create value when the work system changes: priorities become visible, teams limit unfinished work, customers give usable feedback, and leaders relinquish some command-and-control behavior. The book is strongest when it links that argument to specific operating problems. In the aviation support case, work assignment and hidden queues contribute to delays; Kanban changes the flow and the reported lead time falls. The insurance example shows how product-owner access and demonstrations can reduce surprise and support acceptance.

The book also usefully distinguishes tools from outcomes. A Jira board, burndown chart, or stand-up is not evidence of agility by itself. A board that exposes stale work, a review that changes priorities, and a retrospective whose actions are tracked have a stronger claim. Its warnings about velocity-based appraisal and employee surveillance are especially important because measurement can redirect effort toward what is easy to count.

The source is broad and practical, but its examples are not controlled comparisons. The aviation and tobacco case outcomes are persuasive illustrations, not proof that the same method caused every reported gain or will reproduce it elsewhere. Some guidance also treats particular Scrum roles and ceremonies as broadly necessary, while the book recognizes contexts where Kanban or Scrumban may fit better. Readers should therefore use its checklists as prompts for inquiry, not universal rules. The most durable lesson is to identify the actual constraint, choose practices that address it, and inspect whether customer value, quality, and sustainable delivery improve together.

Summary in 30 Seconds
Choose Scrum for work with a clear near-term goal, Kanban for shifting demand, or a deliberate mix. Limit unfinished tasks so teams can resolve blockers and complete work; one support team reduced average ticket lead time from about 25 business days to 10. Use metrics such as lead time and throughput to improve the process, not rank employees. Customer feedback, engaged managers, visible priorities, and realistic capacity commitments help sustain delivery.
Contains spoilers

Last updated:

Report Issue
Want to read the full book?

Glossary

Kanban Maturity Model

Organizational improvement guide

A model for guiding the adoption of Kanban practices according to an organization's current practices and cultural values. It maps more than 130 practices to maturity levels and helps organizations assess their current condition, identify barriers, and plan suitable next steps. Its intended use is evolutionary improvement, not maximizing a score or imposing advanced practices prematurely.

Work-in-progress (WIP)

Work started but unfinished

Work that has begun but has not reached completion in a workflow. Kanban teams make WIP visible and may set limits on how many items can occupy a stage or system at once. Limiting WIP helps reduce multitasking, reveal bottlenecks, and encourage completion before new work is started.

Cumulative Flow Diagram (CFD)

Work states over time

A stacked chart showing the amount of work in different workflow states over time, such as backlog, in progress, and done. Changes in the width of a state can reveal growing queues or bottlenecks. Teams can also use the diagram to observe work arrival and completion patterns and support forecasts.

DEEP

Backlog quality guide

A description of a healthy product backlog: items are detailed appropriately, estimated, emergent, and prioritized. Higher-priority items are usually refined more than distant items, estimates are relative, and the backlog changes as learning occurs. Ordering should make priority clear rather than leave several items competing equally for attention.

Agilefall

Waterfall habits inside Agile

The book's term for an Agile transition that retains traditional Waterfall controls and assumptions. Examples include translating sprint backlogs into detailed Gantt schedules or treating Agile iterations as miniature sequential phases. The term highlights a mismatch: teams adopt Agile labels while continuing to plan and manage work in ways that limit adaptation.

Scrum-ban

Scrum and Kanban blend

A hybrid approach combining selected Scrum structures with Kanban's flow-based work management. It can suit event-driven or unpredictable work, or teams moving from Scrum toward Kanban. The book describes WIP limits, pull-based task selection, and planning on demand as useful practices, while noting that the team should choose the blend to fit its work.

Download PDF

To save this AGILE in Practice summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.27 MB     Pages: 14

Download EPUB

To read this AGILE in Practice 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.32 MB     Pages: 15
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...