Why Is Your Agile Program Still Slow? Many Agile Project Managers struggle to answer this question. Each of your teams works in Sprints. They have Product Owners, Scrum Masters, backlogs, Sprint Reviews, and Retrospectives. Each team meets their Definition of Done each Sprint. Velocity looks reasonably stable.

Yet, when you look at the larger program, something doesn’t add up.

Features still take months to reach customers. Releases are often delayed. Teams frequently wait for each other. Integration becomes a last-minute struggle. A feature that one team completed two Sprints ago is still not in production. I call this a classic “Watermelon Symptom.” Like a watermelon, things look bright and green on the outside. But when you cut open the watermelon (or the project!).  It’s all bright, scary red!!

The individual teams seem Agile. So why is the overall program still slow?

This is a challenge I frequently see in large Agile Programs. We often focus our efforts heavily on making individual teams Agile, while the bigger constraint sits between the teams.

Agile Teams Don’t Automatically Create an effective Agile Program

Imagine an e-commerce company developing a new one-click checkout capability. The Checkout Team finishes the customer interface in a Sprint. But it needs a new API from the Payment Team. The Payment Team, in turn, is waiting for security approval. Once that is complete, everyone needs an integration environment that is currently being used by another release.

Every team may be working efficiently. Each team may be following the Agile Mindset and Scrum Framework. But the customer is still waiting. This is an important mindset shift for Agile Project Managers: local efficiency is not enough to  create end-to-end flow. The real question is not simply, “How quickly is each team completing its work?” It is: “How quickly can we deliver value across the entire system?”

How Can You Improve End-to-End Flow Across Agile Teams?

One common cause of slow program delivery is the way teams are structured. Siloed teams with specialized work type (think a testing team or an API team ) is one of the key causes of delivery Issues in Agile Programs. As per The 17th State of Agile Report 37% of teams dissatisfied with Agile say that siloed teams causing delays in deliverables is  a key reason.

Consider a feature that requires work on the UI, APIs as well as the database. Often the orgs structure their teams around specialized work. This means they will have an independent UI team, database team, testing team and deployment team.

Then in this case usally the work moves like :

UI → API → Database → Testing → Deployment

Each team will be highly skilled and individually productive. But every handoff adds overhead and delay….

The API team may not have capacity when the UI team finishes.  The database team will have different priorities when the API team completes their work. Testing may be committed to another release. Deployment may happen only during specific windows.

This is why large Agile programs need to think carefully about team design, not just Scrum adoption at the individual team level.

Usually, practical, cross-functional Feature Teams that can deliver end-to-end customer value reduce handoff overhead and dependencies. Component, platform and specialist teams will often still be necessary—but smart organizations create those deliberately and thoughtfully rather than simply reflecting existing organizational silos

Why Shared Services Often Become Hidden Bottlenecks

Large programs often need specialist capabilities such as architecture, security, UX, compliance, data science, or infrastructure. These are costly skills. Also, we often do not need them all the time.

Creating shared teams for these skills usually appears efficient in theory.

But imagine ten Agile teams depending on the same security team.

Each delivery team works in two-week Sprints. But the security team works via a centralized queue. Suddenly, supposedly Agile teams are waiting three weeks for a review.

The individual teams are not necessarily the problem. The constraint usually appears at the system level.

Agile Project Managers therefore need to look beyond whether teams are completing their Sprint Backlogs. They need to ask where work queues up, where teams repeatedly wait, and which shared capabilities often become bottlenecks.

How your technology practices often increase Dependencies in your Agile Program?

Organizational structure is just one factor that exacerbates dependencies.  Technology constraints are another major issue.

A team often ends up waiting for another system, API, environment or dataset before they can complete their work.

For example, the Checkout Team is waiting  to test a new digital-wallet option because the Payment API is not ready. An AI team can’t validate its recommendation engine because historical customer data hasn’t been migrated yet.

Simply putting these dependencies on a program board makes them visible. But it does not make them disappear.

Sometimes the better solution is a change in technical approach: API-first development, mock services, automated environment provisioning, reusable components, or a more modular architecture are some of the technological approaches that help withto reduce dependencies.

As an Agile Project Manager, you need to empower your large Agile Projects/ Programs with right technology enablers

How the Metrics you track impact your large program delivery

Another reason slow programs can appear healthy is that we may be looking at the wrong metrics.

Suppose every team’s velocity is stable. Sprint burndowns look good and most teams regularly achieve their Sprint Goals.

Management sees green dashboards.

Yet a customer feature still takes twelve weeks to travel across the organization. – A classic watermelon!

Team-level metrics tell us useful things about individual teams, but they may not expose the delays or bottlenecks between teams.

At the program level, we need different questions (which means different metrics!):

• How long does it take for an idea to reach production?
• Where are the bottlenecks?
• Are queues growing between teams?
• How predictable are our releases?
• Which dependencies repeatedly delay delivery?

Measures such as lead time, Cumulative Flow Diagrams, and release predictability provide a view of program health.

The objective is not to create more metrics. It is to measure what helps us understand end-to-end delivery.

How can you reduce dependencies in your Agile Program?

When programs struggle with dependencies, the natural response is often to improve dependency management.

We create dependency logs, program boards, coordination meetings and design escalation mechanisms.

These are useful. Dependencies must be visible and actively managed.

But there is a more powerful question: Can we remove  this dependency altogether?

Could we create a more cross-functional team?

Could a commonly required capability become a reusable service?

Could we split a large feature into smaller, more independent increments?

Could teams use mock APIs instead of waiting for another team?

Could architecture become more modular?

Could an approval or environment provisioning process be automated?

Good Agile program management doesn’t only coordinate dependencies better. It continuously looks for opportunities to reduce the number of dependencies the organization creates in the first place.

Snehamayee’s View

What Does This Mean for the Agile Project Manager?

This is where the role of the Project Manager changes significantly in an Agile environment.

The Agile PM should not become a person who simply collects status from multiple Scrum teams and combines it into a program report.

Their perspective needs to be broader.

They need to see patterns that individual teams may not see: recurring dependencies, organizational bottlenecks, shared-service constraints, integration risks, vendor delays and program-level flow.

They facilitate conversations across teams, make dependencies visible, escalate systemic impediments and help teams and leaders find ways to simplify the delivery system.

In other words, the Agile PM increasingly moves from managing individual activities to enabling the overall system to deliver.

Why Should You Stop Asking Whether Your Teams Are Agile?

Having ten Agile teams does not automatically give you an Agile program.

You can have excellent Scrum Masters, empowered Product Owners and teams that consistently complete their Sprint Goals—and still have a slow delivery system.

Customers really don’t care how quickly each individual team completes its work.

They want to optimize the time it takes for the whole organization to turn an idea into a usable outcome.

So usually the most useful question for leaders and Agile Project Managers isn’t: “Are our teams Agile?” It instead is:

“How easily does value flow across our teams and reach the customer?”

That is where program agility really begins.

The post Why Is Your Agile Program Still Slow? appeared first on World Of Agile.

In this article, I will address What changes when you AI empower a Product.

When an Agile Professional thinks about AI, it is often as a “productivity enhancer”. We look at AI as something that can reduce our effort. AI indeed does that job. But more importantly, AI is rapidly changing  the products we use every day. For example, search engines summarize answers instead of simply displaying links. Business applications recommend actions instead of just presenting dashboards. Streaming platforms recommend what show you can watch next. Development tools generate code.  And now in addition, AI agents are beginning to execute tasks on our behalf.

It is tempting to look at this as simply another technology shift—similar to moving applications to the cloud or making them mobile-enabled.

But I believe the change is more fundamental.

When we add AI to a product, we don’t just change the technology behind the product. We often need to change entire product behavior

Traditional software was largely designed to follow predefined instructions. AI-empowered products can interpret, generate, recommend, reason, and, increasingly with Agentic AI coming in picture, these products can act.

As Agile Professionals or even Product Specialists, we need to understand how AI-empowered products transition from traditional data crunching and display to understanding impact. Read on the article to understand this shift better

From Executing Commands to Understanding Intent

Traditional software expects users to understand how the application works. The user performs action, and the Product or Software responds

Imagine booking a holiday using a conventional travel application. (Think MakeMyTrip or something similar) You, as the user, have to select a destination, enter dates, apply filters for price and hotel category, compare options, and gradually build your itinerary.

The application is very good at executing the instructions you provide. But it does not customize the itinerary for you.

Now imagine telling an AI-empowered travel application:

“We have five days in Sri Lanka. We enjoy wildlife and history, don’t want long drives and would like two days near a good beach. Suggest an itinerary.”

The user has expressed an intent, not provided a sequence of commands.

The AI needs to interpret that intent, understand the constraints, consider alternatives and generate an appropriate response.

This represents an important shift:

Traditional products ask: “What does the user want to do? / what steps will help the user”

AI-empowered products can increasingly ask: “What is the user trying to achieve?”

With this shift from user actions to user intention, we now need to rethink entire customer journeys rather than simply adding AI to existing screens.

From Deterministic to Probabilistic Behavior

This is another fundamental difference.

Traditional software is predominantly deterministic.

If a banking system is programmed to calculate interest using a particular formula, we expect the same inputs to produce the same output every time. Even if we make a mistake in the formula, the same wrong answer will be displayed every time

We can broadly describe this as:

Input → Rules → Expected Output

Generative AI does not always behave this way.

