Agile Planning Estimation

Agile Planning, Estimation, and Tracking Syed Rayhan Co-founder, Code71, Inc. Contact: srayhan@code71.com Blog: http://blog.syedrayhan.com Company: http://www.code71.com Product: http://www.scrumpad.com http://www.scrumpad.com http://www.code71.com Copyright 2010 Code71 Inc. All rights reserved .

Agenda Section 1 Introduction Section 2 Planning Section 3 Estimation Section 4 Tracking Section 5 Recap Section 6 Q&A www.Code71.com Copyright 2010 Code71 Inc. All rights reserved . www.ScrumPad.com 2

My Background  Co-founder, Code71, Inc., CSP, Agile Coach and Trainer Career  14+ years of total experience  Co-author of “Enterprise Java with UML”  Iterative incremental development Ex pertise  Technology planning and architecture  On-shore/Off-shore software development using Agile/Scrum  Cultural aspect of self-organizing team  Scrum for projects delivered remotely Int erest s  Agile engineering practices  Lean Startup www.Code71.com Copyright 2010 Code71 Inc. All rights reserved . www.ScrumPad.com 3

What to Expect  Teams and organizations are adopting Agile/Scrum Contex t  Teams struggle with making the transition from waterfall to Agile/Scrum  Build a base for Agile planning Focus  Contrast Agile planning with Traditional Planning  Address typical questions asked  How to perform sprint planning and estimation  How to perform release planning an estimation K ey  How to track progress against plan T akeaways  How to adjust plan as project evolves www.Code71.com Copyright 2010 Code71 Inc. All rights reserved . www.ScrumPad.com 4

Planning A gile Wat erfall Empirical Predict ive It erat ive, incremental A ll or none Priorit izat ion is key act ivit y of Priorit izat ion is not import ant planning Crit ical path is eliminat ed through Crit ical pat h is import ant t ime box ing Planning becomes a prioritization exercise www.Code71.com Copyright 2010 Code71 Inc. All rights reserved . www.ScrumPad.com 8

How to do prioritization? Informal A d-hoc and int uit ive MoSCoW Must have, Should have, Could have, Would not have Calculated Priorit y = Business V alue/Complex ity Formal ROI (= Business value – Cost ) based priorit izat ion K ano Mandat ory, Linear, Ex cit er www.Code71.com Copyright 2010 Code71 Inc. All rights reserved . www.ScrumPad.com 9

MoSCoW Must Minimum U sable S ubse T for haves product ion (a.k .a. Minimum V iable Product ) Should haves Import ant , but absence of it would not mak e t he product useless Could Opt ional, if fund and t ime are available haves Would not Out of scope, defines t he boundary of t he haves product Pros and Cons? www.Code71.com Copyright 2010 Code71 Inc. All rights reserved . www.ScrumPad.com 10

Kano Analysis Survey Q#1 Rate your satisfaction if the product has “this” feature? Q#2 Rate your satisfaction if the product does not have “this” feature? Answers: A) Like it, B) Neutral, C) Dislike it Additional Question for trade-off analysis How much extra would you pay for “this” or more of “this” feature? www.Code71.com Copyright 2010 Code71 Inc. All rights reserved . www.ScrumPad.com 12

Kano Analysis Q#1 (Presence of a feat ure) Like Neutral Dislike - ? Q#2 (A bsence of a feat ure) L Like Neut ra E I ? l Dislike L T - - disregard, ? probe further, I indifferent E exciter, L linier, T threshold www.Code71.com Copyright 2010 Code71 Inc. All rights reserved . www.ScrumPad.com 13

Formal BV Complexity Priority High Low 1 High Medium 2 High High 3? Medium Low 4? Low Low 5? Medium Medium 6? Medium High 7 Low Medium 8 Low High 9 Pros and Cons? www.Code71.com Copyright 2010 Code71 Inc. All rights reserved . www.ScrumPad.com 14

Release Planning • Set a release goal • Determine scope through prioritization • Determine a release date • Define sprints • Allocate stories to sprints • Product backlog grooming • Ideally release every sprint www.Code71.com Copyright 2010 Code71 Inc. All rights reserved . www.ScrumPad.com 15

Sprint Planning Capacity Scope Estimation • Load factor • Set a sprint goal • Task breakdown • Availability factor • Take stories from • Estimate tasks in the top of the actual hours or days • Holidays product backlog • Assign task owners • Vacations • Total points = • Assign a story owner Velocity • Verify estimate against capacity www.Code71.com Copyright 2010 Code71 Inc. All rights reserved . www.ScrumPad.com 16

Rules of thumb for Sprint Planning • Tasks should be between 4 -16 hours • For a two-week sprint (most popular sprint length) • 2-4 hours planning • 1-2 hours of sprint review • 1-2 hours of sprint retrospective • Allocate a fixed hours for production support or other unavoidable routine work (10-15%) • 10% for product backlog grooming www.Code71.com Copyright 2010 Code71 Inc. All rights reserved . www.ScrumPad.com 17

Sprint 0 • Project initiation sprint • Business case • Environment setup • Architecture • Team setup • Team norms • Training www.Code71.com Copyright 2010 Code71 Inc. All rights reserved . www.ScrumPad.com 18

Integration / Stabilization Sprint • One or more sprints needed to stabilize a release before final rollout • Ideally a product is always ready for rollout • Final integration and regression tests • Load test • Any last minute bug fixes • Production environment setup • Any other steps (organization specific) needed before production rollout www.Code71.com Copyright 2010 Code71 Inc. All rights reserved . www.ScrumPad.com 19

