An Introduction To Scrum: Lahcen AFIF 29/03/2012

An Introduction to Scrum
Lahcen AFIF 29/03/2012
Lahcen AFIF M : +32 499 96 64 72 E : lahcen@af.be W : http://lahcen.af.be

mardi 24 avril 12
Gestion de Projet Scrum & Agile Training Web Strategy
Surprising lessons
Marshmallow
The
Challenge
Lahcen Af - IT Consultant - Chef de Projet - PRINCE2 & SCRUM - http://lahcen.af.be

mardi 24 avril 12
Tom Wujec Autodesk
Were losing the relay race

The relay race approach to product developmentmay conict with the goals of maximum speed and exibility. Instead a holistic or rugby approachwhere a team tries to go the distance as a unit, passing the ball back and forthmay better serve todays competitive requirements.
Hirotaka Takeuchi and Ikujiro Nonaka, The New New Product Development Game, Harvard Business Review, January 1986.

mardi 24 avril 12
Predictive methods : 4 phases
one shot

mardi 24 avril 12
Predictive methods : 4 phases
iteration 1
iteration 2

mardi 24 avril 12
Which requirement ?

mardi 24 avril 12
Plan or Value ?
Value Driven Project
Rates of functionalities used in a system-type
Never 80% 12% 17% 50% t 17% Rarely sometimes 12% 42% often Always
(c) Agilbee 2011. All right reserved.

mardi 24 avril 12
- 60 -
1000 500 0 1 K 6000 4000 2000 0 1 11 21
Plan or Value ?
> 80%
40% 50%
Agile Waterfa
A 50% du te Stopper le
20% du bud
source : Agilebee (Patrice Petit)
Attention ! Rsultat m
(c) Agilbee 2011. All right reserved.

mardi 24 avril 12
Plan or Value ?
Waterfall
xed scope budget
Agile
time
variable
budget
time
scope

mardi 24 avril 12
Scrum in 100 words

Scrum is an agile process that allows us to focus on delivering
the highest business value in the shortest time. It allows us to rapidly and repeatedly inspect actual working software (every two weeks to one month). The business sets the priorities. Teams self-organize to determine the best way to deliver the highest priority features. Every two weeks to a month anyone can see real working software and decide to release it as is or continue to enhance it for another sprint.

mardi 24 avril 12
Scrum origins
Jeff Sutherland Ken Schwaber

Initial scrums at Easel Corp in 1993 IDX and 500+ people doing Scrum ADM Scrum presented at OOPSLA 96 with Sutherland Author of three books on Scrum Scrum patterns in PLOPD4
Mike Beedle
Ken Schwaber and Mike Cohn

mardi 24 avril 12
Co-founded Scrum Alliance in 2002, initially within the Agile Alliance

Scrum has been used by:

Microsoft Yahoo Google Electronic Arts High Moon Studios Lockheed Martin Philips Siemens Nokia Capital One BBC
mardi 24 avril 12
Intuit Nielsen Media First American Real Estate BMC Software Ipswitch Lexis Nexis Sabre Salesforce.com Time Warner Turner Broadcasting Oce
Scrum has been used for:

Commercial software In-house development Contract development Fixed-price projects Financial applications ISO 9001-certied applications Embedded systems 24x7 systems with 99.999% uptime requirements the Joint Strike Fighter Video game development FDA-approved, life-critical systems Satellite-control software Websites Handheld software Mobile phones Network switching applications ISV applications Some of the largest applications in use

mardi 24 avril 12
Characteristics
Self-organizing teams Product progresses in a series of monthlong sprints
Requirements are captured as items in a list

of product backlog
No specic engineering practices prescribed Uses generative rules to create an agile

environment for delivering projects
One of the agile processes

mardi 24 avril 12
The Agile Manifesto a statement of values

Individuals and interactions
over
Process and tools
Source: www.agilemanifesto.org
mardi 24 avril 12

Individuals and interactions Working software
over
Process and tools Comprehensive documentation
over
mardi 24 avril 12