Ask an AI system to summarize a customer complaint twice, and you may receive two slightly different summaries. Both could be perfectly acceptable.

Ask it to recommend the next best action for a salesperson, and there may be several reasonable answers.

And occasionally, AI hallucinates. This means that the AI may produce an answer that sounds convincing but is simply wrong.

AI product behavior therefore looks more like:

Input + Context + Model → Probable Output

This has a huge shift in product behavior.

For many AI capabilities, we cannot simply ask:

“Did the system produce the correct answer?”

We also need to ask:

“How good was the answer?” (Was the itinerary suitable ?/Was the new show recommended by the streaming service relatable? / Did the AI-based customer agent really help the complainant)

This shift will eventually impact the entire product life cycle. It will change

• How we write requirements. – Now we will have to write requirements that capture how do we know if user intent was met?
• How we test the product.   –
• How we measure quality
• How we decide what is an acceptable range of correctness?
• Last but not least, how do we decide our feature is ready for release?

AI empowered Intent driven products will not be merely right or wrong – we need to find a way to capture if the user intent was fulfilled

From Fixed Expectations to Context-Aware Experiences

For decades, we have designed digital products with fixed expectations. You navigate a certain menu, click a certain button – each time same action happens. This is a fixed expected behavior. We discussed above that Intent makes a key shift from expected behaviors for AI – But Context is an equally important factor to consider

Imagine a project manager opening a portfolio dashboard. With a traditional, fixed-expectations product, she expects to scan each of his 20 dashboards daily. Maybe she even has an alert built in to highlight dashboards with “red” items. But in the end, that alert is based on a fixed set of rules

But when working with an AI-empowered, intent-driven dashboard, instead of examining twenty charts, the manager might ask:

“What has changed since last week, and which three things need my attention?”

For the product to answer well, however, it needs context.

What projects does this person manage? What happened last week? Which risks were previously discussed? What does this organization consider critical? What information is this person permitted to access?

We can now see that context is becoming an increasingly important part of product design.

The quality of an AI experience may depend not only on the model being used but also on what the product Context – What the Product knows, remembers and retrieves at the right moment.

From Providing Features to Providing Intelligent Capabilities

Consider a traditional sales application.

It may provide customer records, reports, dashboards, filters and alerts. These features help a salesperson understand what is happening. And using the information, the salesperson then makes a decision about which customers are likely to turn to a competitor product this month

Instead, an AI-empowered version of the sales application could possibly answer:

“Which of my customers are likely to turn to a competitor product this month and why? What can I do to reduce the impact?

The product is no longer simply retrieving or representing information.

It analyzes information, identifies patterns /trends and/or anomalies , and then recommends possible action.

We can see similar changes across industries.

A traditional HR product stores employee information. An AI capability may help managers identify recurring themes in employee feedback.

A project management product tracks tasks and dependencies. An AI capability may identify emerging delivery risks and suggest possible interventions.

A customer-support product displays previous interactions. An AI capability can summarize the customer’s history and recommend a response.

The conversation when we think about AI products moves beyond: “What features should our product provide?”

To Goes towards “What intelligent capabilities should our product have?”

From Assistance to Increasing Autonomy

AI products are also changing in another significant way: they can increasingly act.

Imagine an expense-management product. If we want to limit AI use to analytics, AI could identify unusual expenses. If we want to go ahead and provide recommendation abilities, AI could explain why an expense appears unusual. It could then recommend an action.

But an AI agent takes this even further. It could potentially investigate supporting documents, contact the employee for missing information, update the case and route it for approval.

The products are now going from providing intelligence to taking coordinated action toward an objective.

The difference between an AI that says “Here is what I recommend” and an AI that says “I have done it” is often the differentiator.

As products move along this spectrum, autonomy itself becomes a product-design choice. We need to decide what action an AI agent should be allowed to take and where we need to insist on human intervention. For example, it may be OK to have AI approve a standard insurance claim, but you may want AI to flag any unusual claims to human or maybe you want all rejections to be vetted by a human.  Going further you may want AI to suggest a possible diagnosis to a physician but never to a lay person.

The decisions on where AI acts and when it recommends… Or even what it can recommend what to whom are now the Product Design decisions

Products Can Now Fail in New Ways

Perhaps the most important shift in behavior appears when AI fails. Traditional software certainly fails. Applications crash, integrations break and calculations contain defects.

But AI introduces different kinds of failure. An AI system may misunderstand a perfectly valid request. It may generate information that doesn’t exist. (Hallucinations!).It may use outdated or inappropriate context. It may make a poor recommendation while sounding extremely confident. An autonomous agent may correctly execute an action that it should never have been allowed to take.

This creates an unusual situation: The software may be functioning exactly as designed, while the product is still producing an unacceptable outcome. Data – availability /correctness and retrieval will now impact a lot of outcomes . With data, we now have to worry about the data security / ethics

Concepts such as trust, uncertainty, boundaries, human oversight and acceptable failure increasingly important product considerations.

Snehamayee’s Perspective – Empowering your product with AI is more than adding an AI patch

The most common way people try to adopt AI is to see how it can make current work more productive. How can AI automate my MoM? Can we use AI write user stories / acceptance criteria or even code for me? How can AI write test cases and analyze test coverage?

A few people go ahead and try to incorporate AI in their products- what they do is to take an existing product and ask: “Where can we add AI?”

People may add a chatbot to their Product. Sometimes they add data summarization or trend analytics. They may even add recommendations. These certainly add value to the product.

But the more interesting question is:“If this product had access to intelligence from the beginning, would we design the product differently?”

Would users still navigate through ten screens? /Would they still analyze the dashboard themselves? /Would they still manually coordinate five different activities?

Or could the product understand their objective, assemble the necessary context, recommend an approach and—with appropriate safeguards—take some of those actions for them?

That is where AI stops being merely another feature and starts changing the product.

And this leads to an important question for those of us working in Agile product development.

If our products are becoming probabilistic, context-aware, adaptive and increasingly autonomous, can we continue building them exactly as we built deterministic software?

• Do our requirements need to change?
• What does “Done” mean?
• How should we test something when there isn’t always one correct answer?
• What new risks should teams consider?

And what does all of this mean for Product Owners, Scrum Masters and Agile teams?

Those are the questions I will explore next. while I do that please refer to this document for the design guideline when we build AI empowered Products

Because when the nature of the product changes, the way we build the product must evolve too.

The post What changes when you AI empower a Product appeared first on World Of Agile.

 Project Management for Traditional, Scrum or Kanban work

PMI says, Project management is the application of knowledge, skills, tools, and techniques to project activities to meet project requirements. For best outcomes, we need to vary our Project Management techniques by work type. Traditional work Vs Scrum or Kanban, all require different approaches

When people hear the word “Project Management”, they often think only about creating plans, tracking schedules, managing risks, coordinating teams, and ensuring that projects get delivered successfully. But should every type of work be managed in the same way? I believe that the answer is a clear “No”. Delivering a project with stable, well-understood requirements is fundamentally different from developing an innovative product where the solution emerges through experimentation. Both are different again from operational work where requests arrive continuously. This is why effective project management starts with understanding the nature of the work. Traditional project management, Scrum, and Kanban do not simply provide three different ways of organizing tasks. They address different types of work and therefore Project Management for Traditional, Scrum or Kanban work requires different approaches to planning, risk management as well as progress tracking. The role of the Project Manager changes for each approach.

Understand the Nature of the Work

Traditional project management works well for defined work, where requirements are relatively stable, and outcomes are known upfront. Usually, established practices already exist. Examples could include a server upgrade, hardware rollout, or SAP security patching. Because uncertainty is relatively low, detailed planning is both possible and useful. Scrum is designed to help with Complex or empirical work. When requirements are unstable or not clear, teams cannot know everything at the beginning. In such situations, requirements evolve through feedback. Trial and error helps to iterate to the right solution. Developing an AI-based demand forecasting solution or a new digital product are examples. Instead of attempting to eliminate uncertainty through more detailed planning, Scrum manages uncertainty through short iterations, feedback, inspection, and adaptation. Kanban is particularly useful for flow-based or operational work. Production support, incident management, service requests, and supplier tickets are some examples. In such work, we usually do not have a defined beginning and end. Work arrives continuously, and priorities do change frequently. Fast response to the changing priorities and incoming work is important. Deciding a Sprint Goal becomes quite difficult. The challenge is therefore to keep work flowing smoothly while avoiding bottlenecks and excessive Work-in-Progress (WIP). A simple way to remember the distinction is:

If the work can be is stable and can be predicted, plan it; if you need to learn while doing it, use empiricism; if work continuously arrives, optimize the flow.

Planning as per work type: Traditional, Scrum or Kanban work

Planning is necessary in all three approaches, but the purpose and horizon of planning change. In a traditional project, the primary planning question is: What work must we complete, and how do we deliver it on time and within budget? The Project Manager typically creates a detailed project plan covering scope, milestones, dependencies, resources, schedule, and budget. Tools such as the Work Breakdown Structure (WBS), Gantt charts, and milestone plans support this predictive approach. When we plan for predictive work, focus is on efficiency and optimization Scrum asks a different question: What is the most valuable thing we should build next, and what can we learn? Planning is adaptive and focuses on feedback. In such an environment, planning happens at multiple levels through the product roadmap, Product Backlog, release planning, backlog refinement, and Sprint Planning. Scope can and often does evolve as customer feedback and learning provide new insight. The objective is not simply to deliver everything originally requested, but to maximize customer and business value. When we are working with  flow-based or operational work, the planning  question is: What work should we pull next to ensure smooth flow and meet service expectations (SLA/KPIs)? In the flow based work, we continuously prioritize work based on demand, urgency, available capacity, and service expectations. Kanban boards, WIP limits, service request queues, and classes of service help while planning Kanban kind of work.

