13.07.2015 Views

Five Levels Of Planning – Agile Project - Rally Software

Five Levels Of Planning – Agile Project - Rally Software

Five Levels Of Planning – Agile Project - Rally Software

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>Presenter — Hubert SmitsI’m an <strong>Agile</strong> Coach for <strong>Rally</strong> <strong>Software</strong>Development. After spending some 20years in managing large softwaredevelopment projects in Europe I saw thelight, joined the <strong>Agile</strong> Alliance andbecame an agilist. First as an agile projectmanager (ScrumMaster), then a trainerand coach.I now support <strong>Agile</strong> Implementations inthe US, Europe, the Middle East and India.I’ve lectured <strong>Agile</strong> <strong>Software</strong> Developmentat Glasgow University.My main community is still Scrum, I amprivileged to be able to train Scrum-Masters, and I enjoy working with someof the thought leaders in this area.3<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDCPurpose of the Workshop“To learn how to plan agile projectsfrom Product Vision all the way to Daily Stand-up”or:“To feel the effect when 100 peoplePrioritize, Estimate and Committhe plans for a major delivery.”4<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDC(c) 2006 <strong>Rally</strong> SDC 2


<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>Our roadmap for the afternoonIntroduction (30)Product Vision (45)Roadmap (45)Release (25)Iteration (15)Stand-up (15)Summary (5)5<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDCOur roadmap for the afternoonIntroductionProduct VisionRoadmapReleaseIterationStand-upSummary6<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDC(c) 2006 <strong>Rally</strong> SDC 3


<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>The ExercisesFor all of our exercises in this course, we will beconsidering the following product:<strong>Agile</strong>2007 — The ConferenceIt will be the basis of our Product Vision, our ProductRoadmap, our 1 st Release <strong>Planning</strong>, and our 1 st Iteration<strong>Planning</strong>. We may even attempt to start the first iterationwith its own Stand-up!7<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDC<strong>Agile</strong> <strong>Project</strong> BasicsRevisiting agreat process<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong> 2006(c) 2006 <strong>Rally</strong> SDC 4


<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>Scrum – a good example of an agile project structureDaily Scrum Meeting• Done since last meeting• Plan for today• Obstacles?24 hoursSprint <strong>Planning</strong> Meeting• Review Product Backlog• Estimate Sprint Backlog• Commit to 30 days• Sprint GoalBacklog tasksexpandedby team30 daysSprint Review Meeting• Demo features to all• Retrospective on the SprintVisionProduct BacklogPrioritized Featuresdesired by CustomerSprint BacklogFeatures assigned to SprintEstimated by teamPotentially ShippableProduct Increment9<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDCGrowing the <strong>Planning</strong> Model∙ It is hard to ‘see the whole’ when teams plan on aper-iteration basis∙ Feature complexity is hard to manage when it spansiterations∙ Iteration <strong>Planning</strong> by itself does not provide thenecessary tools to manage multi-team releases∙ Distributed teams amplify this challenge even more10<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDC(c) 2006 <strong>Rally</strong> SDC 5


<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>Extending the <strong>Agile</strong> <strong>Planning</strong> FrameworkProduct Management with<strong>Agile</strong> relies on multiple levelsof planning:− Product Vision− Product Roadmap− Release Plan− Iteration Plan− Daily CommitmentVisionRelease 1 Release 2 Release 3Iteration 1 Iteration 2 Iteration 3 Iteration 4Task 1 Task 2 … Task nWho, What, How LongWho, What, How Long11<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDCExtended <strong>Planning</strong> Cycle & Rhythms12<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDC(c) 2006 <strong>Rally</strong> SDC 6


<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>Product Visioning<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong> 2006Product Vision Elevator Statement –Geoffrey Moore∙ FOR (target customer)∙ WHO (statement of the need)∙ THE (product name) is a (product category)∙ THAT (product key benefit, compelling reason to buy).∙ UNLIKE (primary competitive alternative),∙ OUR PRODUCT (final statement of primarydifferentiation)Geoffrey Moore “Crossing the Chasm”14<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDC(c) 2006 <strong>Rally</strong> SDC 7


<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>Product Box Visioning–Jim HighsmithJim Highsmith,<strong>Agile</strong> <strong>Project</strong> Management15<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDCExercise: Creating an Elevator Statement∙∙∙∙∙∙∙Form a group at your tableFor our <strong>Agile</strong>2007 product consider the Product VisionCreate an elevator statement with the six componentsWrite the statement on a flipchart with “<strong>Agile</strong>2007 Vision” at thetopTimebox: 10 minutesPrepare to present to the groupElevator Statement:− FOR (target customer)− WHO (statement of the need)− THE (product name) is a (product category)− THAT (product key benefit, compelling reason to buy).− UNLIKE (primary competitive alternative),− OUR PRODUCT (final statement of primary differentiation)16<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDC(c) 2006 <strong>Rally</strong> SDC 8