Individuals and interactions Working software Customer collaboration
over
Process and tools Comprehensive documentation Contract negotiation
over
over
mardi 24 avril 12

Individuals and interactions Working software Customer collaboration Responding to change
over
Process and tools Comprehensive documentation Contract negotiation Following a plan
over
over
over
mardi 24 avril 12
Self organised team

Let people grab the tasks Macro-management rather than micro-management Why ? To get more committed people and less involved people

mardi 24 avril 12
Project noise level
Source: Strategic Management and Organizational Dynamics by Ralph Stacey in Agile Software Development with Scrum by Ken Schwaber and Mike Beedle.

mardi 24 avril 12
Scrum
Return Gift wrap Cancel Product backlog

mardi 24 avril 12
Scrum
Sprint 2-4 weeks
Return Gift wrap Cancel Product backlog

mardi 24 avril 12
Scrum
Sprint goal Return
Sprint 2-4 weeks
Gift wrap Cancel Product backlog

mardi 24 avril 12
Scrum
Sprint goal Return Sprint backlog Gift wrap Cancel Product backlog
Sprint 2-4 weeks

mardi 24 avril 12
Scrum
Sprint 2-4 weeks
Potentially shippable product increment

mardi 24 avril 12
Scrum
mardi 24 avril 12
Sprint 2-4 weeks
Coupons
Scrum
Sprint goal Return Cancel Coupons Gift wrap Product backlog Sprint backlog
Sprint 2-4 weeks

mardi 24 avril 12
Scrum
24 hours
Sprint goal Return Cancel Coupons Gift wrap Product backlog Sprint backlog
Sprint 2-4 weeks

mardi 24 avril 12
Putting it all together
Image available at www.mountaingoatsoftware.com/scrum

mardi 24 avril 12
Sprints
Scrum projects make progress in a series of
sprints Typical duration is 24 weeks or a calendar month at most A constant duration leads to a better rhythm Product is designed, coded, and tested during the sprint

mardi 24 avril 12
Sequential vs. overlapping development

Requirements Design Code Test
Rather than doing all of one thing at a time... ...Scrum teams do a little of everything all the time
Source: The New New Product Development Game by Takeuchi and Nonaka. Harvard Business Review, January 1986.

mardi 24 avril 12
No changes during
Change
Plan sprint durations around how long you can commit to keeping change out of the sprint
mardi 24 avril 12
Scrum framework
Roles Product owner ScrumMaster Team
Ceremonies Sprint planning Sprint review Sprint retrospective Daily scrum meeting Artifacts Product backlog Sprint backlog Burndown charts

mardi 24 avril 12
Scrum framework

mardi 24 avril 12
Product owner
Dene the features of the product Decide on release date and content Beresponsible for the protability of the
product (ROI)
Prioritize features according to market value Adjustfeatures and priority every iteration,
as needed
Accept or reject work results

mardi 24 avril 12
The ScrumMaster
Represents management to the project Responsible for enacting Scrum values and
mardi 24 avril 12
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 (Programmers, testers, user
experience designers, etc...)
Members should be full-time May be exceptions (e.g., database administrator) Teams are self-organizing Ideally, no titles but rarely a possibility Membership should change only between sprints
mardi 24 avril 12
Scrum framework

mardi 24 avril 12
Sprint planning meeting

Team capacity
Product backlog
Business conditions
Current product
Technology

mardi 24 avril 12

Team capacity
Sprint prioritization
Product backlog
Analyze and evaluate product

backlog Select sprint goal
Business conditions
Current product
Technology

mardi 24 avril 12

Team capacity
Product backlog

Sprint goal
Business conditions
Current product
Technology

mardi 24 avril 12

Team capacity
Product backlog

Sprint goal
Business conditions
Sprint planning
Decide how to achieve sprint goal

Current product
Technology
(design) Create sprint backlog (tasks) from product backlog items (user stories / features) Estimate sprint backlog in hours

mardi 24 avril 12

Team capacity
Product backlog

Sprint goal
Business conditions
Sprint planning
Decide how to achieve sprint goal

