Many medical device organizations have invested heavily in Agile teams, Scrum, DevOps, and incremental delivery. Yet at the portfolio level, work is often still managed the old-fashioned way: define projects, approve budgets, lock scope and dates, assign people, and then spend the next year explaining why reality did not cooperate. 

That creates a basic mismatch: Agile teams operating inside a non-Agile portfolio. And eventually, the portfolio wins. 

The Trouble with Project-Oriented Portfolios 

Projects have their place. Regulatory submissions, product launches, remediation efforts, manufacturing transfers, and other initiatives may have very real deadlines and very repeatable patterns that lend themselves to a defined process. The problem is when projects become the default way to organize investment, people, and decision-making. 

A project-oriented portfolio tends to ask: What projects should we approve? What will they cost? When will they finish? Did we deliver the promised scope? 

Those questions often drive detailed commitments at exactly the point when we know the least. They can also create a strange pattern where long-lived products are repeatedly funded through short-lived projects. The project ends. The product, customer needs, technical debt, cybersecurity responsibilities, and regulatory obligations somehow do not get the memo. 

Shift the Focus from Projects to Products 

A more Agile, product-oriented portfolio asks a different question: 

Where should we invest our capacity to create the greatest customer and business outcomes? 

That shift matters. Long-lived products and value streams become the organizing construct. Significant opportunities move through a visible portfolio flow and are evaluated against strategy, customer need, economics, risk, regulatory considerations, and available capacity. 

Instead of approving work once and hoping for the best, leaders regularly decide whether to continue, adjust, increase investment, reduce investment, or stop. That is portfolio agility in practical terms. 

Why This Matters in MedTech 

Medical device organizations rarely suffer from a shortage of important work. New products compete with sustaining engineering, cybersecurity, platform modernization, quality improvements, regulatory commitments, technical debt, manufacturing needs, and the occasional “urgent strategic priority” that appeared Tuesday afternoon. 

When everything is important, the portfolio’s job is not to make everything fit. It is to make the tradeoffs visible. 

An Agile Portfolio uses mechanisms such as Portfolio Kanban, capacity guardrails, strategic priorities, and frequent investment decisions to limit work in process and protect the organization’s ability to deliver. When something genuinely urgent enters the system, the conversation changes from “Can the teams squeeze this in?” to “What are we choosing not to do?” 

That is a much healthier question. 

Agile Doesn’t Stop at the Team Level 

Frameworks such as the Scaled Agile Framework (SAFe®) and others address this challenge through Lean Portfolio Management, connecting strategy, investment, governance, and execution. But the terminology matters less than the behavior. 

If leaders continue to overload the system, lock scope too early, constantly shift priorities, and measure success primarily by project completion, even excellent Agile teams will struggle. 

You can make every development team in the company Agile. But if your portfolio can’t change its mind, your organization still can’t. 

Portfolio Assessment 

Targeting 12 questions…That is enough to distinguish a genuinely agile portfolio from one that has simply added some agile vocabulary to traditional project governance, while still being a 4–5 minute assessment. Also making the answer choices behavioral rather than “strongly agree/disagree”; leaders tend to score themselves more accurately when they have to recognize what their organization actually does. 

How Agile Is Your Portfolio? 

A 5-Minute Assessment for Medical Device Leaders 

Your development teams may be Agile. Your portfolio may even use words like epics, value streams, and strategic priorities. 

But how quickly can your organization actually change where it invests its money and capacity when the evidence changes? 

Answer these 12 questions based on how your organization usually operates today, not how the process says it is supposed to operate. We promise not to tell your PMO. 

For each question, select the answer that best describes your organization. 

Scoring: A = 1 point | B = 2 points | C = 3 points | D = 4 points 

1. How is most product development work organized? 

1. Around temporary projects with defined scope, budgets, teams, and end dates.  

2. Primarily around projects, although some teams remain together across projects.  

3. Primarily around long-lived products, with projects used for specific initiatives when appropriate.  

4. Around long-lived products/value streams with stable capacity and clear ownership of outcomes. 

2. How are major investments funded? 

1. Detailed project business cases are approved individually.  

2. Annual budgets fund projects, with some flexibility during the year.  

3. Products receive ongoing funding, although significant initiatives may require separate approval.  

4. Leaders allocate capacity to products/value streams and adjust investment as strategy and evidence change. 

3. How does strategy influence portfolio decisions? 

1. Strategy exists, but individual projects often win based on sponsorship, urgency, or who has the best PowerPoint.  

2. Strategic priorities influence decisions, but connections to actual investments are inconsistent.  

3. Most investments are explicitly connected to strategic priorities and desired outcomes.  

4. Strategy provides clear investment guidance and is regularly used to start, adjust, or stop work. 

4. What happens when a new high-priority initiative appears? 