Thus, Traditional planning optimizes for predictability, Scrum focuses on planning for experimentation with focus on continuous outcomes and Kanban plans for optimizing the flow and removing bottle necks.

Risk Management: The Risk Itself Changes when work type changes

Risk management also differs as per the nature of the work. Traditional projects primarily face risk of execution not going as per plan. The concern is whether the team manages to deliver the agreed scope according to the plan. Schedule delays, missed dependencies, budget overruns, and scope creep are common risks. Project Managers rely on risk registers, dependency analysis, mitigation plans, contingency reserves, and formal change control. In Scrum, the dominant risk is uncertainty and rapidly evolving requirements. Are we building the right features? Will our customers user our prouduct? What if an assumed technical solution does not work? Scrum reduces these risks through short iterations, prototypes, rapid feedback, backlog reprioritization, and continuous learning. Kanban faces operational risk  . Growing queues, SLA breaches, excessive WIP, capacity constraints, and bottlenecks can quickly affect service. Teams use patterns like WIP limits, SLA monitoring, flow metrics, and bottleneck management.  These patterns help the teams to establish the flow.  

To summarize, Traditional approaches try to predict the risk and then analyze and control it.  Scrum emphasizes on learning based on feedback and then adapting and pivoting as needed. While Kanban focuses on detecting problems quickly, restoring flow, and continuously improving.

Tracking Progress differs for each work type: Are We on Plan, Creating Value, or Flowing?

Perhaps the clearest difference is visible in how progress is measured. In a Traditional project, the key question is: Are we on plan? Measures such as milestone completion, percentage complete, schedule variance, cost variance, Earned Value, SPI, and CPI help compare actual performance against the baseline. In Scrum, the more important question is: Are we creating value effectively? Sprint Goal achievement, working product increments, customer feedback, quality, value delivered, burndown, and velocity can provide useful information. Importantly, completing more work does not automatically mean creating more value. For Kanban, the question is: Is work flowing? Lead time, cycle time, throughput, WIP, work-item age, cumulative flow, and SLA compliance help teams understand whether work is moving efficiently through the system.

Success itself looks different for each work type: Traditional projects emphasize delivering scope, Scrum emphasizes delivering value, and Kanban emphasizes delivering flow.

With Changing work types, The Project Manager’s Role Must Change Too

One major misconception about Agile is that Agile does not need Project managers – well if the work needs managing, we need someone to manage the work. Read this article to understand why we still need a manager in Agile Projects. If planning, risk, and tracking change, the Project Manager cannot operate in exactly the same way either. In Traditional projects, the PM naturally spends significant effort planning, coordinating dependencies, monitoring schedules and budgets, managing risks, communicating status, and controlling deviations from the agreed plan. In an Agile environment, these responsibilities do not disappear—they are redistributed. The Product Owner, Scrum Master, team, technical leaders, and Project Manager may share responsibilities that traditionally sat with one PM. This requires an important mindset shift. Instead of focusing primarily on following the plan, focus on achieving the desired outcome. Instead of controlling change, respond effectively to change. We need to move from managing individual tasks to enable high-performing teams. Rather than measuring activity, we should measure customer value and outcomes. And instead of directing execution, facilitate collaboration and learning.

Snehamayee’s recommendation — Choose the Approach Based on the Work

Project Management for Traditional, Scrum or Kanban work is very different. Which is why, Traditional, Scrum, and Kanban should not be viewed as competing methods where one must always be better than the others. The better question is: What is the nature of the work we are trying to manage?

When work is predictable and well defined, detailed planning and control can provide tremendous value. On the other hand, when the work contains significant uncertainty and learning, Scrum’s empirical approach enables teams to inspect, adapt, and discover better solutions. Lastly in situations where work arrives continuously, Kanban helps teams optimize flow and responsiveness. Great project management is therefore not about rigidly following one methodology. It is about recognizing the type of work in front of us and adapting how we plan, manage risk, measure progress, and lead teams accordingly.

When we work at enterprise level Agile, it becomes important to recognize that often we will need to employ all 3 approaches within same large multi team Agile Project or Program based on what each specific team does – I explore this idea with more depth in World Of Agile Agile PM Skill Badge

The post Project Management for Traditional, Scrum or Kanban work appeared first on World Of Agile.

The Product Manager’s Role in PI Planning

This is a guide to understand the Product Manager’s role in PI Planning. As such, the article will describe what a Product Manager must do during PI planning. Read our earlier article about PI planning preparation to understand how to get ready for the event PI Planning is often described as the heartbeat of the Agile Release Train.  This event is more than a mere planning event. This is the event where the strategy gets validated against the practicalities of delivering realities.

 Product Managers Role in PI planning : The Value Gurdian

Product Managers act as a keeper of Value for the Agile Release Train- (ART). During the PI planning, a PM helps stakeholders and the teams to align, and decide what matters most, and how we will deliver it. This article will not go in depth about the PI Planning structure. This article in scaled agile website describes PI planning structure well. Here, I will talk about how a PM shows up—before and during the event—to make it actually work. Before PI Planning: What a PM must align before Day 1 Most of your impact as a PM happens before PI Planning starts. If you walk into Day 1 hoping alignment will happen in the room, you’re already late. Here I will share a few things you need to get in place early. First, stakeholder alignment. Business, Architecture, and Engineering should not be debating fundamental priorities during PI Planning. You don’t need perfect agreement—but you need enough clarity to move forward towards the intended objective Second, priority clarity. Your “Top 10” features shouldn’t be a vague wishlist. They should reflect real decisions—what makes it in, what doesn’t, and why. When you decide priorities, it is tempting to focus all your energies on the low-hanging fruit. Do not fall for the trap. Make sure to balance new features with Architecture runway. Third, dependencies. If there are known cross-team dependencies, start conversations early. Don’t wait for teams to discover them during breakouts. And finally, trade-offs. Go in with a point of view. If capacity doesn’t allow everything—and it won’t—what gives? Preparation is less about documents and more about decisions.

The Product Managers Core Role  During PI Planning

Once PI Planning starts, your role becomes very visible. At a high level, you need to

• Set the direction through the vision
• Balance priorities against capacity
• Negotiate scope when capacity, skill or dependency issues arise
• Work with stakeholders to get the Business Value (BV) numbers established
• Participating in risk management (ROAM)

What you’re NOT  responsible for is micromanaging team plans. A common mistake is trying to be everywhere and solve everything. That usually creates more noise than clarity. Your role is to anchor the conversation around value—and step in only when alignment is at risk.

Presenting the Vision: What You Must Bring to the Table

The vision presentation at the start of PI planning sets the tone for everything that follows. And it’s easy to get this wrong. Reading through slides won’t cut it. Teams need to understand:

• What are we trying to achieve this PI?
• Why does it matter?
• What are the few things we really care about?

The “Top 10 Features” matter—but not as a list. As a clear signal of priority. If everything sounds equally important, teams will struggle to make decisions later. Also, give guardrails:

• What does success look like?
• Are there constraints teams should be aware of?

  A good vision presentation helps the team with clarity about what they should focus on.

Supporting Teams During Breakouts

Breakouts are where the real planning happens. I have seen that, during the breakouts, many PMs either overstep or disappear completely. Both do not help. The balance is important. You’re there to:

• Explain focus and priority when teams are not clear
• Help negotiate scope as an when needed – This can be because
• Facilitate alignment across Product Owners

  You’re not there to dictate how teams should plan their work.

Participate in Draft Plan Reviews

Draft plan reviews are where the ART leadership (PM /RTE and system architect) first sit down with the teams to discuss the plan. This is not just a status update—it’s your chance to catch issues early. Look at:

• Team-level PI Objectives: Are the team-level PI objectives outcome-focused, or have the team just listed down the sequence of stories?
• Commitment levels: What’s committed vs uncommitted—and why? Have the teams created their commitment only on capacity basis or have they considered uncertainties like skill issues/technical feasibility and dependencies
• Capacity alignment: Are teams overloading themselves? Have they considered day to day overheads

Also, pay attention to dependencies. The ART planning board is your friend here. It helps you see where things might break before they actually do. It is often helpful to start the rough ART planning board in this segment. Don’t just listen to what teams present—look for what’s missing.

 Management Review & Problem Solving: Where PMs Shine

This is usually the most intense part of PI Planning. Plans don’t fit. They don’t look like what we had hoped for. Capacity is exceeded. Dependencies create friction. This is where a skilled and prepared PM makes a difference A good Product manager should come prepared with:

• Trade-off options, not just problems – Talk about what changes and trade offs can help us go closer to our earlier ambitions – be ready with a view on what can move out if something else must come in
• Ideas on how uncommitted work could become committed – what help you need?
• Stay firm on what can not really be done – do not set unrealistic expectations. It is critical to balance Business Urgency with team capacity and technical feasibility
• Champion the Architecture runway – do not lose focus on maintaining a balance with immediate feature value and being ready for what comes next

Assigning Business Value (BV): More Than a Number

