Scrum MODULE 3 Part 3 Scrum Image available

Scrum MODULE 3 – Part 3

Scrum Image available at www. mountaingoatsoftware. com/scrum

Sprints Ø Scrum projects make progress in a series of “sprints” o Analogous to Extreme Programming iterations Ø Typical duration is 2– 4 weeks or a calendar month at most Ø A constant duration leads to a better rhythm Ø Product is designed, coded, and tested during the sprint

Scrum Framework Roles • Product owner • Scrum. Master • Team Ceremonies • Sprint planning • Sprint review • Sprint retrospective • Daily scrum meeting Artifacts • Product backlog • Sprint backlog • Burndown charts

Scrum Framework Roles • Product owner • Scrum. Master • Team

Product Owner Ø Define the features of the product Ø Decide on release date and content Ø Be responsible for the profitability of the product (ROI) Ø Prioritize features according to market value Ø Adjust features and priority every iteration, as needed Ø Accept or reject work results

Scrum. Master Ø Represents management to the project Ø Responsible for enacting Scrum values and practices Ø Removes impediments Ø Ensure that the team is fully functional and productive Ø Enable close cooperation across all roles and functions Ø Shield the team from external interferences

The Team Ø Typically 5 -9 people Ø Cross-functional: o Programmers, testers, user experience designers, etc. Ø Members should be full-time o May be exceptions (e. g. , database administrator)

The Team Ø Teams are self-organizing o Ideally, no titles but rarely a possibility Ø Membership should change only between sprints

Scrum Framework Ceremonies • Sprint planning • Sprint review • Sprint retrospective • Daily scrum meeting

Sprint Planning Meeting Team capacity Sprint planning meeting Sprint prioritization Product backlog • • Business conditions Technology Sprint goal Sprint planning • Current product Analyze and evaluate product backlog Select sprint goal • • Decide how to achieve sprint goal (design) Create sprint backlog (tasks) from product backlog items (user stories / features) Estimate sprint backlog in hours Sprint backlog

Sprint Planning Ø Team selects items from the product backlog they can commit to completing Ø Sprint backlog is created o Tasks are identified and each is estimated (1 -16 hours) o Collaboratively, not done alone by the Scrum. Master Ø High-level design is considered As a vacation planner, I want to see photos of the hotels. Code the middle tier (8 hours) Code the user interface (4) Write test fixtures (4) Code the foo class (6) Update performance tests (4)

The Daily Scrum Ø Parameters o Daily o 15 -minutes o Stand-up Ø Not for problem solving o Whole world is invited o Only team members, Scrum. Master, product owner, can talk Ø Helps avoid other unnecessary meetings

The Daily Scrum Ø Everyone answers 3 questions What did you do yesterday? What will you do today? Is anything in your way? 1 2 3 These are not status for the Scrum. Master o They are commitments in front of peers

The Sprint Review Ø Team presents what it accomplished during the sprint Ø Typically takes the form of a demo of new features or underlying architecture Ø Informal o 2 -hour prep time rule o No slides Ø Whole team participates Ø Invite the world

Sprint Retrospective Ø Periodically take a look at what is and is not working Ø Typically 15– 30 minutes Ø Done after every sprint Ø Whole team participates o Scrum. Master o Product owner o Team o Possibly customers and others

Agile Characteristics Whole team gathers and discusses what they’d like to: Start doing Stop doing This is just one of many ways to do a sprint retrospective. Continue doing

Scrum Framework Artifacts • Product backlog • Sprint backlog • Burndown charts

Product Backlog Ø The requirements Ø A list of all desired work on the project Ø Ideally expressed such that each item has value to the users or customers of the product Ø Prioritized by the product This is the owner product backlog Ø Reprioritized at the start of each sprint

A Sample Product Backlog

Agile Characteristics Ø A short statement of what the work will be focused on during the sprint Life Sciences Database Application Support features necessary for population genetics studies. Make the application run on SQL Server in addition to Oracle. Financial services Support more technical indicato than company ABC with realtime, streaming data.

Managing the sprint backlog Ø Individuals sign up for work of their own choosing o Work is never assigned Ø Estimated work remaining is updated daily Ø Any team member can add, delete or change the sprint backlog Ø Work for the sprint emerges

Managing the sprint backlog Ø If work is unclear, define a sprint backlog item with a larger amount of time and break it down later Ø Update work remaining as more becomes known

A Sprint Backlog Tasks Code the user interface Code the middle tier Test the middle tier Write online help Write the foo class Add error logging Mon Tues Wed Thur Fri 8 4 8 16 12 10 4 8 16 16 11 8 8 8 4 12 8

A Sprint Burndown Chart

A Sprint Burndown Chart Tasks Mon Tues Wed Thur Fri 8 16 8 12 Hours Code the user interface Code the middle tier Test the middle tier Write online help 50 40 30 20 10 0 Mon Tue Wed 4 12 16 8 10 16 Thu 7 11 Fri 8

Scalability Ø Typical individual team is 7 ± 2 people o Scalability comes from teams of teams Ø Factors in scaling o Type of application o Team size o Team dispersion o Project duration Ø Scrum has been used on multiple 500+ person projects

Scaling Through the Scrum of scrums

Scrum of scrums

QUESTIONS AND COMMENTS ?