<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>Exercise: Creating the Product Box∙ Form a group at your table∙ For our <strong>Agile</strong>2007 product consider it as a shrinkwrappeditem on a shelf∙ On a flipchart create the following product box, frontand back:− Label your flipchart “<strong>Agile</strong>2007 Vision”− FRONT represents marketing splash, logo− BACK represents specs, details− Be creative− 10 minutes− Be prepared to exhibityour artwork! FRONT BACK17<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDCProduct Roadmap<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong> 2006(c) 2006 <strong>Rally</strong> SDC 9


<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>Product Roadmap – an example19<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDCProduct Roadmap – an exampleApril 8, ‘06June 3, ‘06July 8, ‘06Aug 12, ‘06Magnesium2006.2Aluminum2006.3Silicon2006.4Phosphorus2006.5•For all users, improvecustomization andconsistency.•For Product Owners,improve Roadmap, andRelease <strong>Planning</strong>.<strong>Agile</strong> PM• Custom Enumerations• Unified Backlog <strong>Planning</strong>• New Release Status ViewSystem Mgmt.Comm. & CollaborationPlatform•UI Consistency•For all users, improveusability, navigation andinformation presentation.<strong>Agile</strong> PM• <strong>Agile</strong> Product ManagerSystem Mgmt.• Ajax-Enabled Detail PagesComm. & CollaborationPlatform•Improved UIResponsiveness• Improved Navigation• For <strong>Rally</strong> customers,implement some of themost requestedenhancements<strong>Agile</strong> PM• Defect DropdownCustomization•Task RankingSystem Mgmt.• Defect Close Rate MetricsComm. & Collaboration• User FilterableNotificationsPlatform•Shared Custom Views• For all users, enhanceflexibility ofrequirements hierarchy•Provide ConfigurableEditions includeEnterprise<strong>Agile</strong> PM• Associate Iterations withReleasesSystem Mgmt.• Hierarchical Stories• Daily Defect MetricsComm. & CollaborationPlatform• Tab Customization & WebTabs20*<strong>Rally</strong> <strong>Agile</strong> Pro Edition only<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDC(c) 2006 <strong>Rally</strong> SDC 10


<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>Exercise: Defining a Product Roadmap∙ Form teams again around your Product Vision∙ Select one person to be the Product Owner∙ For your <strong>Agile</strong>2007 Product Vision, create a one-yearRoadmap:− Define four releases, one per quarter where each release isdefined as a box in a four box roadmap− For each release, declare a theme− For the theme list 5 – 7 epics to be completed− Remember that detail for the soonest release may have moreclarity and detail than for the final release− Capture your four box roadmap on a flipchart− Make sure that your roadmap is approved by the ProductOwner!− The Product Owner will present the roadmap for the team− 10 minutes21<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDCThe Roadmap Jumpstarts the Product Backlog∙All possible system featuresare captured in a prioritizedlist – the Product BacklogHighpriorityEach Sprint implements thehighest priority features∙∙∙New features can be addedat any time to the ProductBacklog by anyoneFeatures have only a grossestimate of effort and valueProduct Owner prioritizes theProduct BacklogEach new feature isprioritized and added tothe stackFeatures may bereprioritized at any timeFeatures may beremoved at any timeLowpriorityFeatures© 2004, Scott W. Ambler22<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDC(c) 2006 <strong>Rally</strong> SDC 11


<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>An Example Backlog -- Doggy Daycare Brochure∙∙∙∙∙∙∙∙∙∙∙∙∙∙∙Create cover art, brand, and/or logoDefine major care sectionsDefine “Ultra Doggy Spa” serviceOutline boarding optionsWrite testimonialsDefine all service offeringsSet pricing structure for servicesSuggest daypack contents to accompany clientsOutline full week lunch menuComplete a guarantee policyProvide satisfied customer testimonialsComplete a certification structureOutline minimum requirements (shots, temper, breeding, etc.)Complete bios on staff members (backgrounds, training,interests)Define discounted partner pet services23<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDCExercise: Defining a Product Backlog∙ Form teams again around your Roadmap∙ Review the first Release theme and its epics∙ Label a flipchart “Release 1 Backlog”∙ Create 15 – 20 items for that theme∙ Place them in priority order∙ Provide a gross-level estimate (S, M, L, XL)∙ 10 minutes24<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDC(c) 2006 <strong>Rally</strong> SDC 12


