FIT2002 Chap.7 Scrum Roles, Events and Commitments
Scrum Roles, Events and Commitments
Scrum is a lightweight framework for generating value through adaptive solutions to complex problems. Its three accountabilities have distinct focuses: the Product Owner maximises product value and manages the Product Backlog, Developers create a usable Increment each Sprint, and the Scrum Master establishes Scrum and improves the team's effectiveness.
Accountability cannot be replaced by a traditional command chain without changing how decisions are made.
Events create a regular inspection-and-adaptation rhythm. The Sprint contains planning, daily coordination, review and retrospective. The Product Goal, Sprint Goal and Definition of Done provide different commitments for the Product Backlog, Sprint Backlog and Increment.
A scenario answer should identify the affected accountability, event or commitment, explain what transparency is lost, and restore a decision rule. Scrum terminology earns little unless it changes the recommended action.
What this chapter covers
- 01
Product Owner accountability for value and Product Backlog management
- 02
Developers' accountability for planning and creating a usable Increment
- 03
Scrum Master accountability for Scrum and team effectiveness
- 04
The Sprint as a container for inspection and adaptation events
- 05
Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective
- 06
Product Goal, Sprint Goal and Definition of Done as commitments
- 07
Empiricism through transparency, inspection and purposeful adaptation
Worked example · free
Repair a Sprint disrupted by an executive request
- +2The Developer should make the request transparent to the Developers and Product Owner rather than accepting hidden work from an external authority.
- +2Inspect the request's value, urgency, size and effect on the Sprint Goal and existing forecast.
- +2The Product Owner may clarify value and ordering, while Developers remain accountable for how selected work is planned and performed.
- +2If the Sprint Goal remains valid, Developers and Product Owner can renegotiate scope without reducing agreed quality or concealing impact.
- +1If the Sprint Goal becomes obsolete, only the Product Owner may cancel the Sprint; urgency alone does not automatically require cancellation.
Key terms
- Product Owner
- The Scrum accountability for maximising the value of the product and for effective Product Backlog management. The role is one person, though that person may represent many stakeholders.
- Developers
- The people in the Scrum Team committed to creating any aspect of a usable Increment each Sprint. They plan the Sprint work, maintain quality and adapt their daily plan.
- Scrum Master
- The accountability for establishing Scrum as defined and improving the Scrum Team's effectiveness. The Scrum Master coaches, enables and helps remove systemic impediments rather than assigning team tasks.
- Sprint Review
- The event in which the Scrum Team and stakeholders inspect the Sprint outcome and consider changes in the environment, then collaborate on what to do next.
- Sprint Retrospective
- The event used by the Scrum Team to inspect how the Sprint went across people, interactions, processes, tools and quality, then plan useful improvement.
- Definition of Done
- A formal description of the state of the Increment when it meets the product's required quality measures. Work that does not satisfy it is not part of the usable Increment.
Scrum Roles, Events and Commitments FAQ
Who can change work during a Sprint?
Developers adapt the Sprint Backlog as they learn, and the Product Owner and Developers can renegotiate selected scope without endangering the Sprint Goal. Changes should remain transparent and quality must not decrease. External stakeholders do not directly assign hidden work. If the Sprint Goal becomes obsolete, only the Product Owner has the authority to cancel the Sprint.
How is a Sprint Review different from a Retrospective?
The Sprint Review inspects the product outcome, progress toward the Product Goal and changes in the environment with relevant stakeholders. The Retrospective inspects how the Scrum Team worked and selects improvements to effectiveness and quality. One informs future product direction; the other focuses on the team's system of work, although learning can connect them.
Is the Scrum Master the team's project manager?
The accountabilities are not equivalent. A Scrum Master establishes Scrum, coaches participants and helps improve effectiveness; the role does not own all product, people and task decisions. Product value belongs with the Product Owner, while Developers manage their delivery plan. In a broader organisation, project governance may still exist, but it should not erase Scrum accountabilities.
Assessment move
Draw a three-column accountability table and fill it using verbs: who maximises and orders, who creates and adapts the plan, and who establishes and enables. Add a fourth column listing actions each role does not own. Build a second map from Product Backlog to Product Goal, Sprint Backlog to Sprint Goal, and Increment to Definition of Done.
For events, revise purpose before timebox or participant details; if you understand the decision produced by an event, scenario application becomes easier. Practise interruptions, unfinished work, stakeholder feedback and quality failures. In each answer identify the transparency problem, the inspection point and the authorised adaptation.
This structure prevents role-name dumping and demonstrates why Scrum's boundaries matter to value, focus and quality.
Working through Scrum Roles, Events and Commitments in FIT2002? Sia is AskSia’s AI Project Management tutor — ask any FIT2002 Scrum Roles, Events and Commitments question and get a clear, step-by-step explanation grounded in how FIT2002 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
