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
Manage Your Project Portfolio

Manage Your Project Portfolio

Increase Your Capacity and Finish More Projects
Your teams are busy, but projects stall. Learn to finish valuable work without adding capacity.
by Johanna Rothman 2008 240 pages
3.72
200 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Manage the whole queue so teams finish valuable work before starting more.

The starting problem was overload. After a customer canceled a contract, one engineering organization was cut to about forty people while still facing a major release and urgent field problems. Everyone was assigned to everything, and little got finished. The manager first limited people to two projects a week, then organized small teams around one problem at a time. As problems were resolved, teams returned to the release and made visible progress. The lesson: a project portfolio is not a master wish list. It makes the organization choose what to work on now, what to defer, and what not to do.

Finished work creates options. A portfolio is the ranked flow of work through teams. Its purpose is to help deliver useful product, not to make a beautiful plan. Starting fewer projects can mean completing more, which frees capacity to respond to customers and changing conditions.

Analysis

What's striking is the reversal of a familiar managerial instinct: keeping everyone busy is not the same as making the organization productive. Queueing theory helps explain why. When work arrives faster than teams can complete it, unfinished items accumulate, waiting grows, and urgent interruptions become more likely. A portfolio gives that overload a visible form and makes tradeoffs discussable. Yet focus is not a universal cure: genuine incidents and market shocks still demand response. The advantage is not eliminating surprise, but making the cost of each interruption explicit instead of pretending every request can be first.

Give teams focus, not fragments of people scattered across projects.

Limit work in progress. Work in progress, or WIP, is work that has started but is not complete. The more projects compete for the same people, the more time is lost switching context and waiting for scarce specialists. Rothman argues for assigning intact, cross-functional teams to a small number of projects, ideally one at a time, rather than spreading individuals across many assignments. In her experience, even two supposedly half-time contributors do not reliably add up to one full-time contributor when both are constantly switching tasks.

Optimize the flow, not utilization. A team may look less than fully occupied when it has room to finish and learn. That slack can prevent one expert from becoming a bottleneck and allow teammates to share knowledge. The goal is completed work across the organization, not every person appearing busy.

Analysis

This is a practical application of flow efficiency: judge the system by how quickly work moves from request to completion, rather than by how fully each worker is booked. In knowledge work, high utilization can create long queues because any delay at a specialist blocks several projects at once. The warning about fractional assignments is especially useful when managers treat people as interchangeable capacity units. Still, a single-project rule can be too rigid for genuine support duties or specialized work. The relevant test is whether the arrangement improves completed outcomes without creating hidden waiting elsewhere.

Inventory all work before arguing about priority or staffing.

Collect the work people forget. A useful first portfolio includes more than named projects. It also records periodic duties, ongoing responsibilities, emergency work, management tasks, and project work. Collect from the people doing the work, then place each item on a simple timeline. Be honest about what cannot be staffed; planned work is not a commitment. Cards or sticky notes help a group see and rearrange the same facts together.

Separate projects from programs. A project has a distinct objective and expected end. A program groups interdependent projects whose combined delivery creates substantial value. If several teams cannot release their work independently, their efforts may belong under one program entry. This makes dependencies visible and reduces the illusion that a manager can sensibly coordinate dozens of supposedly separate projects.

Analysis

The inventory step is a form of operational discovery. Organizations often debate priorities using an incomplete map, while invisible maintenance, interruptions, and coordination duties consume real capacity. Making those activities visible improves the quality of every later decision. Grouping interdependent efforts also resembles systems mapping: the value may reside in the relationship among deliverables, not in any one task. A caution is that categorization can become its own bureaucracy. The board should remain a decision aid, not an exhaustive time-accounting system that demands more maintenance than the work it clarifies.

Test whether each project deserves commitment before ranking its place.

Ask whether it belongs at all. Before deciding which project is first, ask whether the organization should do it. Remove work with no meaningful value. If an idea is uncertain, a short investigation may answer a specific question better than keeping it indefinitely on the active list.

Choose a real next step. For each remaining project, decide to commit, kill, or transform it. A commitment means supplying the people, money, and other essentials needed to make progress, not assigning a few distracted contributors and calling the project staffed. Killing means stopping the work, not merely announcing a cancellation while a devoted employee keeps going. A project that may matter under different conditions can move to a parking lot, a list reviewed separately from active work. Past spending alone is not a reason to recommit.

