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 Project Management

Agile Project Management

Managing for Success
A manager rejected a smart swap of sprint work because the plan had changed. What went wrong?
by James Crowder 2014 80 pages
3.50
6 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Agile succeeds when managers trade command for active facilitation

Change the manager’s job. Agile is not simply a faster development method. It changes how management works: teams adapt plans as they learn, while managers build trust, clear obstacles, connect stakeholders, and keep the product’s purpose visible. The manager remains responsible, but does not dictate every technical choice or treat every deviation from an early plan as failure.

A case makes the mismatch plain. Two teams rearranged equivalent work between sprints so one could use a capability sooner. Their manager objected because the original plan had changed, then asked for a more rigid version of an approach meant to accommodate change. The problem was not the teams’ adjustment. It was a management model that treated flexibility as disobedience.

Analysis

This distinction resembles the difference between managing a stable production line and coordinating work under uncertainty. When the destination is clear but the route is not, control over every move can slow the discovery of a better route. Facilitation is not passivity: it requires decisions about priorities, constraints, resources, and escalation. The case also reveals a useful test for an organization’s agile claims: when teams make a transparent change that protects the product, does management examine its value, or punish the fact that the plan moved?

Give developers real autonomy, then define where coordination is essential

Bound freedom with purpose. Crowder and Friess describe a team member’s Locus of Empowerment as the sense of where they can make decisions and act independently, and where they must coordinate with others. Developers need room to solve assigned problems without constant supervision. They also need clear boundaries because separate teams are building parts of one integrated product.

At the start of a project and each sprint, managers should clarify overall goals, team commitments, individual responsibilities, and feedback expectations. This is not bureaucracy for its own sake. A developer can act confidently when they know what decisions are theirs, what requires collaboration, and how their work contributes to the customer’s outcome. Empowerment is an ongoing adjustment, not a one-time declaration of trust.

Analysis

The useful distinction is between autonomy over methods and alignment on outcomes. Research on motivation often links agency with stronger engagement, while coordination research shows that interdependent work still needs shared expectations and timely information. Agile teams need both: too little discretion makes people wait for permission, while too little coordination creates incompatible components. The book’s framing is especially practical because it asks managers to make decision boundaries explicit. Those boundaries should be revisited when a sprint’s work or dependencies change.

Treat self-organization as a trained capability, not a personality trait

Teams need practice. Self-organization means that a team coordinates its work and roles rather than waiting for a manager to assign every task. The authors warn that teams do not automatically become good at this. Without preparation, confident or forceful personalities may dominate, while quieter members hold back important concerns. Past experiences with blame or failed projects can also make people wary of taking responsibility.

Managers can help by making expectations transparent, helping members understand each other’s strengths, inviting dissent, and addressing conflict before it hardens into mistrust. Accountability should focus on learning and results, not punishment. In the authors’ list of common team failures, mistrust, fear of conflict, weak commitment, avoidance of responsibility, and neglect of results reinforce one another. Self-organization needs deliberate support against these habits.

Analysis

Self-organization is often mistaken for the absence of leadership. In reality, teams need conditions that let useful coordination emerge: psychological safety, clear goals, and fair ways to resolve disagreement. Psychological safety, a concept in organizational research, means that people can raise concerns without expecting humiliation or retaliation. It does not mean avoiding standards or difficult feedback. The book’s emphasis on training is important, though managers should be cautious about reading quietness or disagreement as dysfunction. Different communication styles can conceal expertise as easily as disengagement.

Keep sprint teams stable enough to build trust and working knowledge

Continuity saves attention. When people stay together across sprints, they learn one another’s strengths, working habits, and areas of expertise. They can spend less time rebuilding relationships and explaining context, and more time developing and integrating the product. Frequent team changes can disrupt this shared rhythm, particularly when new members have different assumptions about responsibility and decision-making.

The book treats team instability as a source of uncertainty, or entropy, in the development process. It offers a model that estimates how personnel changes can reduce measured Agile Earned Value; one example assigns a 29 percent reduction after several team moves. That figure depends on the model’s assumptions, not a universal law. The durable lesson is simpler: avoid unnecessary reshuffling, and plan carefully when a change is unavoidable.

Analysis

Stable membership supports what team researchers call shared mental models: overlapping understandings of who knows what, how work fits together, and what signals require attention. These understandings can make collaboration faster, particularly in complex work. Stability should not become a rule against bringing in needed expertise, however. A team can also become isolated or rely too heavily on particular individuals. The practical aim is continuity with intentional onboarding, documentation, and knowledge sharing, so necessary changes do not erase the context the team has built.

Use short feedback cycles to catch costly misunderstandings while they are small

Demonstrate, then adjust. Traditional development often postpones working software until major milestones. If requirements change late, the change can ripple through plans, budgets, and interdependent components. Agile breaks the work into sprints, commonly described in the book as two to six weeks, with working software and stakeholder feedback at the end of each cycle. Teams can then reprioritize before too much effort accumulates around an outdated assumption.

