SCRUM

Scrum Flow Create initial product backlog Perform sprints iteratively Collect user stories Perform sprints iteratively Sprint planning 2-4 weeks of actual sprint Including daily scrum meetings Design, development, and test in parallel Sprint review Sprint retrospective Nothing changes during the sprint! Changes accommodated via backlog and planning

ROLES Scrum master Product owner Team members Stake-holders

ARTIFACTS Task board Sprint backlog Product backlog Product

CEREMONIES Daily scrum Sprint planning Sprint review Sprint Retros-pective Sprint review Sprint planning

Product Owner Represents client Ensure delivery of business value A domain expert Explain product features to team Ensure delivery of business value Manage releases (content and timing) Accept/reject work results Responsible for the product backlog Add user stories (requirements) Prioritize user stories What to do in the next sprint

Scrum Master Like project manager But no personnel responsibilities Remove impediments and allow team to make progress Buffer between team and distractions Responsible for following the Scrum process Chairs planning and daily meetings

Scrum Team “Self organizing” 7  2 full-time people Mixture of skills People sign up for work 7  2 full-time people Larger projects organized as Scrum of Scrums Mixture of skills Developers, testers, user interface experts, … May change from sprint to sprint, but not during a sprint Responsible for actual development Also effort estimation, progress tracking, and alerting upon problems

Product Backlog A list of features Prioritized by business value The requirements Based on user stories Also bugs and technical tasks Prioritized by business value Maintained by the product owner New tasks added as they are discovered

Sprint Backlog Tasks selected for execution in the current sprint Derived from features in the product backlog Selected by team based on priorities Each task has limited (estimated) duration Typically no more than a day Details updated as work progresses But new tasks are not added

Task Board Represents the status of the sprint backlog Used for tracking Tasks classified into 4 stages Todo In progress Testing Done Tasks represented by post-it notes that can be moved as needed

Burndown Chart Typically part of task board Used to monitor progress and schedule

Product Potentially shippable Decision of product owner But should be working Includes cumulative output of all sprints so far

Sprint Planning Part I Part II Team commits to what it will do Analyze product and backlog and set sprint goal What tasks to include in sprint backlog Decided with product owner based on priorities and time estimates Part II Plan the sprint and high-level design issues Estimate effort required Done by team and scrum master Team commits to what it will do

Planning Poker Method to produce effort estimates Every team member has a complete deck of cards After a task is presented, everyone makes an estimate using a card face down All cards turned at once Discussion to reach consensus To avoid anchoring where the initial value spoken influences others

Daily Scrum Every morning At the same time 15 minutes max Standing up Each team member answers 3 questions What did you do yesterday? What will you do today? What is impeding your progress? No discussion

Sprint Review Demo of achievements All stakeholders invited Product owner decides whether team has achieved the sprint’s goals Half day (4 hours)

Sprint Retrospective Team reflects on process What worked What didn’t What don’t we want to do any more? How to improve What do we want to start doing? Half day (3 hours)

Important Values Team autonomy Feedback from outside the team Self organizing Team responsible for estimates and commitments Feedback from outside the team Mainly facilitated by product owner Transparency Everyone can see real progress on a daily basis Problems are aired as soon as they occur