Current product
Technology
(design) Create sprint backlog (tasks) from product backlog items (user stories / features) Estimate sprint backlog in hours
Sprint backlog

mardi 24 avril 12
Team selects items from the product backlog they can

commit to completing
Sprint planning
Sprint backlog is created 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 xtures (4) Code the foo class (6) Update performance tests (4)
Tasks are identied and each is estimated (1-16 hours) Collaboratively, not done alone by the ScrumMaster

mardi 24 avril 12
The daily scrum
Parameters

mardi 24 avril 12
Daily 15-minutes Stand-up
Not for problem solving Whole world is invited Only team members, ScrumMaster, product owner, can talk
Helps avoid other unnecessary meetings

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 ScrumMaster They are commitments in front of peers
mardi 24 avril 12
The sprint review

mardi 24 avril 12
Team presents what it accomplished during the sprint Typically takes the form of a demo of new features or underlying architecture Informal
2-hour prep time rule No slides
Whole team participates Invite the world

Sprint retrospective
Periodically take a look at what is and is not
working Typically 1530 minutes Done after every sprint Whole team participates ScrumMaster
Product owner Team Possibly customers and others

mardi 24 avril 12
Start / Stop / Continue

Whole team gathers and discusses what theyd like to:
Start doing Stop doing

This is just one of many ways to do a sprint retrospective.
Continue doing

mardi 24 avril 12
Scrum framework

mardi 24 avril 12
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 owner
Prioritized by the product

This is the product backlog
mardi 24 avril 12
Reprioritized at the start of

each sprint
A sample product backlog
voir exemple : chier XLS

mardi 24 avril 12
The sprint goal
Life Sciences Database Application Make the application run on SQL Server in addition to Oracle. Financial services Support more technical indicators than company ABC with real-time, streaming data.
mardi 24 avril 12
Support features necessary for population genetics studies.
Managing the sprint backlog

Individuals sign up for work of their own choosing Estimated work remaining is updated daily Any team member can add, delete or change the sprint
backlog
Work is never assigned
Work for the sprint emerges If work is unclear, dene a sprint backlog item with a
larger amount of time and break it down later
Update work remaining as more becomes known

mardi 24 avril 12
A sprint backlog
voir exemple : chier XLS

mardi 24 avril 12
A sprint burndown chart

1.000 800
Hours
600
400
200
0
mardi 24 avril 12
Scalability
Typical individual team is 7 2 people Factors in scaling
Scalability comes from teams of teams Type of application Team size Team dispersion Project duration
person projects
Scrum has been used on multiple 500+

mardi 24 avril 12
Scaling through the Scrum of scrums

mardi 24 avril 12
Scaling through the Scrum of scrums

mardi 24 avril 12
Scrum of scrums of scrums

mardi 24 avril 12

mardi 24 avril 12

mardi 24 avril 12
Where to go next
www.mountaingoatsoftware.com/scrum www.scrumalliance.org www.controlchaos.com scrumdevelopment@yahoogroups.com

mardi 24 avril 12
A Scrum reading list

Agile and Iterative Development: A Managers Guide by Craig Larman Agile Estimating and Planning by Mike Cohn Agile Project Management with Scrum by Ken Schwaber Agile Retrospectives by Esther Derby and Diana Larsen Agile Software Development Ecosystems by Jim Highsmith Agile Software Development with Scrum by Ken Schwaber and Mike Beedle Scrum and The Enterprise by Ken Schwaber Succeeding with Agile by Mike Cohn User Stories Applied for Agile Software Development by Mike Cohn
mardi 24 avril 12
Merci
Retrouvez toutes les ressources de cette prsentation sur mon bookmark ladresse suivante : http://delicious.com/lahcen_af/agile
portions of this presentation are from
Mountain Goat Software, LLC!
Lahcen AFIF M : +32 499 96 64 72 E : lahcen@af.be W : http://lahcen.af.be

mardi 24 avril 12
Gestion de Projet Scrum & Agile Training Web Strategy

