Introduction to Scrum Presented at Agile Awareness Workshop conducted by Xebia by Deepak Mittal, IntelliGrape Software on June 14, 2008

Presented

at

Agile Awareness Workshop

conducted by Xebia

by

Deepak Mittal, IntelliGrape Software

on

June 14, 2008

Agenda Agile Manifesto What is Scrum Scrum core ideas Difficulties with practising Scrum Questions Feedback

Agile Manifesto

What is Scrum

Scrum core ideas

Difficulties with practising Scrum

Questions

Feedback

Quick Poll Agile Manifesto. Scrum. Agile methodologies. Requirements can be frozen. Standish Group report.

Agile Manifesto.

Scrum.

Agile methodologies.

Requirements can be frozen.

Standish Group report.

Agile Manifesto Individuals and Interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan.

Individuals and Interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan.

Scrum Framework Roles : Product Owner, Scrum Master, Team Ceremonies : Spring planning, Spring review, Sprint retrospective, Daily Scrum Meeting Artifacts : Product backlog, Spring backlog, Burndown Chart

Roles : Product Owner, Scrum Master, Team

Ceremonies : Spring planning, Spring review, Sprint retrospective, Daily Scrum Meeting

Artifacts : Product backlog, Spring backlog, Burndown Chart

What is Scrum? The name Scrum Prioritized activities in a product backlog Sprint in 30 calendar days (22 working days)‏ Self-organized, crossfunctional teams, 7 +/- 2 Daily stand-up

The name Scrum

Prioritized activities in a product backlog

Sprint in 30 calendar days (22 working days)‏

Self-organized, crossfunctional teams, 7 +/- 2

Daily stand-up

Scrum Flow

Scrum Roles Product owner Scrum master Scrum team (5-9 people)‏

Product owner

Scrum master

Scrum team (5-9 people)‏

Product Owner Maintaining the product backlog Prioritizing Presentation of product backlog to the team Participation in sprint planning and sprint presentation Responsible for product vision, ROI and release management Can follow sprint via Daily Scrum, Burndown chart and via Scrum Master

Maintaining the product backlog

Prioritizing

Presentation of product backlog to the team

Participation in sprint planning and sprint presentation

Responsible for product vision, ROI and release management

Can follow sprint via Daily Scrum, Burndown chart and via Scrum Master

Scrum Team Teams of 7 +/- 2 participants Crossfunctional Best experts in the domain area Maintaining the sprint backlog Self-organizing Team decides who shall do what They inspect and adapt as the sprint goes along Have most of the powers during a sprint

Teams of 7 +/- 2 participants

Crossfunctional

Best experts in the domain area

Maintaining the sprint backlog

Self-organizing

Team decides who shall do what

They inspect and adapt as the sprint goes along

Have most of the powers during a sprint

Scrum Master Responsible for the process Responsible for optimizing the Scrum environment Responsible for Daily Scrum Runs Sprint Retrospective Coach

Responsible for the process

Responsible for optimizing the Scrum environment

Responsible for Daily Scrum

Runs Sprint Retrospective

Coach

Spring Planning / Workshop 1. Product Owner, Team, and other Stakeholders talk through Product Backlog Items and prioritization. 2. Team determines how much time it has available to commit during the Sprint 3 . Team selects as much of the Product Backlog as it can commit to deliver by the end of the Sprint, and turns it into a plan - Validates commitment by breaking down into tasks with time estimates - Team decides who will do what, when; thinks through sequencing, dependencies, possible task trades, and so forth.

1. Product Owner, Team, and other Stakeholders talk through Product Backlog Items and prioritization.

2. Team determines how much time it has available to commit during the Sprint

3 . Team selects as much of the Product Backlog as it can commit to deliver by the end of the Sprint, and turns it into a plan

- Validates commitment by breaking down into tasks with time estimates

- Team decides who will do what, when; thinks through sequencing, dependencies, possible task trades, and so forth.

Daily Scrum Daily Scrum must not last more than 15 minutes Held same place, same time, every working day Participants can not be late Anybody can come, but only the team and Scrum Master can speak 3 questions answered by each team member What did I do yesterday? What am I going to do today? What are my impediments?

Daily Scrum must not last more than 15 minutes

Held same place, same time, every working day

Participants can not be late

Anybody can come, but only the team and Scrum Master can speak

3 questions answered by each team member

What did I do yesterday?

What am I going to do today?

What are my impediments?

Sprint presentation Team presents work done in the sprint. What have we achieved? Should show finished functionality. What is missing. Maximum of 2 hours for presentation.

Team presents work done in the sprint.

What have we achieved?

Should show finished functionality.

What is missing.

Maximum of 2 hours for presentation.

Sprint Retrospective Run by Scrum Master Team reflects on the sprint What went well? What did not go so well? How can we improve?

Run by Scrum Master

Team reflects on the sprint

What went well?

What did not go so well?

How can we improve?

Who is using Scrum? US Federal Reserve SAP H P Motorola TransUnion Google Microsoft Yahoo Sun Siemens Nokia Philips BBC IBM

US Federal Reserve

SAP

H P

Motorola

TransUnion

Google

Microsoft

Yahoo

Sun

Siemens

Nokia

Philips

BBC

IBM

Scrum Core Ideas Everything is time-boxed. Inspect & Adapt. You can-not plan everything. Fail early. Shippable product at the end of every iteration/sprint. Iterative development. Cross-functional teams. Self-organizing teams. Team owns the sprint backlog.

Everything is time-boxed.

Inspect & Adapt.

You can-not plan everything.

Fail early.

Shippable product at the end of every iteration/sprint.

Iterative development.

Cross-functional teams.

Self-organizing teams.

Team owns the sprint backlog.

Common Problems Creating cross-functional teams. Thinking in time-boxed manner – requires discipline. Shifting from the paradigm of TL/PM- ownership to team-ownership. Making use of Sprint retrospective effectively.

Creating cross-functional teams.

Thinking in time-boxed manner – requires discipline.

Shifting from the paradigm of TL/PM- ownership to team-ownership.

Making use of Sprint retrospective effectively.

Questions!

Feedback [email_address]

[email_address]

License This work is licensed under the Creative Commons Attribution-Noncommercial-Share Alike 3.0 License

This work is licensed under the Creative Commons Attribution-Noncommercial-Share Alike 3.0 License