Scrum introduction

Scrum Primer

José Teixidó - Web Development Supervisor

Status Quo

Any similarities to real events in this presentation are not coincidence


Status QuoThe Waterfall or cascade model


Status QuoThe Waterfall

Usually better when single threaded +Works by gravity (stuff always goes down)+Has a constant flow (conveyor effect)=Fail late process

• If something goes wrong you will find out at the worst possible moment• Since you can't go against the current, and stuff keeps flowing down, you can't do anything without a lot of effort and disruption to the process

José Teixidó - Web Development

Supervisor

Status QuoWaterfall, usually this is more like it


Quo vadis?Scrum


Credit: http://www.flickr.com/photos/kiwi/24658003/

ScrumIs based on:

• Empirical process control:o Inspect the facts and adapto Transparency and honesty

• Time boxed iterations (Sprints) • Incremental delivery• Predictability optimization• Risk control


Scrum

Scrum - Who is using it?

• Microsoft• Apple• Google• Samsung• Nokia• Mtvi• + a lot of others...


ScrumThe Roles


ScrumThe Roles

• Pigs (committed)o Product Owner/so Scrum Mastero Team

• Chickens (involved)o Stake Holderso Managers


Scrum

Product Owner

• Maintains the Product Backlog• Prioritizes desirables/features based on ROI• Represents product users and customers• Can be part of the Team but can’t act as Scrum Master


Credit: http://www.flickr.com/photos/popculturegeek/5134635574/

Scrum

The Team

• Estimates• Does the actual work• Self organized cross-functional team• Maintains the Sprint Backlog• Inspects and adapt as the sprint progress• Ideally not just the developers but everybody required to

make the product


Credit: http://www.flickr.com/photos/hyku/2627349317/in/photostream/

Scrum

The Scrum Master

• Enforces Scrum process rules

• Remove team impediments

• Protects the team from disturbances

• Provides Scrum coaching• Can be part of the team


Supervisor

Credit: http://www.flickr.com/photos/fdolleus/3844650865/sizes/z/in/photostream/

Scrum


Scrum

Artifacts - Product Backlog

• Prioritized list of features posted as "User Stories"• Constantly maintained and evolving• Anyone can contribute but the Product Owners

own the Product Backlog


Scrum

Artifacts - Sprint Backlog

• List of features or items taken from the Product Backlog, that are going to be addressed on the next sprint

• The Team owns the Sprint Backlog and is responsible for keeping it updated


ScrumArtifacts - Sprint Burndown

Chart


Scrum

Meetings - Sprint Planing Meeting

• Who: All• What: Product Owners + Team discuss and agree on

which items will make it into the next Sprint based on Team estimations and dev/hour availability

• How long: Usually 2 hr limit• Where: Meeting room


Scrum

Meetings - Daily Stand Up Meeting

• Who: Team + Product Owners, however only the Team can speak (PO's can only speak if requested by somebody on the team)

• How long: 15 mins max, starts on time• Where: Same place each day, team should be

standing and nobody is leading


Scrum

Meetings - Daily Stand Up Meeting

Every Team member needs to answer three questions:

o What have you done since yesterday's Stand Up?o What are you going to do today?o Do you have any problems preventing you from

accomplishing your tasks?


Scrum

Meetings - Review

• Who: Everybody• What:

o Review of what was "done" in the last sprint.o Team discusses successes and problems on the last

sprint


Scrum

Meetings - Retro

• Who: Everybody, Scrum Master leads• What:

o Team + PO reflects on problems and issues during last sprint.

o Scrum Master decides on process changes or adjustments based on input

o This is the basis of the empirical process


Scrum

Meetings - Retro

• Two main questions:o What went well during the last sprint?o What could be improved for the next sprint?

• Inspect and adapt


ScrumSummary

• Scrum is agile, time boxed, adaptive and transparent• 3 Main Roles:

• Product Owner • Scrum Master • Team

• 4 Meetings: • Sprint Planning• Daily Stand Up• Sprint Review• Sprint Retro

• 3 Artifacts: • Product Backlog• Sprint Backlog• Burndown Chart


Supervisor

Scrum

“Scrum makes all news visible, be it good or bad. It considers intelligent

people will want those news regardless so they can do the most beneficial thing for the whole organization”

Ken Shwaber, co-developer of SCRUM Framework


Business

Scrum introduction