1. It gets added. Teams figure out how to absorb it.  

2. Leaders reprioritize, but existing commitments rarely disappear.  

3. Leaders explicitly evaluate what should be delayed or stopped to create capacity.  

4. Portfolio capacity and work-in-process limits make the tradeoff visible before new work enters. 

5. How much work is typically underway? 

1. More than available capacity can realistically support.  

2. Capacity is considered, but starting new work is still easier than stopping existing work.  

3. Leaders actively manage demand against available capacity.  

4. Portfolio flow and WIP are actively managed to protect focus, speed, and predictable delivery. 

6. When are major scope, cost, and schedule commitments made? 

1. Early, as part of project approval.  

2. Early estimates are expected to remain relatively stable even as teams learn more.  

3. Commitments become more specific as evidence and understanding increase.  

4. Leaders intentionally preserve flexibility early and make increasingly firm commitments as uncertainty declines. 

7. What happens when evidence suggests an initiative is no longer worth pursuing? 

1. We usually finish it. We already approved it, after all.  

2. Scope may be reduced, but stopping altogether is difficult.  

3. Leaders will stop or significantly redirect initiatives when evidence warrants it.  

4. Continue, pivot, increase, decrease, and stop decisions are normal parts of portfolio management. 

8. How are regulatory, quality, cybersecurity, sustainingability, and technical-debt needs handled? 

1. They compete project-by-project with new product development.  

2. Some capacity is planned, but urgent needs frequently disrupt product plans.  

3. Capacity is intentionally balanced across new development and these ongoing responsibilities.  

4. Portfolio guardrails explicitly protect capacity for the different types of work required to sustain safe, compliant products. 

9. How visible is the flow of major initiatives through the portfolio? 

1. Mostly through project plans, status reports, and leadership meetings.  

2. We maintain a portfolio list or roadmap, but flow and bottlenecks are difficult to see.  

3. Major initiatives move through a visible portfolio process from idea through implementation.  

4. Leaders actively manage portfolio flow, aging, WIP, bottlenecks, and decision points. 

10. How is success measured? 

1. Delivering approved scope on time and on budget.  

2. Delivery measures dominate, although business results are also discussed.  

3. Product and business outcomes are measured alongside delivery performance.  

4. Investment decisions are primarily informed by measurable customer, product, business, and strategic outcomes. 

11. How stable are the teams supporting important products? 

1. People are routinely assigned and reassigned as projects start and finish.  

2. Core teams exist, but staffing still changes significantly based on projects.  

3. Most products have persistent teams, supplemented when necessary.  

4. Stable, cross-functional teams own products/value streams over time and continuously build domain knowledge. 

12. How often does leadership reconsider portfolio investments? 

1. Mostly during annual planning or when something goes badly wrong.  

2. Quarterly reviews occur, but previously approved investments rarely change.  

3. Leaders regularly review priorities, evidence, capacity, and outcomes and make adjustments.  

4. Portfolio decisions are continuous enough that investment can move when strategy, evidence, risk, or market conditions change. 

Your Portfolio Agility Score 

Add your points for all 12 questions. 

12–21: Project Portfolio 

Your teams may be practicing Agile, but the portfolio is still largely optimized around approving and executing projects. Funding, staffing, and commitments are made early, making change expensive later. Start by examining how much work is underway and whether investment could be organized around long-lived products rather than temporary projects. 

22–31: Agile at the Edges 

You’ve introduced some portfolio agility, but traditional project behaviors still have a strong gravitational pull. Strategy, capacity, and outcomes influence decisions, but commitments and funding may still lock the organization into plans too early. Focus next on portfolio flow, explicit capacity tradeoffs, and making it easier to stop or redirect work. 

32–40: Product-Oriented Portfolio 

You’re operating substantially around products, outcomes, and capacity rather than simply managing a collection of projects. Leaders can make meaningful tradeoffs and adjust investments as evidence changes. Your opportunity is to strengthen feedback loops, outcome measures, and portfolio-level flow. 

41–48: Agile Portfolio 

Your portfolio behaves as a dynamic investment system rather than an annual collection of approved projects. Strategy guides investment, capacity constrains demand, products have durable ownership, and changing direction is considered good management—not evidence that somebody messed up the plan. 

The real test: When an important new opportunity appears tomorrow, can your organization fund it by consciously changing another investment—or does everyone simply get one more priority? 

The scoring is intentionally weighted evenly. The valuable diagnostic is the pattern of answers. Someone scoring well overall but answering A/B on questions 4, 5, and 7, for example, has a portfolio that talks a good game but still struggles to make hard economic tradeoffs. 

For an online version, let’s show the overall maturity level plus the three lowest-scoring areas and a short recommendation. That makes the result feel specific enough to be useful—and naturally creates a reason for the reader to want a deeper portfolio conversation.