Overview
Managing Products with Agility covers how the Scrum Team, led by the Product Owner, delivers value through the product. It has four areas. Forecasting and release planning covers using empirical data such as velocity and the Product Backlog to forecast, while recognizing forecasts are not commitments. Product value covers maximizing the value of the product and the work, the central Product Owner accountability. Product Backlog management covers ordering, refining and keeping the backlog transparent so it reflects the most valuable work next. Stakeholders and customers covers engaging them, especially at the Sprint Review, to gather feedback and align the product with their needs.
This area applies the Product Owner accountability and the product-related artifacts from the framework. The PSM I rewards understanding that value, not output, is the goal, that the Product Owner owns the ordered Product Backlog, that forecasts are empirical and uncertain, and that stakeholder feedback through Scrum's events steers the product, all consistent with the Scrum Guide.
How it's tested
PSM I questions in this focus area describe a product, backlog, forecast or stakeholder situation and ask how to manage it for value. PSM I questions test the Scrum Guide precisely, so read the scenario and choose the answer consistent with what Scrum defines, rejecting options that reflect common workplace deviations.
-
Maximize value
A product or work situation is described, and you choose the option that maximizes value, not just output.
-
Own the backlog
A backlog situation is described, and you apply that the Product Owner owns its ordering and content.
-
Forecast empirically
A planning or forecasting need is described, and you use empirical data while treating forecasts as uncertain.
A stakeholder insists a low-value feature they personally want be moved to the top of the Product Backlog. The order of the Product Backlog is the Product Owner's accountability, decided to maximize product value, not dictated by any single stakeholder. So the Product Owner considers the input but decides the ordering based on value, and the team respects that decision.
Focus areas 4
Official focus areas from the Scrum.org outline, in outline order.
3.1 Forecasting and release planningUsing empirical data to forecast, treating forecasts as uncertain.
- What it means
- This covers forecasting and release planning using empirical data, such as past throughput or velocity and the Product Backlog, to project what might be delivered and when, while recognizing that forecasts are projections, not guarantees, and are refined as more is learned.
- What to understand
- Scrum uses empiricism to forecast: based on evidence from completed work, the team projects likely outcomes, and these forecasts become more reliable over time but remain uncertain for complex work. A forecast is not a fixed commitment, and plans adapt as reality unfolds. Understanding forecasting as empirical and provisional is the key insight.
- How it shows up
- A planning or forecasting situation is described, and you must apply empirical forecasting and its uncertainty.
- Common confusion
- Treating a forecast as a firm commitment rather than an evidence-based, uncertain projection.
3.2 Product valueMaximizing the value of the product and the work.
- What it means
- This covers maximizing the value of the product resulting from the work of the Scrum Team, the central accountability of the Product Owner, including focusing on outcomes and value rather than simply the volume of output, and using the Product Goal to guide value delivery.
- What to understand
- The purpose of Scrum is to deliver value, and the Product Owner is accountable for maximizing it. Value is about outcomes and benefit to users and the organization, not the number of features shipped. The Product Goal provides a focus for value, and decisions are made to maximize value given constraints. Prioritizing value over output is a core principle.
- How it shows up
- A product or prioritization situation is described, and you must choose the value-maximizing option.
- Common confusion
- Measuring success by output (features delivered) rather than by the value and outcomes achieved.
3.3 Product Backlog managementOrdering, refining and keeping the backlog transparent.
- What it means
- This covers managing the Product Backlog: the single ordered list of what is needed to improve the product, owned by the Product Owner, including ordering it to maximize value, refining items to add detail and estimates, and keeping it transparent and understood by the Scrum Team.
- What to understand
- The Product Backlog is the single source of work for the product, and the Product Owner is accountable for its content, ordering and availability, though others may help refine it. Items near the top are clearer and smaller, ready to be selected, through ongoing refinement. The Product Owner's ordering decision is respected. Knowing who owns the backlog and how it is managed is central.
- How it shows up
- A backlog situation is described, and you must apply ordering, refinement or the Product Owner's ownership.
- Common confusion
- Having someone other than the Product Owner decide the backlog order, or treating refinement as a separate formal event.
3.4 Stakeholders and customersEngaging stakeholders to gather feedback and align the product.
- What it means
- This covers engaging stakeholders and customers, understanding their needs, and gathering their feedback, especially at the Sprint Review where the Scrum Team and stakeholders inspect the Increment and adapt the Product Backlog together to steer the product.
- What to understand
- Stakeholders and customers are the source of feedback that keeps the product valuable. The Sprint Review is the key event for collaborating with them on the Increment and what to do next, and the Product Owner engages them throughout. Their feedback adapts the Product Backlog, closing the empirical loop. Engaging stakeholders well is essential to delivering value.
- How it shows up
- A stakeholder or feedback situation is described, and you must choose how to engage them or use their feedback.
- Common confusion
- Treating the Sprint Review as a one-way demo rather than a collaborative working session that adapts the backlog.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Empirical forecasting
Projecting from evidence such as velocity.
- Remember
- Forecasts are uncertain, not commitments.
- Tested as
- Forecasting questions.
- Trap
- Treating a forecast as a guarantee.
-
Forecast vs. commitment
A projection versus a promise.
- Remember
- Forecasts adapt as more is learned.
- Tested as
- Forecasting questions.
- Trap
- Confusing the two.
-
Product value
Outcomes and benefit, not output volume.
- Remember
- The Product Owner maximizes it.
- Tested as
- Value questions.
- Trap
- Measuring success by features shipped.
-
Product Goal
The long-term objective for the product.
- Remember
- Guides value delivery.
- Tested as
- Value questions.
- Trap
- Ignoring the Product Goal.
-
Product Backlog
The single ordered list for the product.
- Remember
- Owned by the Product Owner.
- Tested as
- Backlog questions.
- Trap
- Letting others own the order.
-
Backlog ordering
Ordering to maximize value.
- Remember
- The Product Owner's decision.
- Tested as
- Backlog questions.
- Trap
- Ordering by stakeholder pressure.
-
Product Backlog refinement
Adding detail, estimates and order.
- Remember
- An ongoing activity, not a formal event.
- Tested as
- Backlog questions.
- Trap
- Treating it as a separate event.
-
Product Owner accountability
Maximizing value and owning the backlog.
- Remember
- One person, decisions respected.
- Tested as
- Role questions.
- Trap
- Splitting or overriding the role.
-
Sprint Review
Collaborating with stakeholders on the Increment.
- Remember
- Adapts the Product Backlog.
- Tested as
- Stakeholder questions.
- Trap
- Treating it as a one-way demo.
-
Stakeholder feedback
Input that keeps the product valuable.
- Remember
- Gathered especially at the Review.
- Tested as
- Stakeholder questions.
- Trap
- Ignoring stakeholder feedback.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Forecast vs. commitment
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Forecast | Evidence-based projection | Uncertain, adapts | Treating it as a guarantee |
| Commitment | A fixed promise | Not how Scrum forecasts work | Confusing with a forecast |
Value vs. output
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Value | Outcomes and benefit | The goal of Scrum | Measuring by output |
| Output | Volume of features | Not the measure of success | Equating it with value |
Sprint Review vs. one-way demo
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Sprint Review | Collaborate and adapt the backlog | Working session with stakeholders | Confusing with a demo |
| One-way demo | Show the work only | Not the full purpose | Treating the Review as this |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Stakeholder dictates the order
- What candidates pick
- Move a stakeholder's pet low-value feature to the top of the Product Backlog because they insist.
- Why it looks right
- The stakeholder is influential.
- Why it's wrong
- The Product Owner is accountable for ordering the Product Backlog to maximize value; input is considered, but the Product Owner decides.
Clue to watch for A stakeholder is trying to control the backlog order.
-
Forecast is a promise
- What candidates pick
- Treat a velocity-based forecast as a fixed delivery date.
- Why it looks right
- Forecasts give a date.
- Why it's wrong
- Forecasts are empirical projections that are uncertain and adapt as more is learned; they are not fixed commitments.
Clue to watch for A projection is being treated as a firm guarantee.
-
Output equals success
- What candidates pick
- Judge the product successful because many features were delivered.
- Why it looks right
- Delivering a lot feels productive.
- Why it's wrong
- Scrum measures success by value and outcomes, not the volume of output; features that do not deliver value are not success.
Clue to watch for Success is being measured by quantity of features.
-
Review is a demo
- What candidates pick
- Run the Sprint Review purely as a demonstration of completed work.
- Why it looks right
- Showing the work is part of it.
- Why it's wrong
- The Sprint Review is a working session where the team and stakeholders inspect the Increment and adapt the Product Backlog together.
Clue to watch for The Review is treated as one-way presentation only.
-
Shared Product Owner
- What candidates pick
- Have a committee jointly own and order the Product Backlog.
- Why it looks right
- The product is complex.
- Why it's wrong
- The Product Owner is one person accountable for the backlog and value; the role is not a committee.
Clue to watch for The backlog ownership is split among several people.
Answer framework
For any Managing Products with Agility scenario, use these steps to find the answer the PSM I expects.
- Keep value, meaning outcomes and benefit to users and the organization, as the goal in every decision, rather than the sheer volume of output produced.
- Protect the Product Owner's accountability for ordering and owning the Product Backlog to maximize value.
- Use empirical data to forecast and plan releases, treating forecasts as uncertain projections that adapt.
- Refine the Product Backlog continually so the most valuable, ready work is near the top.
- Engage stakeholders and customers for feedback, especially at the Sprint Review, and adapt the Product Backlog accordingly. Where two options seem to fit, choose the one that reflects what the Scrum Guide prescribes rather than a common deviation.
Practice question
Want more like this? The PSM I practice test has questions for every domain.
Checklist
0 of 10
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Study this focus area around one idea: Scrum exists to deliver value, and the Product Owner is accountable for maximizing it. Fix firmly that value and outcomes, not output volume, measure success, and that the Product Owner owns the Product Backlog's content and order, considering stakeholder input but deciding based on value with that decision respected.
Learn forecasting as empirical and uncertain, so a forecast is never a firm commitment, and learn Product Backlog management, ordering and ongoing refinement, and that refinement is an activity, not a formal event. Understand the Sprint Review as a collaborative working session where stakeholders and the team inspect the Increment and adapt the backlog, not a one-way demo.
Because the PSM I tests these as scenarios, practice choosing the value-focused, Product-Owner-accountable answer consistent with the Scrum Guide. This is the final focus area, so finish with full practice assessments across all three and aim consistently above 85%.
FAQ
What does Focus Area 3 cover on the PSM I?
Managing Products with Agility: forecasting and release planning, maximizing product value, Product Backlog management, and engaging stakeholders and customers, applying the Product Owner accountability and product artifacts.
Is a forecast a commitment in Scrum?
No. A forecast is an evidence-based projection of what might be delivered, which is uncertain for complex work and adapts as more is learned. It is not a fixed commitment or guarantee.
How is success measured in Scrum?
By the value and outcomes delivered, not the volume of output. Delivering many features that do not provide value is not success; the Product Owner maximizes value, guided by the Product Goal.
Who owns the Product Backlog?
The Product Owner, who is accountable for its content, ordering and transparency. Others may help refine items, but the Product Owner decides the order to maximize value, and that decision is respected.
What is Product Backlog refinement?
The ongoing activity of adding detail, estimates and order to Product Backlog items so the most valuable, ready work is near the top. It is an activity carried out as needed, not a separate formal Scrum event.
What is the purpose of the Sprint Review?
It is a working session where the Scrum Team and stakeholders inspect the Increment and collaborate on what to do next, adapting the Product Backlog. It is not merely a one-way demonstration of completed work.
How does Focus Area 3 connect to the rest of the exam?
It applies the Product Owner accountability and the product-related artifacts from the framework area, delivered by the effective team developed in the people area, closing the loop from framework to value.
Other Agile & Scrum certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 3 knowledge
You have covered forecasting, product value, Product Backlog management and stakeholders. Test whether you can manage the product for value under exam conditions.