Analysis

Separating project selection from project ranking reduces a common decision error: comparing the relative merits of options before asking whether each option is viable or strategically relevant. The three-way decision also makes continuation conditional rather than automatic. This resembles staged investment, where a small initial commitment buys information before a larger commitment is made. The human cost deserves attention too. People may attach identity and career hopes to a project, so a clean cancellation requires communication and reassignment, not just a changed spreadsheet. A project can be stopped without treating its contributors as disposable.

Rank by value lost through delay, not by confident-looking forecasts.

Compare the cost of waiting. Cost of Delay estimates what the organization gives up when a project arrives late, such as missed revenue, customer adoption, or reduced customer retention. The estimate need not be exact to distinguish an opportunity worth pursuing from one that can wait. Teams should also count work that removes internal waste, such as better test automation or a faster build system.

One investment exposed the tradeoff. In a book example, a company estimated that delays across several releases could cost millions. It chose a two-week test-infrastructure effort costing about $200,000, which could address a six-week release bottleneck. Other ranking methods include assigning relative business-value points or comparing projects in pairs. Cost and return estimates remain uncertain, so use them to guide discussion, not to disguise guesses as precision.

Analysis

Cost of Delay turns prioritization into a comparison of consequences over time, rather than a contest over whose project has the most persuasive sponsor. It also makes enabling work legible: infrastructure may have greater portfolio value than a customer-facing feature if it accelerates several releases. This is compatible with real-options thinking, where a modest investment can preserve or unlock future choices. The limitation is that delay costs can be hard to estimate and may privilege measurable revenue over less quantifiable obligations. Teams should expose assumptions and include customer risk, compliance, and strategic learning where they matter.

Make portfolio choices with peers, then protect the agreement from overrides.

Choose for the organization. No single manager sees every customer, dependency, and constraint. Portfolio decisions therefore need the people who can explain project value and the leaders who can commit the organization. Participants should state the principle behind their rankings, such as protecting a key product or reducing customer waste, rather than defend a project merely because it belongs to their department.

Publish what changes. A useful evaluation meeting reviews project evidence, ranks the work, decides what to commit, kill, or transform, and publishes the result and next review date. The book describes how competing incentives can make peers fight for their own projects, and how a senior leader can derail a decision by arriving late with a new preference. Clear authority, shared goals, and a visible ranking help keep the agreement meaningful.

Analysis

Portfolio governance is a political process in the constructive sense: it allocates scarce collective capacity among competing interests. Shared principles shift debate from personal positions toward reasons others can assess, while public decisions reduce the space for informal priority changes. Research on psychological safety and team learning also suggests that transparency works best when bad news is safe to report, not punished. Collaboration cannot substitute for authority, however. A meeting without decision-makers may produce a thoughtful ranking that nobody is empowered to honor. Both participation and a clear decision right are necessary.

Review every few weeks or months, using working evidence and small bets.

Set a review rhythm. Review the portfolio often enough to respond to market or customer change, but not so often that teams cannot complete meaningful work. Rothman recommends starting with at least quarterly reviews, with shorter cycles when work and markets change quickly. Agile teams can provide evidence at the end of timeboxes, which should be no longer than four weeks in the book's guidance.

Fund in stages. A review should consider completed work, progress, obstacles, and remaining value. Funding projects incrementally allows leaders to continue, change, or stop based on evidence rather than sunk cost. The author advises against committing more than half the organization to a project for more than three months without visible results. Even when annual budgets remain, allocating funds in shorter periods can make decisions more adaptive.

Analysis

A review cadence is a control loop: observe results, compare them with the current strategy, and adjust the next allocation. Short feedback cycles reduce the duration of an incorrect bet, while stable commitments within each cycle give teams room to work. This balances adaptability with the danger of managerial thrashing. The appropriate interval depends on the speed of external change and the time needed to produce meaningful evidence. A two-week review is not automatically superior to a quarterly one if the work cannot yet reveal useful information.

Track finished customer value and blocked flow, never individual busyness.

Measure usable progress. The central evidence is completed, tested work that a customer could use, not documents, optimistic status colors, or a person's apparent activity. Teams can track their own velocity over time, along with WIP, cycle or lead time, obstacles, backlog change, and cost when funding decisions require it. Velocity belongs to a particular team and should not be used to rank teams against one another.

