Agile Estimating and Planning With SCRUM: 14 February 2009

Agile Estimating and Planning with SCRUM
www.scrumguides.com
14 February 2009
About myself
Alexey Krivitsky Software developer, Agile coach Certified ScrumMaster Certified Scrum Practitioner http://www.linkedin.com/in/alexeykrivitsky email: alexey@scrumguides.com skype: alexeykrv icq: 436-471-64 gsm: +380 50 358 92 12 Currently building up a training center www.scrumguides.com
Agile Estimating and Planning with SCRUM SCRUMguides
Our presence
Ukrainian Agile community www.agileukraine.org Join our Google discussion group
Ukrainian SCRUM portal www.scrum.com.ua
SCRUM recap
Agenda
Levels of Planning Requirements in SCRUM Estimation Techniques Sprint Planning

6
Release Planning
The two levels of planning Strategic level / Story level / product backlog Tactical level / Task level / spring backlog
From Mike Cohns Planning Agile Projects
Todays agenda Levels of Planning Requirements in SCRUM Estimation Techniques
Sprint Planning Release Planning

10
Requirements What are the requirements to requirements?
11
The requirements to requirements?
12
User Story is
User stories are simple, clear, brief descriptions of functionality that will be valuable to either a user or purchaser of a product
Expressed in a form like:
As a <user> I can <do> so that <value>

13
Key ideas of User Stories They highlight negotiation to happen between the customer and the team. User stories help deferring details till later They talk problems not solutions They fit nicely as your Product Backlog items
14
Samples Travel reservation system
As a user, I can reserve a hotel room.
As a vacation planner, I can see photos of the hotels. As a user, I can restrict searches so that I only see hotels with available rooms.
Agile Estimating and Planning 15 with SCRUM SCRUMguides
As a user, I can cancel a reservation.
15
Details added in smaller substories

As a premium site member, I can cancel a reservation up to the last minute. As a non-premium member, I can cancel up to 24 hours in advance.
As a site visitor, I am emailed a confirmation of any cancelled reservation.
16
Details added as tests

High level tests are added to the story
Can be used to express additional details and expectations

Verify that a premium member can cancel the same day without a fee. Verify that a non-premium member is charged 10% for a same-day cancellation. Verify that an email confirmation is sent. Verify that the hotel is notified of any cancellation. Figure out what to do if the users card is expired.
17
What makes a good story?

Independent Negotiable
INVEST
Valuable Estimatable Small Testable
18
Thanks to Bill Wake for the acronym. See www.xp123.com.
19
Making good user stories

How would you rewrite the following requirement to make it a good user story?
All connections to the database are through a connection pool.
20
The Five Whys
21
User Stories Workshop

1. 2. 3.
PO presents his/her Project Vision PO and the team discuss the Users of the system PO and the team dive into brainstorming on User Stories (new Users might appear at this stage) When they have enough stories, they group them, discard duplicates, discuss priorities, etc. At some stage team estimates the stories .
4.
5. 6.
23
The Project Vision
24
The iPET project
25
Agile Planning
Levels of Planning Requirements in SCRUM Estimation Techniques Sprint Planning

26
Release Planning
27
From Mike Cohns Agile Estimating and Planning
28
29
30
31
32
33
A typical issue with estimations
34
35
36
37
38
The Zoo project

1. 2. 3. 4. 5. 6. 7. 8. 9. 10.
Zebra Hippopotamus Elephant Giraffe Panda Monkey Tiger Bear Sea lion Coyote
39
40
Estimating in Story Points

Means the relative size of the story:

Login screen is 2 Search feature is 4 (twice bigger)
Unit-less points. Integrated level of understanding, complexity, risks, feelings Precision is enough for release planning. Easy to estimate, harder to explain. Dont inflate
41
Estimating in Ideal Time

Think of Ideal Time as when

You have no interruptions You have all you need You feel good
Think of how many productive hours a day you usually have. Hard to agree, easy to argue:

I can do it in 10 hours, you can do it in 5. So who is right? Today I think it is 10h, next month (when I know more) I think it is 2
Easier to explain, harder to estimate. Time estimates might inflate.
42
Agile Planning
Levels of Planning Requirements in SCRUM Estimation Techniques Sprint (Iteration) Planning

44
Release Planning
45
46
47
48
49
What DONE means Before you start estimating it is very important to agree with your PO on done criteria for the whole product increment. - So is it done? (the client asks the team) - Yes! - Can I ship it to my clients today? - Well We will need 2 days to finish something there
50
Agile Planning
Requirements in SCRUM Estimation Techniques Levels of Planning Sprint Planning

