Agile Frameworks and Methodologies
What this domain tests
Agile delivery embraces emergent requirements and short feedback loops. Know the Agile Manifesto values (individuals and interactions, working software, customer collaboration, responding to change - while still valuing the items on the right). Understand Scrum roles (Product Owner, Scrum Master, Development Team), artifacts (product backlog, sprint backlog, increment), and events (sprint planning, daily scrum, sprint review, retrospective). Know Kanban (visualize flow, limit WIP, measure cycle time) and XP practices (pair programming, TDD, continuous integration).
Concepts to master
- Servant leadership: the Scrum Master removes impediments rather than assigning work.
- Definition of Done and acceptance criteria as quality gates.
- Velocity and burndown/burnup charts for forecasting, not for judging individuals.
- Backlog refinement and story points as relative estimation.
- Retrospective as the inspect-and-adapt event for the team's process.
Traps in questions
Beware answers that have the Scrum Master direct the team or reassign tasks - that violates self-organization. A common distractor adds scope mid-sprint; the correct response is to let the Product Owner reorder the backlog for the next sprint. Another trap conflates the sprint review (demonstrate the increment to stakeholders) with the retrospective (improve team process). Also, velocity is a planning aid, not a performance metric.
Rule of thumb
When a question describes a team blocked by an external dependency, the Scrum Master's job is to remove the impediment or escalate it - not to do the technical work or pressure the team to go faster.