Make impediments visible. A cumulative-flow view shows how much work is accumulating in different states. A growing queue or repeated delay may reveal unfinished testing, technical debt, missing expertise, or excessive work in progress. Individual productivity measures invite gaming and ignore the collaborative work needed to produce a complete feature. Use measures to find and remove obstacles, not to punish the people reporting them.

Analysis

This measurement philosophy distinguishes activity from outcomes and treats metrics as instruments for learning. It aligns with Goodhart's law: once a measure becomes a target, people can optimize the number while damaging the result. Team-level measures are less misleading because software delivery depends on coordination, testing, and integration, not just individual output. Yet even a completed feature count can be gamed through trivial slicing. Measures need a qualitative check: did the work solve a user problem, and did it leave the product in a releasable state?

Write a mission specific enough to reject work and align units.

Make purpose operational. An actionable mission names what a group delivers, for whom, and the benefit. It sets boundaries, helping managers identify work that belongs and work that should be declined or escalated. A mission such as delivering working tools to medical staff so they can treat patients today guides choices more clearly than an abstract promise to provide excellence. Strong verbs and plain language make the mission easier to use.

Connect strategy to delivery. If senior leaders have not supplied a useful mission, a group can examine its actual work and draft one, then test it with its manager and peers. At enterprise scale, business units first make their portfolios and decision principles visible; leaders then reconcile differences against the broader strategy. This combines local knowledge with organization-wide direction instead of imposing a single spreadsheet from above.

Analysis

A mission is valuable here not as a slogan, but as a decision rule that narrows the set of plausible work. That makes strategy observable in everyday allocation choices. The book's bottom-up and top-down approach also addresses a real design tension: local units know their customers, while enterprise leaders see cross-unit dependencies. A mission can still become a shield for departmental preference if it is too broad or untested. Its practical quality is revealed by whether it helps people explain both what they will do and what they will leave undone.

Analysis

The book's central argument is that project overload is not mainly a scheduling defect. It is a failure to govern demand against finite capacity. When leaders keep adding projects without stopping anything, the organization accumulates unfinished work, hidden dependencies, and urgent interruptions. Rothman's portfolio is therefore both a prioritization device and a public agreement about which work receives attention for a defined period.

Its strongest move is shifting attention from individual utilization to system throughput. A fully occupied specialist may look efficient while blocking several teams; a team with room to collaborate may finish more. This challenges the intuitive but often damaging assumption that every available hour should be assigned. The practical sequence is coherent: expose all work, decide which efforts deserve commitment, rank the survivors, staff them as complete teams, and revisit decisions using demonstrable output.

The method also makes strategy concrete. A mission is useful when it can exclude requests, not merely inspire employees. Likewise, a ranking has value only if leaders with authority honor it. That political dimension matters: portfolio tools cannot overcome incentives that reward managers for defending local projects, nor can metrics compensate for a lack of trust. The framework has limits. Cost of Delay is a useful comparison, but uncertain estimates can reflect power and optimism as much as economics. A strict focus on near-term deliverables may underweight research whose value is distant or difficult to demonstrate. The book partly addresses this through timeboxed exploration, but organizations still need explicit room for learning and maintenance. Its most durable principle is not that all work must be agile or that every team must work on exactly one project. It is that capacity, uncertainty, and strategic value should be made visible together, so tradeoffs become deliberate rather than disguised as multitasking.

Summary in 30 Seconds
Starting more projects does not create more capacity; it creates switching, queues, and unfinished work. Inventory all commitments, reject work without sufficient value, and staff a few chosen projects with intact teams. Compare projects by the value lost through delay, treating estimates as uncertain guides. Review choices at least quarterly, fund in stages, and track tested customer-ready work, work in progress, and obstacles rather than individual busyness.
Contains spoilers

Last updated:

Report Issue

Review Summary

3.72 out of 5
Average of 200 ratings from Goodreads and Amazon.

Manage Your Project Portfolio receives mixed reviews, with an average rating of 3.71/5. Positive reviews praise its practical advice on prioritizing projects, reducing multitasking, and improving team efficiency. Readers appreciate the book's lean principles and leadership insights. Some find it essential for software managers and product teams. Critical reviews mention lack of depth, repetitiveness, and over-reliance on agile methodologies. The book is seen as a good introduction to project portfolio management, particularly useful for those new to the concepts.

Your rating:
4.3
107 ratings
Want to read the full book?

