Applying Scrum in Real Teams

PSM I PSM I · Applying Scrum in Practice

By Abu Anns · Last updated 20 November 2026Exam version: PSM I (Scrum Guide 2020)

Knowing the Scrum Guide is one thing; applying it in a real organization is another. The PSM I exam tests both. Many questions are scenario-based: a situation is described, and you must choose the response that matches the Scrum Guide rather than the response that matches common workplace habit. This guide covers the applied topics the exam draws on most: how Scrum works at larger scale, how forecasting works empirically, how the Scrum Master coaches and facilitates, and the misconceptions that trap even experienced practitioners. If you can recognize the pattern in each scenario — which accountability owns the decision, which pillar is at stake, which value is missing — the scenario questions become the easiest part of the exam, not the hardest.

Scaling Scrum

Scrum scales by multiplying teams, not by enlarging them. When one Scrum Team is not enough for a product, the Guide's answer is multiple cohesive Scrum Teams, each focused on the same product, sharing the same Product Goal, the same Product Backlog, and the same Product Owner. Each team has its own Scrum Master and its own Developers, runs its own Sprints, and produces Increments that must work together — which is why multiple teams on one product must mutually define and comply with the same Definition of Done. There is no scaling framework in the Scrum Guide itself: Nexus, LeSS, and SAFe exist outside it, and the PSM I exam does not test them. What it tests is the Guide's own scaling logic: one product, one backlog, one Product Owner, one Product Goal, one Definition of Done — and teams small enough to communicate well. Any option that creates a hierarchy of teams, a backlog per team, or a committee of Product Owners contradicts the Guide.

Forecasting and release planning

Forecasting in Scrum is empirical: it is based on what the team has actually delivered, not on upfront estimates of the whole backlog. Various practices exist to forecast progress, such as burn-down charts, burn-up charts, and cumulative flow diagrams. While these have proven useful, they do not replace empiricism — a burn-down chart is a visualization of observed progress, not a promise. The Product Owner uses observed delivery to forecast when the Product Goal might be reached and to plan releases, and stakeholders should understand that forecasts change as the team learns more. The exam tests this through scenarios where someone demands a fixed date for a distant scope: the Scrum answer is an empirical forecast with a range, updated each Sprint, not a commitment to a date. Release planning works the same way: the Product Owner considers value, risk, and learning, and plans releases for when an Increment is usable and valuable — not on a fixed calendar decided months in advance.

Coaching, facilitation, and servant leadership

The Scrum Master's applied skills are coaching, facilitation, and teaching. Coaching means helping team members and the Product Owner develop their own capability — in self-management, in cross-functionality, in Product Backlog management — rather than doing the work for them. Facilitation means helping events and discussions work well: keeping a Sprint Retrospective honest, helping stakeholders and the team collaborate at a Sprint Review, ensuring the Daily Scrum stays focused. Teaching means helping the organization understand Scrum theory and practice, including the empirical approach to complex work. The thread connecting all three is servant leadership: the Scrum Master leads by serving the team and the organization, without authority over anyone. Exam scenarios that offer a commanding response — the Scrum Master tells the team what to do, overrules the Product Owner, or escalates to a manager — are almost always wrong. The right response is the one where the Scrum Master coaches, facilitates, teaches, or removes an impediment.

Common misconceptions

The exam recycles a set of misconceptions, and recognizing them is worth several questions. The Scrum Master is not a project manager. The Daily Scrum is not a status meeting. The Sprint Review is not a demo or a sign-off. The Product Owner is not a committee and cannot delegate accountability. The Developers are not just coders — everyone who creates the Increment is a Developer. The Sprint Backlog is not fixed at Sprint Planning. Quality cannot be traded for scope. A Sprint cannot be extended. The three questions are not mandatory at the Daily Scrum. The Definition of Done is not the same as acceptance criteria. Refinement is not an event. And Scrum has no roles beyond the three accountabilities — no project manager, no tech lead, no business analyst as a formal role. If an option introduces a role, a meeting, or a document that is not in the Guide, it is almost certainly wrong.

Worked scenario

A company adopts Scrum and appoints a project manager as Scrum Master, keeps the existing weekly status meeting, and asks the Product Owner to write a detailed six-month plan. Three months later, nothing has improved. What went wrong? The project manager is managing the team instead of serving it, which breaks self-management. The status meeting duplicates the Daily Scrum instead of trusting the artifacts for transparency. And the six-month plan contradicts empiricism — the Product Backlog is emergent, and forecasts should be based on observed delivery. The fix is not more process; it is applying the framework as defined: a servant-leader Scrum Master, daily inspection by the Developers, and an empirical approach to planning. The exam rewards candidates who can see these patterns, not candidates who have memorized the Guide word for word.

Starting Scrum in a traditional organization

Organizations adopting Scrum for the first time often keep their old habits alongside the new framework: the project manager becomes the Scrum Master but keeps managing, the status meeting survives alongside the Daily Scrum, and the detailed annual plan sits next to the emergent Product Backlog. The result is Scrum in name only, and the benefits do not appear. The Scrum Master's organizational work — leading, training, and coaching the organization in its Scrum adoption, and removing barriers between stakeholders and teams — is what closes the gap between adopting the ceremonies and adopting the framework. Change takes time, and the Scrum Master should expect resistance: self-management feels like a loss of control to managers, and empiricism feels like a loss of certainty to executives. Patience, teaching, and visible results are the tools, not mandates.

Advertisement

Exam traps to watch for

Practice questions

Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.

Q1.A company has three Scrum Teams working on one product. Which statement is TRUE?

Report an error

Q2.A stakeholder demands a fixed delivery date for a large scope of work six months away. What is the BEST Scrum-aligned response?

Report an error

Q3.Which statement about forecasting practices such as burn-down charts is TRUE?

Report an error

Q4.A Scrum Master notices the Developers are struggling with self-management and keep asking for direction. What is the BEST action?

Report an error

Q5.Which of the following is NOT part of the Scrum framework as defined in the Scrum Guide?

Report an error

Q6.A Scrum Team's Sprint Review has become a monthly slide presentation to executives, with no discussion. What SHOULD the Scrum Master do?

Report an error

Q7.An organization wants to adopt Scrum and asks the Scrum Master to write a detailed plan for the next year of product development. What is the BEST response?

Report an error

Q8.A new Scrum Master is unsure how to handle a conflict between two Developers. Which approach BEST fits the Scrum Master accountability?

Report an error

Q9.Which statement about the Scrum framework is TRUE?

Report an error