<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>Release <strong>Planning</strong><strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong> 2006Product Owner Presents Highest Priority Featuresfrom Product Backlog26<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDC(c) 2006 <strong>Rally</strong> SDC 13


<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>Team Breaks Features into Smaller “Stories”27<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDCDelivery Team Gives Story Estimates28<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDC(c) 2006 <strong>Rally</strong> SDC 14


<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>ScrumMaster and Product Owner at Work29<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDCTeam Moves Stories Across Iterations30<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDC(c) 2006 <strong>Rally</strong> SDC 15


<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>Exercise: Conducting a Release <strong>Planning</strong> Session∙ In your team, plan the first Release of your <strong>Agile</strong>2007roadmap:− Review the Release theme and backlog− Create a flipchart with three boxes on it: Iteration 1, Iteration2, Iteration 3− Through discussion as a group, brainstorm high-level storiesthat would comprise the items− Put each story on a post-it note− You should have at least 10 – 15 stories defined for yourRelease− Physically arrange the stories across the three iterations basedon what could be done in four-week increments with the teamthat you have− Post all your decisions and assumptions on the wall as well− 20 minutes33<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDCIteration <strong>Planning</strong><strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong> 2006(c) 2006 <strong>Rally</strong> SDC 17


<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>Team Agrees on the Release Plan35<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDCSample Iteration Plan36<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDC(c) 2006 <strong>Rally</strong> SDC 18


<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>Iteration Plan Consensus37<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDCExercise: Defining “Done”∙ In your team, consider what it means to complete afeature in an iteration:− Which artifacts are delivered− Are they documented, and how− Can or need they be tested− How is an artifact accepted− What else is produced as part of a feature∙ Use a flipchart, label this one: “Definition of Done”∙ Collect all the parts of “Done” on the chart∙ Post all your decisions and assumptions on the wall aswell∙ Choose a team representative to debrief to the group∙ 5 minutes38<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDC(c) 2006 <strong>Rally</strong> SDC 19


<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>Example definition of “Done”39<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDCExercise: Conducting an Iteration <strong>Planning</strong> Session∙ In your team, plan the first Iteration of your firstRelease:− Review the release theme and all the features in the firstiteration− Create a flipchart with the features on post-it notes− Line the features horizontally− Through discussion as a group, brainstorm the IterationTheme− Also brainstorm the tasks that make up each feature− Put each task on a post-it note – different color from thefeatures− You should have app. 2-5 tasks per feature− Estimate the work involved in each task− Post all your decisions and assumptions on the wall as well− 20 minutes40<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDC(c) 2006 <strong>Rally</strong> SDC 20


<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>Daily Stand-up<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong> 2006Daily Standup– the team is tracking itself42<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDC(c) 2006 <strong>Rally</strong> SDC 21


<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>Scrum of ScrumsWhat did I do yesterday?What will I work on today?What is getting in my way?43<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDCTeams of Teams Stand Up Too!44<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDC(c) 2006 <strong>Rally</strong> SDC 22


<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>Exercise: The Stand-Up Meeting∙ We need a group of 8 people∙ Who is willing to be the ScrumMaster?∙ Imagine that you're a member of a team developing an<strong>Agile</strong>2007 track.∙ Take a moment to decide what you've been workingon and how you'll answer the three questions.∙ Each of you will get a “secret goal”; this card is for youonly to see. During the scene, you'll have this goal ashidden second agenda∙ If the ScrumMaster addresses your behavior, thendon't persist in it45<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDCSummary<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong> 2006(c) 2006 <strong>Rally</strong> SDC 23


<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>Purpose of the Workshop“To learn how to plan agile projectsfrom Product Vision all the way to Daily Stand-up”or:“To feel the effect when 100 peoplePrioritize, Estimate and Committhe plans for a major delivery.”47<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDCOur roadmap for the afternoonIntroductionProduct VisionRoadmapReleaseIterationStand-upSummary48<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong>© 2006, <strong>Rally</strong> SDC(c) 2006 <strong>Rally</strong> SDC 24


<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>Thank youjean@rallydev.comhubert@rallydev.com<strong>Five</strong> <strong>Levels</strong> of <strong>Planning</strong>, <strong>Rally</strong> <strong>Software</strong> 2006(c) 2006 <strong>Rally</strong> SDC 25

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!