Sprint length should fit the work. A very short cycle may yield little that can be meaningfully evaluated; a long one can bundle too many capabilities and delay learning. The authors suggest roughly 30 to 45 days as a reasonable duration in many cases, while emphasizing that complexity, team capability, and project context matter. Keep the cadence steady, demonstrate useful work, and move promptly into the next planning cycle.

Analysis

Frequent demonstrations turn assumptions into observable evidence. This is a form of feedback control: compare what the system does with what users need, then adjust the next action. The same logic appears in experimental science, where quick tests can expose a weak hypothesis before it becomes an expensive commitment. But feedback is valuable only when stakeholders can respond and teams can act on what they hear. A calendar full of reviews is not agility if decisions remain fixed or the demonstrated product is too incomplete to judge.

Keep architecture visible so sprint-level freedom produces one coherent system

Adapt within a design. Agile does not mean that teams can ignore architecture. The authors argue that a shared system design is especially important when many teams are building connected components. Architecture gives developers a common picture of how their work fits together, while remaining open to change as new information arrives. Systems engineering must keep that design aligned with what teams are actually building.

A large launch-vehicle project in the book used twelve teams, including two working off-site. Architects met regularly to review the system design, while the teams worked in a shared physical environment or connected remotely. The visible design helped keep the overall system in view as the teams developed separate parts. The point is not that every project needs one giant room or daily architecture meetings. It is that integration requires active coordination, not optimism.

Analysis

This is a classic tension in complex systems: local teams need room to optimize their components, but local improvements can harm the whole if interfaces and dependencies are neglected. Architecture functions as a shared map, not a frozen blueprint. The book’s example illustrates the value of making that map accessible and revisiting it as the product evolves. A useful caution is that coordination rituals can become overhead if they do not resolve real dependencies. The right level of architectural governance depends on how tightly coupled the components are.

Build collaboration into tools, records, and team spaces

Tools should preserve context. A laptop and coding software are not enough for a team that needs to share designs, decisions, tests, and lessons across locations and sprints. The book calls for integrated tools that help manage backlogs, planning, demonstrations, retrospectives, releases, and the artifacts behind the software. Developers also need ways to capture and share ideas, not just management dashboards that track tasks.

The authors envision an Electronic Engineering Notebook: a digital record that captures, connects, and publishes project information, including decisions and technical work. This addresses a recurring risk in fast development: knowledge stays in private conversations or scattered files, then disappears when people move on. Tools should support the team’s working habits and preserve useful context. Introducing unfamiliar software mid-project, however, can disrupt the very rhythm it is meant to improve.

Analysis

The deeper issue is organizational memory. Teams make many small choices that shape a system, and a task board alone rarely explains why those choices were made. Capturing context can reduce repeated debates and make distributed collaboration more reliable. At the same time, more documentation is not automatically better. Records become valuable when they are easy to maintain, searchable, and tied to actual decisions or artifacts. Tool selection should therefore be judged by whether it improves shared understanding, rather than by feature count or the appearance of control.

Measure demonstrated software and team health, not lines of code alone

Choose measures that fit the work. Traditional Earned Value Management compares planned work, completed work, cost, and schedule against a detailed baseline. The authors argue that this approach can mislead agile projects when plans are expected to change. In their failure case, a project used sprint meetings and a backlog but retained a rigid waterfall schedule. Managers reported reassuring cost and schedule indicators while teams built capabilities that the customer no longer needed. The project was cancelled after the mismatch became visible.

Their proposed Agile Earned Value Management System emphasizes working, integrated software, customer feedback, team effectiveness, and product quality. It also treats changes in team membership and defect patterns as warning signals. These measures can help managers investigate instability, but they should not be mistaken for exact forecasts. The authors’ entropy-based calculations depend on assumptions that need validation in each setting.

Analysis

Metrics do not merely describe a project; they influence what people prioritize. If code volume or schedule compliance becomes the main target, teams can optimize those numbers while missing customer value. This is a familiar measurement problem across organizations: a proxy is useful until it becomes a substitute for the outcome. Demonstrable software offers a more direct signal, but it still needs context, including usability, reliability, and whether stakeholders find it valuable. The proposed entropy metrics are best treated as diagnostic prompts, not precise evidence of a predictable percentage loss.

Count team sustainability and inclusion as part of delivery success

A product is not the whole result. A project can meet its cost and schedule targets and still damage the organization if the team is exhausted, divided, or unwilling to work together again. The authors define the manager’s responsibility broadly: facilitate teams, support customer collaboration, monitor progress, and create conditions where people can contribute and learn.

That includes making room for different experience levels, cultures, and communication styles. A team with senior and junior developers can exchange hard-won knowledge and newer techniques, but only if neither group assumes the other has nothing to teach. The same applies across cultural differences. Inclusion is not simply assembling diverse people; it means ensuring they can be heard and that expertise, rather than volume or status, shapes decisions. Sustainable pace and team capability matter beyond one delivery date.

Analysis

This wider definition of success connects project management to the long-term health of an organization. Teams carry knowledge, relationships, and future capacity from one project to the next, so burning them out can create costs that a project ledger misses. Diversity can broaden the perspectives available for solving problems, but its benefits are not automatic. Unequal voice, stereotyping, or poor coordination can prevent those perspectives from being used. Inclusion therefore requires concrete practices, such as inviting contributions and making decisions transparent, rather than relying on diversity as a label.