An Introduction To Scrum: Lahcen AFIF 29/03/2012

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

An Introduction To Scrum: Lahcen AFIF 29/03/2012

Загружено:

Авторское право:

Доступные форматы

An Introduction to Scrum

Lahcen AFIF 29/03/2012

Lahcen AFIF M : +32 499 96 64 72 E : lahcen@af.be W : http://lahcen.af.be

Gestion de Projet Scrum & Agile Training Web Strategy

Lahcen Af - IT Consultant - Chef de Projet - PRINCE2 & SCRUM - http://lahcen.af.be

Tom Wujec Autodesk

Were losing the relay race

Lahcen Af - IT Consultant - Chef de Projet - PRINCE2 & SCRUM - http://lahcen.af.be

Predictive methods : 4 phases

Lahcen Af - IT Consultant - Chef de Projet - PRINCE2 & SCRUM - http://lahcen.af.be

Predictive methods : 4 phases

Lahcen Af - IT Consultant - Chef de Projet - PRINCE2 & SCRUM - http://lahcen.af.be

Lahcen Af - IT Consultant - Chef de Projet - PRINCE2 & SCRUM - http://lahcen.af.be

(c) Agilbee 2011. All right reserved.

Lahcen Af - IT Consultant - Chef de Projet - PRINCE2 & SCRUM - http://lahcen.af.be

1000 500 0 1 K 6000 4000 2000 0 1 11 21

source : Agilebee (Patrice Petit)

(c) Agilbee 2011. All right reserved.

Lahcen Af - IT Consultant - Chef de Projet - PRINCE2 & SCRUM - http://lahcen.af.be

Lahcen Af - IT Consultant - Chef de Projet - PRINCE2 & SCRUM - http://lahcen.af.be

Scrum in 100 words

Lahcen Af - IT Consultant - Chef de Projet - PRINCE2 & SCRUM - http://lahcen.af.be

Ken Schwaber and Mike Cohn

Co-founded Scrum Alliance in 2002, initially within the Agile Alliance

Scrum has been used by:

Lahcen Af - IT Consultant - Chef de Projet - PRINCE2 & SCRUM - http://lahcen.af.be

Scrum has been used for:

Lahcen Af - IT Consultant - Chef de Projet - PRINCE2 & SCRUM - http://lahcen.af.be

Requirements are captured as items in a list

No specic engineering practices prescribed Uses generative rules to create an agile

One of the agile processes

The Agile Manifesto a statement of values

Process and tools

The Agile Manifesto a statement of values

Process and tools Comprehensive documentation

The Agile Manifesto a statement of values

Process and tools Comprehensive documentation Contract negotiation

The Agile Manifesto a statement of values

Process and tools Comprehensive documentation Contract negotiation Following a plan

Self organised team

Lahcen Af - IT Consultant - Chef de Projet - PRINCE2 & SCRUM - http://lahcen.af.be

Project noise level

Lahcen Af - IT Consultant - Chef de Projet - PRINCE2 & SCRUM - http://lahcen.af.be

Return Gift wrap Cancel Product backlog

Sprint 2-4 weeks

Return Gift wrap Cancel Product backlog

Sprint goal Return

Sprint 2-4 weeks

Gift wrap Cancel Product backlog

Sprint 2-4 weeks

Lahcen Af - IT Consultant - Chef de Projet - PRINCE2 & SCRUM - http://lahcen.af.be

Sprint 2-4 weeks

Potentially shippable product increment

Lahcen Af - IT Consultant - Chef de Projet - PRINCE2 & SCRUM - http://lahcen.af.be

Sprint 2-4 weeks

Potentially shippable product increment

Lahcen Af - IT Consultant - Chef de Projet - PRINCE2 & SCRUM - http://lahcen.af.be

Sprint 2-4 weeks

Potentially shippable product increment

Lahcen Af - IT Consultant - Chef de Projet - PRINCE2 & SCRUM - http://lahcen.af.be

Sprint 2-4 weeks

Potentially shippable product increment