ScrumGuides Agile Estimating And Planning With Scrum

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 2 with SCRUM ©SCRUMguides

Our presence Ukrainian Agile community www.agileukraine.org Join our Google discussion group Ukrainian SCRUM portal www.scrum.com.ua Agile Estimating and Planning 3 with SCRUM ©SCRUMguides

SCRUM recap Agile Estimating and Planning 5 with SCRUM ©SCRUMguides

Agenda ► Levels of Planning Requirements in SCRUM Estimation Techniques Sprint Planning Release Planning Agile Estimating and Planning 6 with SCRUM ©SCRUMguides

The two levels of planning Strategic level / Story level / product backlog Tactical level / Task level / spring backlog Agile Estimating and Planning 7 with SCRUM ©SCRUMguides

From Mike Cohn’s “Planning Agile Projects” Agile Estimating and Planning 8 with SCRUM ©SCRUMguides

Today’s agenda Levels of Planning ► Requirements in SCRUM Estimation Techniques Sprint Planning Release Planning Agile Estimating and Planning 10 with SCRUM ©SCRUMguides

Requirements What are the requirements to requirements? Agile Estimating and Planning 11 with SCRUM ©SCRUMguides

The requirements to requirements? Agile Estimating and Planning 12 with SCRUM ©SCRUMguides

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> Agile Estimating and Planning 13 with SCRUM ©SCRUMguides

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 Agile Estimating and Planning 14 with SCRUM ©SCRUMguides

Samples – Travel reservation system As a vacation planner, I As a user, I can reserve a can see photos of the hotel room. hotels. As a user, I can restrict As a user, I can cancel a searches so that I only see reservation. hotels with available rooms. Agile Estimating and Planning 15 15 with SCRUM ©SCRUMguides

Details added in smaller substories As a premium site member, I can cancel a reservation up to the last minute. As a non-premium As a user, I can member, I can cancel up to cancel a 24 hours in advance. reservation. As a site visitor, I am emailed a confirmation of any cancelled reservation. Agile Estimating and Planning 16 16 with SCRUM ©SCRUMguides

Details added as tests High level tests are added to the story Can be used to express additional details and expectations – As a user, I can cancel a reservation. • 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 user’s card is expired. Agile Estimating and Planning 17 17 with SCRUM ©SCRUMguides

What makes a good story? Independent Negotiable Valuable INVEST Estimatable Small Testable Thanks to Bill Wake for the acronym. See www.xp123.com. Agile Estimating and Planning 18 18 with SCRUM ©SCRUMguides

Agile Estimating and Planning 19 with SCRUM ©SCRUMguides

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. Agile Estimating and Planning 20 20 with SCRUM ©SCRUMguides

The Five Whys Agile Estimating and Planning 21 with SCRUM ©SCRUMguides

User Stories Workshop PO presents his/her Project Vision 1. PO and the team discuss the Users of the system 2. PO and the team dive into brainstorming on User 3. Stories (new Users might appear at this stage) When they have enough stories, they group them, 4. discard duplicates, discuss priorities, etc. At some stage team estimates the stories 5. …. 6. Agile Estimating and Planning 23 with SCRUM ©SCRUMguides

The Project Vision Agile Estimating and Planning 24 with SCRUM ©SCRUMguides

The iPET project Agile Estimating and Planning 25 with SCRUM ©SCRUMguides

Agile Planning Levels of Planning Requirements in SCRUM ► Estimation Techniques Sprint Planning Release Planning Agile Estimating and Planning 26 with SCRUM ©SCRUMguides

From Mike Cohn’s “Agile Estimating and Planning” Agile Estimating and Planning 28 with SCRUM ©SCRUMguides

A typical issue with estimations Agile Estimating and Planning 34 with SCRUM ©SCRUMguides

The “Zoo” project Zebra 1. Hippopotamus 2. Elephant 3. Giraffe 4. Panda 5. Monkey 6. Tiger 7. Bear 8. Sea lion 9. Coyote 10. Agile Estimating and Planning 39 with SCRUM ©SCRUMguides

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. Don’t inflate Agile Estimating and Planning 41 with SCRUM ©SCRUMguides

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. Agile Estimating and Planning 42 with SCRUM ©SCRUMguides

Agile Planning Levels of Planning Requirements in SCRUM Estimation Techniques ► Sprint (Iteration) Planning Release Planning Agile Estimating and Planning 44 with SCRUM ©SCRUMguides

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… Agile Estimating and Planning 50 with SCRUM ©SCRUMguides

Agile Planning Requirements in SCRUM Estimation Techniques Levels of Planning Sprint Planning ► Release Planning Agile Estimating and Planning 51 with SCRUM ©SCRUMguides

Steering your Projects “Ready? Fire! Aim… Aim… Aim… Aim…” © Kent Beck, Martin Fowler “Planning eXtreme Programming” Agile Estimating and Planning 53 with SCRUM ©SCRUMguides

Visualizing the time-scope relationship Release Burndown 2000 1800 1785 1620 1600 1400 Estimations 1200 1000 800 713 600 512 400 324 228 200 175 155 0 1 2 3 4 5 6 7 8 Sprints Agile Estimating and Planning 55 with SCRUM ©SCRUMguides

A SCRUM game To practice the following concepts: Backlog Estimations in points with Planning Poker Sprints Velocity Sprint Planning Meeting Sprint Review Meeting Retrospection Agile Estimating and Planning 60 with SCRUM ©SCRUMguides

Backlog two-stored building 1. catholic church 2. traffic light 3. one-stored building 4. one-stored building 5. tractor 6. kiosk 7. garage for tractor 8. tower cran 9. lorry 10. garage for lorry 11. kinder garden 12. two-stored building 13. one-stored building 14. bus stop 15. Agile Estimating and Planning 61 three-stored building 16. with SCRUM ©SCRUMguides

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 Agile Estimating and Planning 62 with SCRUM ©SCRUMguides

Join our community! Ukrainian Agile community www.agileukraine.org Join our Google discussion group Ukrainian SCRUM portal www.scrum.com.ua Agile Estimating and Planning 63 with SCRUM ©SCRUMguides

ScrumGuides Agile Estimating And Planning With Scrum

0 comments

Notes on slide 1

9 Favorites