Glossary

Project portfolio

Ranked organizational work

A ranked view of the projects an organization has committed to, alongside work it may consider but has not staffed. It helps leaders decide what receives capacity now, what waits, and what should stop. Unlike a product roadmap, it compares work across the organization rather than ordering features for one product.

Cost of Delay

Value lost through lateness

The expected value an organization loses when delivery is delayed. It may include postponed revenue, reduced customer adoption, or costs created by waiting. Rothman recommends comparing projects with estimates that are useful enough to distinguish relative urgency, while recognizing that the numbers are uncertain and should not be mistaken for precise forecasts.

WIP, Work in Progress

Started, unfinished work

Work that has begun but is not complete. High WIP spreads attention across unfinished tasks, increases waiting and context switching, and makes it harder to respond to new information. Limiting WIP encourages teams to complete work before starting more, improving visibility into both progress and bottlenecks.

Commit, kill, or transform

Three project decisions

The three possible portfolio decisions for a project that has been evaluated. Commit means provide the resources needed to proceed. Kill means stop the work, not merely remove it from a report. Transform means change the project, its scope, team, or approach to improve its fit or prospects.

Program

Interdependent projects grouped

A collection of projects whose combined delivery creates significant value. Individual projects may have some benefit, but their interdependence or shared release goal means the total outcome matters most. Treating related projects as a program makes dependencies and coordination responsibilities visible in the portfolio.

Minimum marketable feature (MMF)

Smallest valuable feature

The smallest piece of functionality that has value to a customer. An MMF can be completed and, where appropriate, released independently. Organizing work around MMFs supports shorter feedback cycles and lets teams and managers make decisions based on finished value rather than partially completed project activity.

Timebox

Fixed work period

A fixed period in which a team plans to complete a defined amount of work. At the end, the team reviews what is finished and uses the result to inform future planning. Rothman recommends timeboxes of no more than four weeks, with two weeks often preferred, and emphasizes delivering usable work within them.

Velocity

Team completion rate

A measure of how much work a particular team completes over time, often recorded across iterations. It can help that team understand its capacity and make near-term predictions. Velocity is specific to the team and its work, so it should not be used to compare teams or judge individual productivity.

Resource efficiency

Maximizing individual utilization

An approach that tries to keep each person or specialist fully occupied, often by assigning partial effort across several projects. Rothman contrasts this with flow efficiency, which focuses on completing work across the system. High individual utilization can create queues and bottlenecks that delay the organization's overall output.

FAQ

What is "Manage Your Project Portfolio" by Johanna Rothman about?

  • Project Portfolio Management Focus: The book centers on how to organize, visualize, and prioritize all the work your team or organization undertakes, aiming to increase capacity and finish more projects.
  • Agile and Lean Principles: Rothman integrates agile and lean methodologies to help teams deliver value frequently and adaptively, using real data for decision-making.
  • Collaboration and Leadership: Emphasizes that managing a project portfolio is a collaborative, leadership-driven process that aligns work with organizational mission and strategy.

Why should I read "Manage Your Project Portfolio" by Johanna Rothman?

  • Solve Multitasking and Throughput Issues: The book provides practical solutions for teams struggling with too many simultaneous projects and low completion rates.
  • Make Better Project Decisions: Offers tools and frameworks to help you decide which projects to commit to, kill, or transform, focusing on maximizing value.
  • Improve Organizational Health: Shows how effective portfolio management can align projects with strategy, improve morale, and reflect the overall health of your organization.

What are the key takeaways from "Manage Your Project Portfolio" by Johanna Rothman?

  • Commit/Kill/Transform Framework: Use a triage approach to decide the fate of each project, ensuring resources are focused on the most valuable work.
  • Ranking by Value: Apply methods like Cost of Delay and business value points to collaboratively rank projects and prioritize staffing.
  • Collaboration and Transparency: Build trust and foster open communication across teams and management to optimize organizational value.

How does Johanna Rothman define project portfolio management and its importance?

  • Comprehensive Work Overview: Portfolio management involves collecting and visualizing all types of work—projects, ongoing tasks, emergencies, and management work.
  • Strategic Alignment: Ensures that all projects and efforts are aligned with the organization’s mission and strategic goals.
  • Continuous Adaptation: Encourages regular review and adaptation of the portfolio to respond to changes in strategy, market, or project progress.