Rules of thumb • A team size of 7-9 • 1 and half medium stories per developer • 1 Tester for every two developers • Do not change sprint length • Prefer 100% allocation over partial allocation of people www.Code71.com Copyright 2010 Code71 Inc. All rights reserved . www.ScrumPad.com 20

How do we know when we are done? design review code review architecture load test design+code+unit test functional test regression test www.Code71.com Copyright 2010 Code71 Inc. All rights reserved . www.ScrumPad.com 23

Estimation Relative Absolute Story points Hours/Days Used for Release planning Used for Sprint planning Accuracy is not important Accuracy is important to some extant Eliminates bias Does not eliminate bias Cannot be compared with Supports comparison another team’s Why relative est imation? V elocit y, suit able for longer horizon www.Code71.com Copyright 2010 Code71 Inc. All rights reserved . www.ScrumPad.com 25

Relative estimation using “Planning Poker” Decide on scale Fibonacci scale (1, 2, 3, 5, 8, 13, 21…) Identify a reference story set Use most understood story as a reference story for each level on the scale Everybody estimates individually, then Estimate the rest reveals as a team, hence the term “Planning Poker” Challenges? www.Code71.com Copyright 2010 Code71 Inc. All rights reserved . www.ScrumPad.com 26

How to resolve disagreement in estimation? Consensus A sk the out liers and discuss as a t eam t o agree on an est imat e Majorit y Pick t he one t hat was chosen by t he majority Choose t he T o err on the side of caution highest Pros and Cons? www.Code71.com Copyright 2010 Code71 Inc. All rights reserved . www.ScrumPad.com 27

Velocity Definition Points delivered by a team per sprint How to calculate? Rolling average of 4 weeks, Max, Min, Lifetime average • Velocity without a quality metric is not useful • Velocity of two teams are not comparable • Velocity changes with team composition Keep in mind • Velocity increases with team’s tenure • Velocity is not productivity • Do not include bugs and rejected stories • Used to determine sprint scope How to use? • Used to calculate approximate costs of a release • Used to track release progress www.Code71.com Copyright 2010 Code71 Inc. All rights reserved . www.ScrumPad.com 28

How do you track progress? MS Project 50% done Wat erfall V s. ScrumPad 3 st ories done, 5 st ories remaining A gile Y ou don’t get credit for part ial work www.Code71.com Copyright 2010 Code71 Inc. All rights reserved . www.ScrumPad.com 30

Tracking progress Sprint Burndown Track remaining hours, track done/remaining points by day Release Burndown Track remaining points by sprint Sprint Burnup Track time spent by day Metrics Velocity, Bug find rate per sprint, Bug fix rate per sprint, Test coverage www.Code71.com Copyright 2010 Code71 Inc. All rights reserved . www.ScrumPad.com 31

Tracking progress Daily Scrum A 15-minute standup meeting where team answers the following; tracking 1) What did I do yesterday? impediments 2) What am I going to work on today? 3) What is impeding my work, if any? Sprint Review Team meets with the product owner and stakeholders to show the work done in the current sprint and solicit feedback. www.Code71.com Copyright 2010 Code71 Inc. All rights reserved . www.ScrumPad.com 32

Continuous Improvement (Inspect and Adapt) Retrospective Team meets at the end of each sprint to discuss-  What is working well?  What needs improvement? And  How to improve/fix it? www.Code71.com Copyright 2010 Code71 Inc. All rights reserved . www.ScrumPad.com 33

Let’s test our understanding  Difference between relative vs. absolute estimation?  How to do resource allocation?  How to handle shared resources?  How to plan for production support work?  Do you still need a Gantt chart?  How to plan for fixed bid contract?  Who does planning?  What is velocity?  How to improve estimation?  How do you ensure team delivers what they plan to deliver in a sprint? www.Code71.com Copyright 2010 Code71 Inc. All rights reserved . www.ScrumPad.com 36

Recap  Prioritize product backlog on an on-going basis  Estimate backlog in story points for release planning  Estimate backlog in actual hours or days for sprint planning  Pick a suitable sprint length and stick with it  Allocate people to a single project in a single sprint  Staff the team in the beginning and keep the team in place through out the life of the project www.Code71.com Copyright 2010 Code71 Inc. All rights reserved . www.ScrumPad.com 37

Recap contd.  The team should be cross-functional- include testers, Sys admins, DBA, SMEs  Team should be physically or virtually collocated  Know your team “velocity”  Use open space  Use appropriate information radiators www.Code71.com Copyright 2010 Code71 Inc. All rights reserved . www.ScrumPad.com 38

Q&A Please contact for on-site training or Webinar: Contact: srayhan@code71.com Blog: http://blog.syedrayhan.com Company: http://www.code71.com Product: http://www.scrumpad.com www.Code71.com Copyright 2010 Code71 Inc. All rights reserved . www.ScrumPad.com 39

http://www.scrumpad.com	267
http://cms.scrumpad.com	229
http://scrumpad.wpengine.com	167
http://www.code71.com	17
http://www.slideshare.net	16
http://localhost	10
http://code71.com	2
http://cra.scrumpad.com	1
https://www.scrumpad.com	1
http://translate.googleusercontent.com	1
https://etiprojects.scrumpad.com	1
http://spcms.test.nascenia.com	1

Agile Planning Estimation

by Syed Rayhan

Accessibility

Categories

Upload Details

Usage Rights

12 Embeds 713

Statistics

Agile Planning Estimation Presentation Transcript