Scrum is an agile framework for complex projects
Practices,
Roles,
Activities and
Artifacts
3 main Scrum roles:
Product Owner
Scrum Master
DEV Team
= the project’s “key” stakeholder (or key user)
represents users, customers and others in the process
creates a prioritized wish list called a product backlog
responsible for making sure the team is as productive as possible
by helping the team use the Scrum process, by removing impediments to progress, by protecting the team from outside, …
between 5 – 9 persons
no “traditional” roles such as programmer, designer, tester or architect
everyone on the project works together to complete the set of work they have committed to complete within a sprint
“we’re all in this together”
Scrum provides activities to help teams apply agile principles:
Sprint, Sprint Planning, Daily Scrum, Sprint Execution, Sprint Review, Sprint Retrospective, Product Backlog Care
Sprints = iterations (2 – 4 weeks)
Start: Sprint Planning (select a set of stories)
Sprint: Daily Scrum (goal: complete stories)
End: Sprint Review (discuss completion, lessons learned, how to improve productivity)
Sprint Planning = beginning of a sprint
-> PO presents the top items on the product backlog to the team
-> Team select a set of stories to complete in the new sprint (selects the work they can complete during the coming sprint)
Work move PBL -> SBL
Daily Scrum = a 15 min standup each day during the sprint
-> helps set the context (What I did yesterday and what I will do on the coming day?) for each day’s work and helps the team stay on track
all team members attend
Sprint Execution = doing the work the Scrum Team selected to meet the sprint goal
goal of each sprint = to complete the selected items
Sprint Review = end of each sprint
-> discuss the completion of each story and
-> what the team has learned from the sprint and
-> how to maintain/improve the productivity in future sprints
inspect & adapt the build product
Sprint Retrospective = “real” end of each sprint
3 points are discussed: What the team did well and should continue, what the team should start doing, and what did not work and should stop doing?
learn from the past and discuss how to improve the productivity of the coming sprints
Start