Agile Project Execution

Agile Project Execution

Scrum structures a team's work into short, predictable cycles. The three roles (Product Owner, Scrum Master, Developer), the sprint events (planning, daily stand-up, review, retrospective), the five Scrum values, and the core artefacts (product backlog, sprint backlog, increment) form the framework within which you learn to write user stories, acceptance criteria, and a Definition of Done that actually holds up.

Starting Points

• Scrum.org. What is Scrum?
• Stellman, A., & Greene, J. (2017). Head First Agile. O'Reilly.

Key Points

• You set up a backlog with epics and user stories, and a sprint board with a sprint backlog.
• You name and describe the three Scrum roles and their main responsibility.
• You list all Scrum events (Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective) and their purpose.
• You name the five Scrum values and explain how each influences behaviour in a team.
• You identify the main artefacts: Product Backlog, Sprint Backlog, Increment/MVP.
• You write a user story in the standard format ("As a <user>, I want <feature>, so that <benefit>"), including description, tasks, acceptance criteria, and Definition of Done.
• You interpret a burndown or burnup chart and explain MoSCoW prioritisation.