Analysis

Crowder and Friess make a management argument more than a procedural one: agile development cannot be installed by adopting sprint meetings, software tools, or a new label for an old schedule. It depends on a shift in authority and attention. Managers must allow teams to adapt their work while preserving accountability for customer value, integration, and quality. The case studies dramatize the cost of violating that bargain. One manager rejects a sensible exchange of sprint work because the plan changed; another keeps familiar performance measures while overlooking what the teams are actually building. In both cases, control rituals create confidence without creating understanding.

The book is strongest when it connects technical delivery to human conditions. Team continuity, trust, transparent goals, mentoring, and inclusion are not decorative concerns added after engineering. They affect how quickly a team can surface risks, share context, and integrate work. Its insistence that architecture remains necessary is equally important: adaptability without a system-level view can produce components that work locally but fail together.

The weakest point is the precision suggested by some proposed Agile Earned Value and entropy calculations. The text gives numerical estimates for the effects of team changes, but the excerpt does not establish that those values generalize across organizations or project types. Such metrics can focus attention on instability, but their outputs should be tested against observed outcomes and treated as uncertain estimates. More broadly, no single measure captures whether software is useful, maintainable, affordable, and delivered by a team capable of continuing the work.

The book’s central practical test is therefore not whether a project follows a branded method. It is whether its management system makes learning visible and usable. Working demonstrations, honest retrospectives, timely stakeholder decisions, and clear responsibility provide stronger evidence of agility than terminology does. The manager’s authority remains important, but its value lies less in preserving an early plan than in enabling coordinated adaptation without losing the purpose of the system.

Summary in 30 Seconds
Agile fails when managers keep command habits: they must facilitate, remove obstacles, and still answer for customer value. Give developers autonomy inside clear boundaries, and train self-organization instead of assuming it. Keep teams stable, since reshuffling erodes trust and context. Use sprints of roughly 30 to 45 days with working demos, keep a shared architecture, and measure working software and team health, not rigid baselines. Sustainability and inclusion count as delivery success.
Contains spoilers

Last updated:

Report Issue

Review Summary

3.50 out of 5
Average of 6 ratings from Goodreads and Amazon.

Unfortunately there are no reviews available for Agile Project Management based on the information provided. The document indicates there are 0 reviews and an overall rating of 0 out of 5 stars on Goodreads. Without any actual reader reviews or ratings, a meaningful summary of reviews cannot be generated for this book at this time.

Your rating:
4.18
48 ratings
Want to read the full book?

Glossary

Locus of Empowerment

Where decision-making authority sits

A way of describing how a team member understands their ability to make choices and act within a team. It includes awareness of individual strengths, role, and independence, as well as recognition of when work depends on teammates or management. In the book, empowerment is continually adjusted as sprint needs and team relationships change.

Locus of Control

Beliefs about personal influence

An individual’s belief about whether events are shaped mainly by their own actions or by outside forces such as other people, circumstances, or chance. The book applies this idea to agile teams: a developer’s sense of what they can influence affects initiative, information seeking, and accountability. Managers should clarify which decisions individuals can control and where coordination is required.

Agile Earned Value Management System (AEVMS)

Agile-focused progress measurement

The authors’ proposed approach to assessing agile project progress and effectiveness. In contrast with traditional Earned Value measures based on a fixed plan, it emphasizes integrated working software, customer feedback, team effectiveness, quality, and changing conditions across sprints. The proposal also considers team and defect volatility, although its formulas require careful validation before being treated as predictive.

Entropy of Team Volatility (ETV)

Uncertainty from team changes

A proposed measure of uncertainty introduced when team membership changes during an agile project. The authors use an entropy-based model to estimate how personnel moves may affect future Agile Earned Value. The concept highlights a plausible operational risk: new members and reshuffling can interrupt trust, shared context, and established working rhythms. Its numerical estimates depend on the model’s assumptions.

Software Defect Entropy

Variation in normalized defects

A proposed way to track changes in software defects across successive sprints after accounting for differences in sprint complexity. The authors expect defect levels to decline as teams gain familiarity with the system and one another. An increase in normalized defects is treated as a possible signal of disruption or process problems that warrants investigation, rather than proof of a particular cause.

Electronic Engineering Notebook

Shared project knowledge record

The authors’ envisioned digital version of an engineering notebook, designed to capture, connect, and share project information. It would preserve technical artifacts and context, including ideas, requirements, designs, and decisions, across people and teams. Its purpose is to strengthen collaboration and organizational memory, rather than simply store files or display management status.

About the Author

No information is provided about the authors James A. Crowder and Shelli Friess in the given documents. The author section is empty, so there are no details available about their backgrounds, qualifications, other works, or areas of expertise. Without any biographical information or context about the authors, a summary cannot be generated. More data would be needed to provide any substantive information about the authors of this book on Agile project management.

Download PDF

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

Download EPUB

To read this Agile Project Management 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: 18
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 25,
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...