Assigning Business Value often becomes a mechanical exercise. It shouldn’t be. This is where you help stakeholders understand what really matters. Once stakeholders really “see” what your teams will be doing – alignment is easy to follow A few things to keep in mind:

• Not everything can be “high value” – encourage stakeholders to show what matters most to them
• Explain Architectural runway  –  help the stakeholders truly sppericiate the impact they will have if teams ignore the runway completely in favor of only immediate value
• Explain Uncommitted objectives are not low priority and team will not be ignoring those—The uncommitted status reflects uncertainty

Use this moment to create shared understanding, not just assign numbers.

Common Pitfalls in PI planning

Some patterns show up very often. Good PMs take care to avoid these. Overcommitment is the big one. Planning at 100% capacity seems efficient—but it rarely works in reality. Plan adequate but transparent buffers to allow for unexpected Another anti-pattern of is to actually plan feature delivery work in the IP iteration – This will quickly kill both innovation and your planning for the next PI Then there’s the silent PM. Being unavailable or disengaged during PI Planning creates confusion quickly. Another one is ignoring architectural runway. It’s easy to deprioritize it in favor of visible features—but the cost shows up later. And finally, over-controlling. Trying to drive every decision slows teams down and reduces ownership. The goal is not control—it’s clarity.

How to be an effective PM during PI planning

Being effective during PI Planning isn’t just about what you know—it’s about how you interact during PI planning First, presence. You don’t need to be everywhere—but you do need to be accessible. Especially in high-risk discussions. Second, knowing when to step in. — Step in when teams are not clear about priorities. If they’re debating execution details—step back Third, reading the room. — Confusion, hesitation, repeated questions—these are signals that something isn’t clear. Fourth bring clarity to management and stakeholders – help them understand trade-offs —Discuss what can and can not be done — explain the need for innovation and architecture  runway Finally comes decision-making. — you will be asked to make a lot of decisions. You won’t have complete information. That’s normal. Some factors to consider are Value , risk , capacity and technical feasibility. Also consider face trade-offs: Short-term delivery vs long-term architecture or Business pressure vs technical reality Sometimes you push. Sometimes you adapt.

Conclusion: Bring enough clarity start execution

At the end of PI Planning, you’ll have a plan. But more importantly, you’ll have a level of alignment. The confidence vote is not about perfection. It’s about whether teams believe in what they’ve planned. Your role doesn’t end here. The plan needs to translate into a living backlog. Priorities need to hold—or be consciously adjusted. PI Planning is not about getting everything right upfront. It’s about creating enough clarity and alignment so that when things change—and they will—teams know how to respond. That’s what good product leadership looks like.  

The post The Product Manager’s Role in PI Planning appeared first on World Of Agile.

Being a Scrum Master for Multiple Teams: Why It Happens, What It Breaks, and How to Make It Work

Being a Scrum Master for Multiple Teams – Is it possible? Can it work? and rather “How to make it work?” – In almost every organization I’ve worked with, this question eventually comes up:

“Can one Scrum Master handle multiple teams?” And more often than not—the answer is already assumed to be yes.

Not because it’s ideal. But because it feels practical… It seems more efficient

Let’s be clear about why this model exists before we jump into whether it works.

Why Organizations Assign One Scrum Master to Multiple Teams

In my experience across large agile transformations, this decision usually comes from one (or more) of these reasons:

1. Budget Constraints

Agile transformations are often expected to be “lean.”

So instead of hiring one  Scrum Master per team, Organizations go for one Scrum Master for 2–3 teams. On paper, it looks efficient.

2. Misunderstanding the Scrum Master Role

This is still very common. Often leadership sees the Scrum Master as:

• A meeting facilitator
• A Jira admin
• A status tracker

Then naturally, they ask – “Why can’t one person handle multiple teams?”

3. “Senior = Can Handle More”

I’ve seen this especially with Senior Scrum Masters or Experienced Developers stepping into SM roles. The logic then becomes: “They’re experienced, so they should handle more teams.”

Experience does increase effectiveness. But it doesn’t multiply time or presence.

4. Mature Teams (At Least Perception of It)

Sometimes the assumption is: “These teams are “doing” Agile for long time now. They don’t need much support.” Sometimes this is true. But many times it’s just… optimistic.

When  Organizations Assign One Scrum Master to Multiple Teams

 – What Actually Happens?

Let me share something I’ve seen repeatedly. I once worked with an organization where one Scrum Master supported three teams.

• Team A was high-performing
• Team B was struggling with dependencies
• Team C was newly formed

Guess where most of the Scrum Master’s time went?

Team C (firefighting)
Then Team B (escalations)

And Team A? -They slowly drifted. Retrospectives became routine … Improvement slowed down ….Small issues went unnoticed

Nothing broke immediately. But growth stalled.

That’s the subtle risk in this model.

Challenges You Should Expect

Despite of all this, it is inevitable that you will have to look after more than one team at a time – Below I will give some challenges you should expect in the situation

1. Context Switching Is Real

Every team has:

• Different stakeholders and Energy
• Different maturity
• Different challenges (geographical distribution / domain complexities / cultural differences /product lifecycle stage.. etc)

Switching between them isn’t just logistical—it is a definite mental stress. And this stress builds up. Slowly but surely.

2. You May Move from Deep Impact to Surface Coverage

When you work with many teams, you run the risk of spreading yourself too thin. Then, instead of:

• Coaching behaviors
• Enabling ownership
• Driving systemic improvements

You may end up:

• Just Attending Events – and this is when the Scrum Events start to turn into mere “ceremonies”
• Focusing on the obvious, on the surface “blockers” – you now lack bandwidth to go deeper to seek and address the true impediments. Read this article to understand how (and more importantly – “why” to differentiate between blocker and impediment. 

3. Your Availability Becomes a Bottleneck

Teams don’t need you all the time. But when they do need you—it’s usually urgent. With multiple teams, you’re often:

• In another meeting
• Context-switching
• Or already overloaded

Slowly the teams start to normalize you being less available to them… and that often leads ti them accepting the waiting game.

4. Impediments Take Longer to Resolve

The real work of a Scrum Master is not in meetings or Scrum Events. It’s in:

• Following through
• Influencing stakeholders
• Removing systemic blockers

And that work suffers when attention is split.

5. Energy Drain (The Silent One)

When you are working as a Scrum master for more than one team, you are running from one meeting to other …

• Daily Scrum for Team  A
• Refinement sessions for Team B
• Reviews for Team C
• Retrospectives  for Team A

The cycle goes on and on without a break. This is where even experienced Scrum Masters start feeling stretched.

What Helps When One Scrum Master Is Supporting Multiple Teams

Scrum Guide says Scrum Master is accountable for helping the Scrum Team become more effective. When you work with multiple teams as a Scrum Master, that expectations will still remain. Below I have given some tips that help

1  Shared Product Context

If there’s one factor that significantly improves the chances of success in a multi-team setup, it’s this:  The teams are working on the same or closely related products. I’ve seen this make a huge difference.

When teams are aligned around:

• The same product
• A shared customer journey
• Interconnected features

The Scrum Master gains leverage:

• Better context retention (less mental switching)
• Stronger stakeholder alignment
• Easier dependency management
• More meaningful cross-team coaching

I once worked with three teams building different modules of the same platform.

Instead of treating them as separate units, we:

• Ran joint backlog refinement for shared features
• Aligned retrospectives occasionally to spot system-level issues
• Visualized dependencies across both teams

The result?

Less duplication
Faster decision-making
And significantly smoother flow

Compare that to supporting unrelated teams (say, one in payments and another in HR systems)—the cognitive load and disconnect are much higher.

So if organizations must assign one Scrum Master to multiple teams, product alignment is a powerful enabler.

2. Shift from “Team Scrum Master” to “System Enabler”

If you try to give equal time to all teams—you’ll struggle. Instead:

• Look for patterns across teams
• Solve problems at the system level
• Reduce recurring issues

This is where Kanban thinking (flow, bottlenecks) becomes incredibly valuable.

3. Be Intentional About Where You Go Deep

Not all teams need the same level of attention.

I usually ask:

• Which team is at risk?
• Which team can self-sustain?
• Where will my effort create the most impact?

Then I adjust accordingly.

4. Build Capability Inside the Team

One of the biggest shifts:

Stop being the center of everything.

Instead:

• Encourage team members to facilitate
• Build ownership of Scrum Events
• Develop internal champions

If everything depends on you—you won’t scale. Remember, as a Scrum Master you are accountable from Scrum Team effectiveness – and you are NOT accountable to do everything yourself

5. Make Retrospectives Non-Negotiable

If there’s one place to invest your energies deeply—it’s for Sprint Retrospectives

Even with multiple teams:

• Make every effort to keep retrospectives meaningful
• Focus on real actionable improvement items
• Follow through on actions

This is where the teams start being more effective.

6. Use Visualization to Your Advantage

Across teams:

• Visualize bottlenecks
• Highlight delays
• Track dependencies

When leaders see the system, conversations change. Teams delivering value is more important  than teams just “doing work”

7. Protect  Your Own Energy and bandwodth Ruthlessly

This is rarely talked about—but critical.

• Avoid stacking heavy sessions back-to-back – if you are not at your best, that will impact the value you bring to the table.
• Create thinking space (not just meeting space)  – create some bandwidth for your self to  just think
• Protect time for actual coaching work

You’re not effective when you’re exhausted.

Final Thoughts On Being a Scrum Master for Multiple Teams….

Being a Scrum Master for multiple teams isn’t about doing more.

It’s about:

• Establishing Synergy
• Empowering Teams
• Enabling systems
• And using context (especially shared product context) to your advantage

When done thoughtfully, this model can actually elevate the Scrum Master role from team facilitator to organizational change agent.

The post Being a Scrum Master for Multiple Teams appeared first on World Of Agile.

How to prepare for PI Planning: A Practical Guide from the Trenches

How to  prepare for PI planning? In Other words, do you have a checklist for PI Planning Readiness

When I help organizations with their SAFe journey, I often get a request, do you have a PI Planning Readiness checklist? That is the question I am planning to answer with this article

 Introduction: Why Preparing for Your First PI Planning feels overwhelming (and why it doesn’t have to be)

Getting ready for your first PI Planning often feels like tackling a mountain of scary and unclear work There are multiple teams that will participate, So many senior senior stakeholders to take care of , A lot of people have big expectations from SAFe  They are expecting measurable business outcomes from this PI and they want PI planning to ensure the magic.

Somewhere in the middle of all that, you’re expected to help “align everything.” It’s not surprising most people are a little (or a lot) overwhelmed.

I remember my first PI planning—I thought the challenge was ensuring that the two days go smoothly. It wasn’t. The real challenge was everything that what we should have done before those two days.

I am here to make that part clear…. Once you see PI Planning as a time and opportunity to get ready for the upcoming PI and not just an event. It then to starts to feel a lot more manageable. And honestly, a lot more valuable.

Common mistakes first-timers make as they Prepare for their First PI planning

The biggest mistake I see? Treating PI Planning as a two-day activity. By the time those two days begin, has already to be done already be done. PI planning is a time for Agile Teams , ART leadership, Management and Stakeholders to align their thoughts on what work we will do in the PI and how we will do it. It is not the time to start thinking fresh for the first time on what work we will do in the PI? Some other patterns tend to show up:

• People walk in without a clear sense of priorities  and the Goal
• Not considering Architecture Runway and having no idea about their percentage capacity allocation….
• Backlogs that are either over-detailed or completely unclear
• Major Dependencies only get discovered during breakout sessions
• There’s an expectation that the plan will be “final” and perfect

I’ve been in a PI where everything looked well-prepared on paper. We were so sure of our success in the PI . But on the ground, once the PI started, we realised we had not accounted for some day-to-day maintenance work we had to do… That kind of thing slows everything down.

PI Planning Preparation starts weeks before (not days before)

If you take away one thing from this article, let it be this: PI Planning wins or loses before it begins. Here is a simple checklist Few  weeks before: You focus in shaping the direction of the PI

• What is the business impact we are trying to achieve this PI?
• What are our top priorities for this PI?
• Who are the key stakeholders? Are they roughly aligned?

You don’t need all the answers—but you need a strong starting point. 1–2 weeks before: Now you start sharpening things.

• Understand  the top backlog items
• Start identifying dependencies
• Begin early conversations across teams

This is where most of the real alignment work happens. Final week: You’re not “building”—you’re checking.

• Are there any major gaps?
• Are stakeholders aligned enough?
• Do teams understand what’s coming?
• Any major dependencies

If you have been focusing in earlier week, it actually starts to feel easier at this time

Clarity on Vision, Priorities, and Outcomes is the Key To Success in PI Planning

A lot of PI Planning issues come down to one thing: unclear priorities. Not lack of effort. Not lack of tools. Just unclear direction. It is really not about detailing everything. It’s about being clear on what matters most. I’ve seen backlogs with 40 “top priorities.” That doesn’t work. Teams don’t need more items—they need clarity:

• What are the few things we really care about this PI?
• Why do they matter?
• What does success look like?

When the “why” is clear, teams make smarter calls during planning. When it isn’t, they fill in the gaps themselves—and that’s where misalignment creeps in.

 Get the Backlog Ready (without over-engineering it)

Many teams tend to overprepare the backlog. They want every story refined. Every detail thought through. Every i dotted and every t crossed.It feels responsible. It’s not always useful. What you actually need is a backlog that’s good enough to have a conversation. That means:

• The top items are clear
• There’s enough context to discuss
• Priorities are visible

That’s enough! Over-refinement can backfire. I’ve seen teams spend days breaking work down, only to rework everything once cross-team conversations begin. Also, don’t try to eliminate uncertainty. You won’t be able to do that. The goal is to surface it early, not pretend it doesn’t exist.

The fine line: Prepared enough vs over-prepared

There’s a point where preparation stops helping and starts getting in the way. You’ll notice it when teams spend more time polishing stories than actually talking about what needs to be built. It feels like progress—but it’s not always the kind that helps during PI Planning. I’ve seen teams walk in with extremely detailed backlogs—everything estimated, everything broken down neatly. And then within a few hours, half of it gets reworked because priorities shift or dependencies come up. Worse still, you notice people are not having conversations – they are merely ticking off the checklist… Assuming that things are already planned and “frozen!!”… That’s a dangerous assumption. It leads to people not speaking up even when they do notice something ….. Over-preparation usually shows up as:

• Too much detail too early
• Refining things that aren’t even top priority
• Trying to “lock” the plan before alignment actually happens

The intent is good—you want things to go smoothly. But PI Planning isn’t about validating a pre-built plan. It’s about building it together. Prepared enough means you’re ready for meaningful discussions—not that you’ve removed the need for them.

Align Stakeholders before the PI Planning

If there’s one thing that will derail your PI Planning quickly, it’s stakeholder misalignment. When Business, Product, and Architecture aren’t on the same page, it shows up fast—and publicly. Try to get ahead of that:

• Are priorities agreed upon?
• Are there known trade-offs?
• Is there any major disagreement that hasn’t been addressed?
• Last but not least – do they understand what PI planning is about?

You don’t need perfect alignment—but you do need enough alignment to move forward. The worst place to discover fundamental disagreements is in the middle of planning.

Prepare Teams (and not just the Product Owner) Before PI planning

A common pattern: Only the Product Owner is doing all the preparation work. The teams are waiting to hear from “somebody” to tell them what they will do next PI That does not help…. Teams need context. Without it, they’re starting the PI Planning in the dark. Before PI Planning:

• Share the vision and priorities
• Talk through key constraints
• Highlight known dependencies
• Explain high level stories /items
• Think about what other type of work team has to do (Build Architecture runway/deal with technical debt? / Handle some defects?) – a discussion about % capacity allocation goes a long way

This doesn’t have to be heavy. A short briefing, a walkthrough, even informal conversations go a long way. Also, make roles clear:

• Product  Manager sets direction
• Teams plan how to deliver and how much they can deliver
• Facilitators keep things moving
• Business validates alignment

When everyone knows their role, the event feels a lot less chaotic.

Logistics matter more than you think

This is one of those things you only appreciate after it goes wrong. If tools don’t work, if breakout rooms aren’t ready, if people can’t access boards—it drains energy fast. Check the basics:

• Tools are working and accessible
• You have set up the board 
• Breakouts are planned
• Considered the timebox

It sounds simple, but smooth logistics make a big difference to how the session feels.

 What “good preparation” actually looks like

Good preparation isn’t about having everything figured out. It’s about having enough context to plan…. Having the right people to Plan You’re in a good place when:

• Priorities are clear
• Stakeholders are mostly aligned
• Dependencies are visible
• Capacity  allocation and availability is understood
• Teams feel prepared—neither in dark  nor ready with a “frozen” plan.  If everything feels completely locked before PI Planning even starts, that’s usually a red flag—not a sign of readiness. You should still need the conversations.

Final checklist: Are you ready?

Before you start, do a quick check:

• Are the top priorities clear?
• Do you understand the high level business imperative for PI
• Is the backlog ready enough?
• Are stakeholders aligned?
• Have key dependencies been identified?
• Do teams have context?
• Are tools and logistics sorted?

If you’re ticking most of these, you’re in good shape.

Closing: PI Planning is a leadership moment

PI Planning very quickly exposes how things really work in your organization. It shows how well you align. How realistic your plans are. How clearly you communicate. It’s also a moment where leadership becomes appreant—not just in decisions, but in how well teams are set up to succeed. You don’t need a perfect plan. That’s not the goal. What you need is shared understanding, realistic direction, and teams that feel confident about what they’re committing to. Get that right, and PI Planning stops feeling overwhelming—and starts becoming genuinely useful

The post How to prepare for PI Planning appeared first on World Of Agile.

How a Scrum Master Can Help the Product Owner Succeed

Discover How a Scrum Master Can Help the Product Owner to succeed. Product Owners face complex decisions daily. Get some practical tips on how Scrum Masters elevate Product Owners. Learn how Scrum Masters empower Product Owners to move from reactive execution to value-driven delivery through coaching, flow practices, and better stakeholder collaboration. This article is a part of the series describing roles and responsibilities of the Scrum Master.

Introduction: Why does the Product Owner Need Support from The Product Owner?

The role of a Product Owner is far more demanding than it appears on paper. Scrum Guide says the Product Owner has to maximize value. As such this person sits at the intersection of market forces, stakeholders, and technology. In order to balance the three, they need to constantly make decisions that balance benefits, risk, and delivery. As a Product Owner you will end up doing some

• Constantly balancing competing stakeholder expectations
• Managing and refining an ever-evolving Product Backlog
• Making high-impact prioritization decisions with incomplete information
• Bridging the gap between product vision and team execution
• Handling pressure to deliver value quickly while ensuring alignment

In fast-paced and complex environments, this responsibility can quickly become overwhelming. This pressure often pushes Product Owners into working in a reactive mode rather than enabling strategic, outcome-driven thinking. This is where the Scrum Master becomes a critical partner. Beyond facilitating events, an effective Scrum Master enables the Product Owner through coaching, structure, and flow—helping them move from reactive execution to intentional value delivery. Below, I have articulated some key areas where the Scrum Master supports the Product Owner

What Can the Scrum Master Do To Help the Product Owner 

Teaching Scrum for Better Product Ownership

One of the most important ways a Scrum Master supports a Product Owner is through teaching Scrum. Product Owners usually operate in complex environments where misunderstandings about roles and expectations are common.  Scrum Master teaches Scrum to Product Owners, stakeholders and Developers

• Teaching Scrum to Product Owners – Product Owners often are used to working in traditional ways of working. Helping them understand and implement self-management helps Developers to deliver value more effectively. Of Course, this, in turn, helps the Product Owner- our value custodian
• Teaching Scrum to Developers – Similar to the Product Owners, Developers also need teaching and hand-holding to work in Scrum. This obviously helps them deliver value more effectively.
• Teaching Scrum to Stakeholders – Organizations usually are diligent about teaching to Developers and Product Owners. But we often ignore teaching Scrum to stakeholders. But Scrum represents a very different way of working for the stakeholders. Like the Product Owners, the stakeholders are often used to working independently in the traditional way of working. They are not used to working hand in glove with Developers and the Product Owner. We see this often when the stakeholders resist requests for frequent refinement sessions and regularly scheduled Sprint Reviews.

Thus, The Scrum Master helps the Product Owner—and the broader ecosystem of Developers and stakeholders—understand how Scrum works in practice. This includes reinforcing accountabilities, clarifying boundaries, and fostering a shared understanding of value delivery. When the Scrum Master helps to build this alignment, it helps the Product Owner to focus on Value delivery.

Facilitating Effective Product Backlog Refinement

Product Backlog refinement helps ideas evolve into actionable work. But, without proper facilitation, it easily becomes inefficient or unfocused. The Scrum Master helps to keep refinement sessions structured, time-boxed, and collaborative. They help the team focus on clarity, alignment, and readiness. This helps to ensure the backlog items are well understood and appropriately sized When Scrum helps with effective Product Backlog Refinement, the Product Owner can concentrate on defining what needs to be built Here are some tips to help with effective Product Backlog Management

 Strengthen the  Product Backlog Management

Effective backlog management is more than maintaining a list of user stories. It is  about continuously aligning work with value. Scrum Masters support Product Owners by introducing techniques such as story slicing, outcome-oriented thinking, and maintaining appropriate levels of detail. They help ensure that near-term work is clear while avoiding over-investment in distant priorities. The result is a backlog that remains dynamic, relevant, and value-driven.

Support Prioritization and Decision-Making

Prioritization is one of the most challenging aspects of the Product Owner role. Every decision involves trade-offs and invites in depth often conflicting discussions. The Scrum Master does not make decisions, instead they enhance decision quality. They introduce techniques like impact mapping, cost of delay, or WSJF. These techniques provide structured ways to evaluate priorities. This helps the Product Owner shift from reactive prioritization to more intentional and informed decision-making.

Enhance Stakeholder Collaboration

Stakeholders are essential to product success—but unmanaged interactions sometimes overwhelm the Product Owner. The Scrum Master helps design effective engagement models, ensuring that feedback is timely, relevant, and constructive. They facilitate meaningful Sprint Reviews and coach stakeholders on how to collaborate with the team. By creating structured communication channels, the Scrum Master enables better alignment without constant disruption.

Help the Product Owner to Align Product Vision with Outcomes

A common challenge for Product Owners is how to maintain an alignment between long-term vision and day-to-day backlog work. Scrum Masters help bridge this gap by encouraging outcome-driven thinking. They facilitate alignment with business goals, OKRs, or value streams, ensuring that backlog items contribute to meaningful outcomes. This strengthens the Product Owner’s ability to communicate direction and purpose.

Improving Flow and Delivery Predictability

Incorporating flow-based practices can significantly improve delivery outcomes. Scrum Masters help by introducing Kanban practices such as visualizing work, limiting work in progress, and tracking flow metrics like cycle time. These practices provide valuable insights into delivery patterns. For the Product Owner, this means better forecasting, clearer expectations, and more predictable delivery.

Removing Organizational Impediments

Product Owners face many challenges that go beyond the team level. Scrum Masters work to identify and remove these systemic impediments. Some examples are multi-team dependencies, governance delays, or organizational silos. Scrum Masters work within the organisational constraints and create an environment where the Product Owner can operate more effectively.

Fostering Strong Collaboration with the Team

Product success depends on collaboration between the Product Owner and Developers. Scrum Masters coach both sides to move away from a “handoff” mindset toward shared ownership. They encourage continuous dialogue, joint problem-solving, and active participation. This leads to stronger alignment and better outcomes.

Conclusion: Scrum Masters Help the Product Owner Succeed by enabling Product Success Through Partnership

Ultimately, the effectiveness of a Product Owner is deeply influenced by the support system around them—and the Scrum Master is central to that system. Scrum Masters go beyond facilitating Scrum events. A skilled Scrum Master elevates the Product Owner’s ability to think strategically, act decisively. They help the Product Owner collaborate effectively with Developers as well as Stakeholders. A Scrum Master combines coaching, facilitation, and flow-based practices to help shift Product Owners from reactive execution to value-driven delivery. This partnership can be a true force multiplier. When the Scrum Master and the Product Owners work in tandem, they go beyond delivering increments. Together, they enable outcomes, accelerate learning, and drive meaningful business impact.    

The post How a Scrum Master Can Help the Product Owner appeared first on World Of Agile.

Does Agile Need Project Managers? A Reality Check

Introduction: Agile and Project Managers

“Agile doesn’t need Project Managers.” Or “Project Managers are getting obsolete”

I often hear this statement. People often say this with conviction, sometimes with relief, and occasionally with confusion.

Over the last decade or so frameworks like Scrum and Kanban have become more famous. And that brought a shift away from traditional roles. Scrum, in particular, explicitly defines only three accountabilities: Product Owner, Scrum Master, and Developers. Scrum Guide does NOT mention a project manager at all.

And just like that, many organizations concluded: the Project Manager role is obsolete. We do not need Project Managers any longer…..

But is that the right conclusion ? — Or have we misunderstood what Agile is actually trying to change?

I do not plan to defend job titles in this article. Instead, I want to discuss and examine the ground reality. I want to talk about what actually happens in Agile projects beyond theory, certifications, and frameworks.

Where Did This Question Come From?

To understand the confusion, we need to go back to traditional project management.

In a traditional setup, the Project Manager was the central authority. This person was responsible to plan, track, report, manage the risk management, communicate with team and stakeholder and above all ensure value delivery.

With so much to do, project managers often became a bottle neck.

Agile challenged this model.

Instead of centralized control, Agile emphasized:

• Self-managed teams
• Collaboration over hierarchy
• Adaptability over rigid planning

In doing so, Agile (more specifically Scrum) didn’t explicitly include the Project Manager role.

Many interpreted  this as “no need for project managers.”

That’s a dangerous assumption and a myth!

While Agile removed the role as a command-and-control authority, it did not eliminate the responsibilities that ensure delivery.

What Agile Frameworks Actually do Say about Project Management

Now Let’s separate the myth from reality.

We saw that Scrum did not specifically ask for Project Managers

What Does Scrum Say about Project Managers?

Scrum defines accountabilities clearly—and Project Manager isn’t one of them. But Scrum operates at the team level. It assumes a relatively contained environment where a single team can deliver value incrementally.

It does not address:

• Cross-team dependencies
• Complex stakeholder landscapes
• Organizational constraints

Kanban and the Project Manager
Kanban goes even further. It doesn’t mandate specific roles at all. Kanban focuses on evolutionary change, improving  the flow via work visualisation, and limiting work in progress.

But again, it assumes a system where flow can be managed effectively. Someone still needs to ensure alignment, remove bottlenecks, and manage expectations. These days, roles emerge for flow management in kanban. Some common  roles are  the Service Delivery Manager (SDM)(who manages workflow and removes bottlenecks – similar to a Scrum Master), and the Service Request Manager (SRM) (who manages the backlog and prioritizes customer requests – like a Product Owner)

SAFe (Scaled Agile Framework) and the Project Manager

SAFe also does not have a designated role called a Project manager. However,  SAFe does include roles like  the Release Train Engineer, the  Product Manager, and the System Architect.

Question is Why?

Because at scale, coordination and alignment is critical. Dependencies multiply. Stakeholders increase. Complexity grows.

And suddenly, the need for overarching thinking becomes undeniable.

The Reality of Agile Projects on the Ground

In real organizations, Agile projects today rarely operate in isolation. They involve:

• Multiple teams working on shared outcomes
• Dependencies across systems and functions
• Stakeholders with competing priorities
• Pressure to deliver faster, with quality

Now ask yourself:

• Who ensures that all of this comes together?
• Who aligns teams when priorities conflict?
• Who manages risks that span across teams?
• Who communicates with stakeholders beyond the team level?
• Who takes accountability for multi team integrated delivery outcomes?

Self-organizing teams are powerful—but they are not designed to solve organizational complexity on their own.

 So Who Actually Does this Work?

Even in Agile environments, the following responsibilities don’t disappear:

• Stakeholder Management – Aligning expectations, managing communication
• Dependency Management – Coordinating across teams and systems
• Risk Management – Identifying and mitigating delivery risks
• Planning at Scale – Beyond sprint-level planning
• Delivery Accountability – Ensuring outcomes, not just outputs

What happens on ground? These responsibilities are often:

• Distributed
• Unclear
• Or silently pushed onto Scrum Masters, Product Owners, or senior team members

This creates confusion—and sometimes, burnout. Read this article to understand the Scrum Accountabilities and what happens when we ask people to wear multiple hats  

The Emergence of the Agile Project Manager

In many organizations, something interesting happens. The role doesn’t disappear—it evolves. The title may not be “Project Manager” anymore. Instead, the new title can be:

• Delivery Manager
• Program Manager
• Agile Project Manager
• Release Train Engineer

But the essence remains the same:
Someone is responsible to connect the dots.

When you assume the title of an Agile e Project Manager, you do not assume a command-and-control authority.

Instead, you become a

• A Facilitator of alignment
• A Enabler of flow
• A Manager of complexity

and

• An Influencer without formal authority

When Agile Projects Fail Without Project Management

Let’s be honest—many Agile transformations struggle.

Not because Agile doesn’t work, but because critical responsibilities are ignored.

Common patterns include:

• Teams delivering increments that don’t align with business outcomes
• Dependencies causing delays and frustration
• Stakeholders feeling disconnected and dissatisfied
• Lack of clear ownership for delivery risks

In such cases, Agile doesn’t feel empowering—it feels chaotic.

And often, the missing piece is not process—it’s project-level thinking and coordination.

What Makes an Agile Project Manager Different

If Agile still needs project management, then what changes?

Everything.

The Agile Project Manager is not:

• A task assigner
• A status tracker
• A gatekeeper

Instead, they:

• Enable flow, not control work
• Facilitate decisions, not impose them
• Influence stakeholders, not manage them through authority
• Focus on outcomes, not just timelines

It’s a shift from control to alignment and orchestration.

Snehamayee’s Thoughts

So do you need an Agile Project Manager? The answer is: it depends.

You may not need a dedicated Project Manager when:

• You have a single, small, co-located team
• Dependencies are minimal
• Stakeholders are closely aligned

But as complexity increases—

• Multiple teams
• Distributed environments
• High uncertainty
• Organizational constraints

—project-level coordination becomes essential.

Call it what you want, but the capability must exist.

The Bigger Problem: We’re Asking the Wrong Question

“Do Agile projects need Project Managers?” is the wrong question.

The better question is:

Do Agile projects need strong project management capabilities?

The answer is clearly yes.

Organizations don’t fail because they have Project Managers.
They fail because they lack clarity on how the role should evolve in Agile.

Conclusion: A Project Manager for an Agile Project is still relevant – You just have to align the work for Agile Realities

Agile didn’t eliminate the need for project management.

It redefined it.

The role is no longer about control—it’s about enabling alignment, managing complexity, and ensuring delivery in dynamic environments.

Whether you call it a Project Manager, Delivery Manager, or something else doesn’t matter.

What matters is this:

If no one is taking ownership of project-level responsibilities, your Agile setup is incomplete.

Reflection for you:
In your Agile projects today—who is actually handling project-level responsibilities?

The post Does Agile Need Project Managers? appeared first on World Of Agile.

Why Removing Blockers Isn’t Enough: How a Scrum Master Causes Real Impediment Removal

This article will discuss Why Removing Blockers Isn’t Enough: How a Scrum Master Causes True Impediment Removal. It is a part of an ongoing series of articles where I talk about Scrum masters’ common roles and responsibilities 

When most teams talk about impediments, they are usually referring to issues that surface in the Daily Scrum—someone is waiting for access, a dependency is stuck, or a requirement is unclear. Tracking these is not wrong. But it is not enough. Over years, I have seen one consistent pattern. What teams call “impediments” are often just symptoms of deeper systemic issues. When a Scrum Master limits their role to removing day-to-day blockers, they may help the team in the short term. But that  rarely improves how the system works. Then these issues keep on repeating. Which means recurring delays and wasted efforts to sort the blockers out True effectiveness lies in seeing beyond blockers and causing impediment removal at the system level.

Reframing Impediments: More Than What Shows Up Daily

A blocker is immediate and visible. Some examples can be A missing requirement or a dependency causing a delay.  On the other hand, an impediment is often persistent and structural. Some examples of impediments are Chronic unclear requirements and A dependency-heavy architecture Most teams operate in a loop of fixing blockers while they leave impediments untouched. The cost? Reduced flow, poor predictability, and increasing frustration. A mature Scrum Master learns to ask: “What keeps causing this problem to reappear?”

A Practical View: Types of Impediments

Not all impediments are equal. Treating them the same leads to ineffective actions. A useful way to think about them:

1. Team-Level

• Skill gaps
• Poor collaboration
• Unclear acceptance criteria or poorly written requirements

2. Organizational

• Approval bottlenecks and long tedious workflows
• Functional and/or Technical silos
• Traditional HR processes like appraisals /appreciation structures
• Misaligned Legal Contracts

3. Technical

• Legacy systems
• Fragile or Patchwork architecture
• Poor tooling

4. Flow-Related (Kanban lens)

• Too much work in progress
• Context switching (Parallel work)
• Bottlenecks in specific stages

This classification helps because each type requires a different intervention strategy The Scrum Master’s True Accountability There is still a persistent myth that Scrum Masters are facilitators who “help run ceremonies.” (even though the word “ceremony” was retired from Scrum Guide a long time back!) Facilitating the Scrum Events is a very small part of what Scrum Master should do Scrum Guide says that The Scrum Master is accountable for the Scrum Team’s effectiveness. This requires:

• Ability to influence without authority
• Challenging organizational constraints
• Enabling better ways of working

This is where many struggle—not because they lack intent, but because they underestimate the organisational dimension of impediment removal.  

How to Detect Impediments Early: Signals to Watch

Impediments rarely appear suddenly. They leave signals. Some of the most reliable ones:

• Stories repeatedly spill over sprints – we think we will complete and then figure out we can not. Reasons can be many – estimation issue/skills issue / adhoc work or poorly written stories. But if your Developers often struggle with story completion,  you should look into the underlying reason
• Work items often age without progress  /Cycle time Increases- Many times, the Scrum Team starts a piece of work only to find that the work is getting stalled. Again, there can be many immediate factors – conflicting priorities/dependencies / too big a piece of work, but if we do not show measurable progress and we have too much work-in-progress, items staying too long, it warrants further study. Studying Kanban and Flow principles can be a good idea
• Teams avoid difficult conversations – Teams not having any conflicts may seem good on the surface. You believe they are working in harmony. However, healthy conflict is necessary for progress in an uncertain or complex environment
• Dependencies become “normal”  –  When teams say things like  “long dependency tracking meetings are usual” or “we should add a dependency buffer to the timeline,”  it usually signals a need to simplify.

  The Kanban principle of Visualizing the work and tracking the progress via Flow Metrics provides a clear way to identify many of these signals early. The Kanban boards allows to see bottlenecks and the flow metrics help to capture flow efficiency (how much time gets wasted “waiting” / Cycle time (end to end time) are specifically helpful

Interpret the Signals ( Symptoms )to identify Root Causes

The signals we discussed above are often just  the  symptoms. A good doctor usually does not focus all his energy on symptoms, but they look at all symptoms in totality. The analyze the situation and identify the root cause. We, the Scrum masters, should do the same. Use the symptoms to think about the patterns. Quick fixes are tempting. They make progress visible. Working on pattrens and fixing the root cause often takes time, commitment , patience and most importantly fixing the root cause often needs courage. However, quick fixes almost always will guarantee recurrence. Whereas, fixing the root cause will lead to lasting relief. Effective Scrum Masters invest time in understanding root causes: They think Why does this dependency exist?  Or Why is this approval needed? Or Why does work get stuck at this stage? Techniques like 5 Whys or Fishbone diagrams help—but more important is the mindset of systems thinking. The goal is not to fix the issue. Rather, the goal is to remove the condition that creates the issue.

Create Safety to Surface Real Issues

One of the biggest barriers to impediment removal is not process—it’s psychological safety. When team members do not feel safe to raise issues, transparency suffers. Teams often hide impediments because  they fear blame or worse still because they believe “nothing will change anyway” A Scrum Master’s role here is subtle but critical:

• Stay neutral, avoid being judgmental
• Unless critical, try not step in with ready made solutions for immediate problems.
• Instead,ask questions that allow people to find out their own answers, asking right questions is the top trick a scrum master should learn.
• Observe patterns, not just listen to words

When teams don’t feel safe to expose problems, you’ll only ever deal with surface-level issues.

Choosing the Right Removal Strategy

Not every issue should be solved by the Scrum Master. I use the below quick dipstick to see if I as a Scrum Master should be involved. Let the team solve their blockers or impediments when:

• It’s something they can control
• It builds ownership
• It strengthens capability

I step in when:

• The issue spans multiple teams and my team does not have the necessary connects yet
• It requires facilitation or negotiation
• The team is stuck
• Issue is recurring and the team is doing quick fixes

 Escalate when:

• The issue is systemic or a symptom of a large organizational inefficiency or impediment
• It requires policy or structural change

The mistake many Scrum Masters make is becoming a “resolver of everything”, which creates dependency rather than capability.

Making Impediments Visible

If impediments are not visible, they will not be addressed. Simple practices can make a big difference:

• Maintain an impediment board or log
• Track aging of unresolved issues
• Review impediments regularly with stakeholders

This shifts the conversation from: “Do we have problems?” to “what we can do to solve these?” Visibility creates accountability.

Leveraging Scrum, SAFe, and Kanban Together

Scrum guide says Scrum master is accountable to make the Scrum team more effective. It does not ask the Scrum Master to limit them selves to Scrum Guide. In fact the guide encourages the Scrum Teams (and Scrum masters) to improve their own development practices. A good Scrum Master will often combine practices from Scrum /Kanban/SAFe or even the Lean philosophy Scrum

• Retrospectives provide a built-in opportunity for structured reflection. Good Scrum Masters use this time to
• Sprint reviews expose stakeholder-related impediments

Kanban

• Visualisation makes bottlenecks transparent
• Flow metrics provide objective signals

SAFe

• Escalation paths exist for systemic impediments
• ART-level coordination addresses cross-team constraints

Lean

• Mapping the Value Stream – Identify real value and understand how the team(or teams) delivers the value
• Eliminate waste – Identify steps that are not adding value

  The real impact comes when we integrate these perspectives. We do not need to choose one over the other. For example:

• Use Kanban metrics to identify a bottleneck
• Use Scrum retrospective to explore root causes
• Use SAFe forums to escalate systemic issues

Working with Leadership

Many impediments are outside the team’s control. This is the area where  Scrum Masters must step into a different role: They now just also put on hat of an organizational influencer. Some things that help are

• Translating team issues into business impact
• Using data instead of opinions
• Building relationships with decision-makers

For example: Instead of saying “dependencies are slowing us down”, say: “Our cycle time has increased by 30% due to cross-team dependencies, impacting release predictability.”   Leaders respond to impact, not frustration.

Measuring Impact

I always believe that what is measured gets improved. The principle applies to Impediment removal also. Impediment removal should lead to measurable outcomes: Some examples of these measurable outcomes are

• Reduced cycle time
• Improved flow efficiency
• Better predictability
• Increased team ownership

If these are not improving, it’s worth asking: Are we really removing impediments—or just managing them?

Closing Thought on How a Scrum Master Causes Real Impediment Removal

 Impediment removal is not about clearing obstacles faster. It is about changing the system so that fewer obstacles exist in the first place. That’s where Scrum Masters move from being facilitators…to becoming true enablers of transformation.

Scrum Masters evolution from Impediment Removal to a person who causes Impediment removal is the key to success

The ultimate evolution of the Scrum Master role is from someone who removes impediments to to someone who enables the system to remove those impediments continuously This means:

• Coaching teams to solve their own problems
• Building awareness of system constraints
• Shifting from reactive to proactive

At this stage, impediment removal is no longer an activity. It becomes part of the team and organizational culture.

The post Why Removing Blockers Isn’t Enough: How a Scrum Master Causes True Impediment Removal appeared first on World Of Agile.

Real-Life Scenarios when multiple Teams are working on the Same Product

In this section, we will look at some real-life scenarios that Scrum Team(s) often face when multiple Teams are working on the Same Product . This article is part of an ongoing series on real-life scenarios that many Scrum Teams face. Adding more teams to a product should increase speed. That’s the expectation. However, in many organisations, the opposite happens. Despite having multiple Scrum Teams working in parallel, delivery slows down, dependencies increase, and alignment becomes harder. Teams stay busy, but product progress feels inconsistent. The problem is not the number of teams—it is the complexity that comes with them. Working with multiple teams on the same product requires a different level of discipline, collaboration, and clarity. Without it, scaling Agile can quickly turn into scaling confusion. Based on my experience working with multi-team environments across Scrum, SAFe, and Kanban setups, here are some real-life scenarios that frequently emerge.

1. “We are done” (But Others cannot use it!!)

Team A completes their work and marks their stories as “Done.” However, when Team B tries to use the same functionality, they run into issues—missing APIs, incomplete validations, and inconsistent behaviour. From Team A’s perspective, the work is complete. From Team B’s perspective, it is not usable.

Snehamayee’s perspective

What’s happening here? Each team delivers their work with their own interpretation of what “Done” means. There is a clear lack of a shared understanding at the product level. Impact: Work appears complete on dashboards, but real progress is not seen. Instead, the teams struggle with rework, delays, and frustration What we can do?

• A shared Definition of Done across teams is critical. It should include integration, usability by other teams, and alignment with product-level quality standards. “Done” should mean usable—not just complete within a team boundary.
• Integrated Solution level or Product level reviews – SAFe (Scaled Agile Framework ) recommends regular System demos. These are integrated demos – These will enable teams to “see” how their work is being used by other teams. These demos also help the teams as they encourage collaboration

2. Dependency Chaos Between Teams

A very common situation in multi-team setups is when one team’s progress depends heavily on another. You often hear statements like: “We can’t start until Team B finishes their part.” Or “We’re blocked waiting for the API from Team C.” Snehamayee’s perspective What’s happening here? Some possible reasons are

• Component Teams -Teams are often structured around components rather than features. This leads to tight coupling between teams.
• Inefficient work slicing – In addition, the work slicing (splitting work across teams) often creates additional dependencies across team boundaries

Impact: Planning becomes uncertain, commitments become unreliable, and teams lose their ability to deliver independently. Instead of enabling speed, multiple teams create bottlenecks. What we can do?  

• Reducing dependencies should be a continuous focus. This may involve rethinking backlog slicing, re-assignment of work, or even restructuring teams toward more feature-oriented ownership.
• Dependency Board – Visually tracking the multi-team dependencies will help the teams identify critical path to monitor, bottlenecks to be aware about and trigger remedial actions in advance to reduce dependencies. Another SAFe technique the ART planning board will help.
• Design Feature Teams –Teams that are designed to deliver end to end value rather than a specific component help with easier coupling

3. Conflicting Priorities Across Teams

In another setup, each team appears busy and productive. However, when viewed from a product perspective, progress is slow and scattered. Different teams work on different priorities—some on new features, others on technical improvements, and some addressing stakeholder requests.

Snehamayee’s perspective

What’s happening here?

There is no clear alignment at the product level. Teams optimize for their own backlog rather than a shared product goal.

Impact: High activity does not translate into meaningful outcomes. Work gets fragmented, and the product evolves in an inconsistent manner. What we can do?

• Clear product-level prioritization is essential. Whether through a single Product Owner, a Chief Product Owner, or a well-aligned Product Management function, teams need a shared understanding of what matters most.
• A cross-domain planning session – A common planning session across teams will help the teams to align their priorities and expectations.

4. Integration Becomes a Nightmare

Integration of work is one of the most common challenges for the multi-team product. Each team develops and tests its work independently. Everything works fine within team boundaries. However, when all components come together, issues start to surface—unexpected defects, incompatible interfaces, and performance problems.

Snehamayee’s perspective

What’s happening here?

Integration happens too late. Teams work in silos with limited visibility into how their work interacts with others.

Impact: Integration risks accumulate over time. On top,  these integration risks will often surface at the worst possible moment—close to release timelines.

What we can do?

• Frequent integration is key. Practices such as continuous integration, shared environments, and automated testing help reduce surprises. Integration should not be treated as a separate phase—it should be part of everyday development.
• A common Sprint Duration – A common Sprint Duration will provide a cadence needed for frequent integration
• Regular Integrated demos Or System demos as defined by SAFe will help. These demos help to enforce regular integration

5. Ownership Confusion – “Who Owns This?”

In multi-team environments, features often span across teams. This creates situations where responsibility is unclear. When an issue arises, the response is often: “This part belongs to Team A.” or “That integration is handled by Team B.” or “This is not our responsibility”

Snehamayee’s perspective

What’s happening here?

Ownership is divided along component or functional lines, rather than end-to-end product outcomes.

Impact: Slow decision-making, blurred accountability and issues that take longer to resolve. In some cases, important items fall through the cracks because no team feels responsible.

What can we do? Clear ownership of outcomes is critical. Even if multiple teams contribute, there should be clarity on who is accountable for delivering the feature end-to-end. Shifting toward feature ownership rather than component ownership can help address this challenge.

Final Thoughts on Real-Life Scenarios Faced by Scrum Teams When Multiple Teams Work on the Same Product

Working with multiple teams on the same product is not just about adding capacity(or people). It is about managing complexity. Many of the challenges discussed above are not caused by a lack of skill or effort. They arise from gaps in alignment, communication, and shared understanding. Some common issues I have seen across many customers are:

• Lack of shared standards – for example, a common integrated Definition of Done or common  quality standards
• High dependencies between teams means a tight coupling and more limitations
• Misaligned priorities lead to effort wastage and rework
• Limited focus on integration and ownership

  It takes conscious effort to address these challenges. Some tips that help are

• Better Alignment among teams by planned multi team events like structured cross-domain planning
• Establishing collaboration forums like dependency boards
• Designing feature teams that deliver end to end value and move away from component teams

Organisations that recognise and actively address these patterns are more likely to realise the true benefits of scaling Agile. Those that do not often find themselves adding more teams—but not necessarily delivering more value.    

The post Real-Life Scenarios Faced when multiple Teams are working on the Same Product appeared first on World Of Agile.