51
Release Planning
52
Steering your Projects
Ready? Fire! Aim Aim Aim Aim

Kent Beck, Martin Fowler Planning eXtreme Programming
53
There are four main parameters to planning
54
Visualizing the time-scope relationship

Release Burndown
2000 1800 1600 Estimations 1400 1200 1000 800 600 400 200 0 1 2 3 4 5 6 7 8 Sprints
1785 1620
713 512 324 155 228 175
55
56
57
58
Calibrating Velocity
59
A SCRUM game To practice the following concepts: Backlog Estimations in points with Planning Poker Sprints Velocity Sprint Planning Meeting Sprint Review Meeting Retrospection
60
Backlog
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15.
61
16.
two-stored building catholic church traffic light one-stored building one-stored building tractor kiosk garage for tractor tower cran lorry garage for lorry kinder garden two-stored building one-stored building bus stop three-stored building
The cycle Estimate new stories Sprint planning - 3 min

Expected velocity Everyone knows what to work on
Sprint - 3 min Demo - 3 min

Actual velocity Updated release plan

Retrospection - 3 min
62
Join our community!

Ukrainian Agile community www.agileukraine.org Join our Google discussion group
Ukrainian SCRUM portal www.scrum.com.ua
63

Agile Estimating and Planning With SCRUM: 14 February 2009

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Agile Estimating and Planning With SCRUM: 14 February 2009

Uploaded by

Copyright:

Available Formats

Agile Estimating and Planning with SCRUM

Agile Estimating and Planning with SCRUM SCRUMguides

Ukrainian SCRUM portal www.scrum.com.ua

Agile Estimating and Planning with SCRUM SCRUMguides

Agile Estimating and Planning with SCRUM SCRUMguides

Levels of Planning Requirements in SCRUM Estimation Techniques Sprint Planning

Agile Estimating and Planning with SCRUM SCRUMguides

Agile Estimating and Planning with SCRUM SCRUMguides

From Mike Cohns Planning Agile Projects

Agile Estimating and Planning with SCRUM SCRUMguides

Todays agenda Levels of Planning Requirements in SCRUM Estimation Techniques

Sprint Planning Release Planning

Requirements What are the requirements to requirements?

Agile Estimating and Planning with SCRUM SCRUMguides

The requirements to requirements?

Agile Estimating and Planning with SCRUM SCRUMguides

As a <user> I can <do> so that <value>

Agile Estimating and Planning with SCRUM SCRUMguides

Samples Travel reservation system

As a user, I can reserve a hotel room.

As a user, I can cancel a reservation.

Details added in smaller substories

As a user, I can cancel a reservation.

As a site visitor, I am emailed a confirmation of any cancelled reservation.

Agile Estimating and Planning 16 with SCRUM SCRUMguides

Details added as tests

Can be used to express additional details and expectations

As a user, I can cancel a reservation.

Agile Estimating and Planning 17 with SCRUM SCRUMguides

What makes a good story?

Valuable Estimatable Small Testable

Thanks to Bill Wake for the acronym. See www.xp123.com.

Agile Estimating and Planning 18 with SCRUM SCRUMguides

Agile Estimating and Planning with SCRUM SCRUMguides

Making good user stories

All connections to the database are through a connection pool.

Agile Estimating and Planning 20 with SCRUM SCRUMguides

The Five Whys

Agile Estimating and Planning with SCRUM SCRUMguides

User Stories Workshop

The Project Vision

Agile Estimating and Planning with SCRUM SCRUMguides

The iPET project

Agile Estimating and Planning with SCRUM SCRUMguides

Levels of Planning Requirements in SCRUM Estimation Techniques Sprint Planning

Agile Estimating and Planning with SCRUM SCRUMguides

Agile Estimating and Planning with SCRUM SCRUMguides

From Mike Cohns Agile Estimating and Planning

Agile Estimating and Planning with SCRUM SCRUMguides

Agile Estimating and Planning with SCRUM SCRUMguides

Agile Estimating and Planning with SCRUM SCRUMguides

Agile Estimating and Planning with SCRUM SCRUMguides

Agile Estimating and Planning with SCRUM SCRUMguides

Agile Estimating and Planning with SCRUM SCRUMguides

A typical issue with estimations

Agile Estimating and Planning with SCRUM SCRUMguides

Agile Estimating and Planning with SCRUM SCRUMguides

Agile Estimating and Planning with SCRUM SCRUMguides

Agile Estimating and Planning with SCRUM SCRUMguides

Agile Estimating and Planning with SCRUM SCRUMguides

The Zoo project

From Mike Cohns Agile Estimating and Planning