What are the main agile and lean approaches recommended by Johanna Rothman for portfolio management?

  • Frequent Value Delivery: Agile and lean enable teams to finish and deliver small, valuable increments of work, providing feedback for portfolio decisions.
  • Adaptive Management: These approaches support changing priorities and project transformations based on real progress and evolving business needs.
  • Visual Controls and WIP Limits: Use tools like kanban boards and limit work in progress to improve flow, transparency, and team focus.

How does "Manage Your Project Portfolio" by Johanna Rothman address multitasking and emergencies?

  • Limit Multitasking: Advocates for teams to focus on one or two projects at a time to increase throughput and morale.
  • Portfolio-Driven Emergency Management: Regular portfolio reviews help identify and reduce emergencies by prioritizing and addressing technical or management debt.
  • Lean Pull Systems: Implement pull systems to ensure teams complete current work before starting new tasks, reducing overproduction and chaos.

What methods does Johanna Rothman recommend for ranking and prioritizing projects in a portfolio?

  • Collaborative Ranking: Involve peers and stakeholders in ranking projects to ensure balanced perspectives and shared commitment.
  • Cost of Delay and Value Points: Use quantitative methods like Cost of Delay and business value points to prioritize projects based on impact.
  • Pairwise Comparison and Elimination: When value points are hard to assign, use pairwise comparisons or elimination tournaments to determine project priority.

How should organizations create and visualize their first project portfolio according to Rothman?

  • Collect All Work: Gather every type of work within your influence, including ongoing, emergency, and management tasks, for a complete picture.
  • Use Physical Tools: Start with sticky notes or index cards to visualize work by week and by person, making it easier to discuss and adjust.
  • Organize by Programs: Identify interdependent projects and group them into programs for more effective management and oversight.

What are the best practices for collaboration and decision-making in project portfolio management from Rothman’s perspective?

  • Build Trust: Foster trust by delivering on promises, being consistent, and practicing integrity to enable effective collaboration.
  • Define Principles and Mission: Clearly articulate the principles behind project ranking and align decisions with the organizational mission.
  • Structured Portfolio Meetings: Hold agenda-driven meetings to review, rank, and make commit/kill/transform decisions, ensuring transparency and shared understanding.

How does Johanna Rothman suggest organizations handle transparency, information sharing, and zero-sum thinking?

  • Promote Transparency: Encourage open sharing of progress, velocity, and backlog information to enable informed portfolio decisions.
  • Overcome Information Hiding: Address resistance to sharing status by demonstrating the benefits of visibility for throughput and emergency reduction.
  • Shift from Zero-Sum to Organizational Goals: Move the focus from individual project wins to collective organizational success, reducing internal competition and fostering collaboration.

What are common traps and mistakes to avoid in project portfolio management according to Rothman?

  • Confusing Value and Effort: Don’t mix business value points (value) with story points (effort), as this leads to poor prioritization.
  • Ignoring Risky Projects: Avoid excluding high-risk projects, as they may offer significant opportunities; manage risk incrementally.
  • Misusing Roadmaps: Don’t treat the portfolio as a product roadmap; the portfolio optimizes work across the organization, not just for a single product.

How does "Manage Your Project Portfolio" by Johanna Rothman recommend scaling portfolio management and measuring success in large organizations?

  • Balance Top-Down and Bottom-Up: Combine detailed project-level data with high-level strategic alignment across business units for effective scaling.
  • Address Silos and Incentives: Tackle challenges like functional silos and misaligned incentives by adjusting compensation and organizational structures.
  • Measure Team Throughput: Track running, tested features, velocity, and work in progress at the team level, avoiding individual productivity metrics for more meaningful insights.

About the Author

Johanna Rothman is a consultant, speaker, and author specializing in high-technology product development management. She provides pragmatic approaches to hiring, project management, risk management, and people management. Rothman is known for her direct communication style and unconventional humor. She writes a monthly newsletter called the Pragmatic Manager and maintains three blogs: Managing Product Development, Hiring Technical People, and Create an Adaptable Life. Her non-fiction work offers straightforward advice for complex problems, while her fiction features strong, intelligent female protagonists. Rothman's expertise helps managers, teams, and organizations become more effective in their operations.

Download PDF

To save this Manage Your Project Portfolio summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.38 MB     Pages: 20

Download EPUB

To read this Manage Your Project Portfolio 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.40 MB     Pages: 25
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...