Key CSM terms in plain English. The exam tests the Scrum framework from the Scrum Guide, so it helps to know the core vocabulary: the roles, events, artifacts and values, plus how the certification works.
| Term | Definition |
|---|---|
| Scrum | A lightweight framework for delivering value in short cycles, built on empirical process control and a small set of roles, events and artifacts. |
| Agile | An iterative, incremental approach to delivering work that values collaboration, customer feedback and adapting to change. |
| Empirical process control | Managing work through transparency, inspection and adaptation rather than detailed up-front plans. |
| Scrum Master | A servant leader who helps the team understand and apply Scrum, facilitates events and removes impediments. |
| Servant leadership | A leadership style focused on enabling and supporting the team - coaching, facilitating and removing blockers - rather than commanding. |
| Product Owner | The person accountable for maximising the value of the product by managing and ordering the Product Backlog. |
| Developers | The team members who do the work of building a usable Increment each Sprint. |
| Scrum Team | The Scrum Master, Product Owner and Developers working together; small, cross-functional and self-managing. |
| Sprint | A fixed-length cycle (typically up to a month) that contains all the other Scrum events and produces an Increment. |
| Sprint Planning | The event that starts a Sprint, where the team plans the work and sets the Sprint Goal. |
| Daily Scrum | A short daily event for the Developers to inspect progress and plan the next day’s work. |
| Sprint Review | An event near the end of a Sprint to inspect the Increment with stakeholders and adapt the Product Backlog. |
| Sprint Retrospective | An event where the Scrum Team reflects on how it works and plans improvements for the next Sprint. |
| Product Backlog | An ordered, evolving list of everything that might be needed in the product, owned by the Product Owner. |
| Sprint Backlog | The set of Product Backlog items selected for the Sprint plus the plan to deliver them. |
| Increment | A usable, “Done” step toward the Product Goal produced during a Sprint. |
| Product Goal | The longer-term objective for the product; the commitment for the Product Backlog. |
| Sprint Goal | The single objective for a Sprint; the commitment for the Sprint Backlog. |
| Definition of Done | A shared, agreed checklist of what must be true for an Increment to be considered complete; the commitment for the Increment. |
| Scrum values | The five values that guide Scrum behaviour: commitment, focus, openness, respect and courage. |
| Transparency | An empirical pillar: the work and process are visible to those who do and receive it. |
| Inspection | An empirical pillar: regularly checking artifacts and progress toward goals. |
| Adaptation | An empirical pillar: adjusting the work or process as soon as inspection shows a need. |
| Impediment | Anything that blocks or slows the team, which the Scrum Master helps to remove. |
| Self-managing team | A team that decides internally who does what, when and how, rather than being directed externally. |
| Time-box | A maximum fixed duration set for a Scrum event so it does not run long. |
| Certified Scrum Trainer (CST) | A trainer accredited by Scrum Alliance to teach the official CSM course and certify candidates. |
| Scrum Education Unit (SEU) | The unit of continuing education used to renew Scrum Alliance certifications such as the CSM. |