ScrumandtheBusinessAnalyst(2)

ScrumandtheBusinessAnalyst

Reporting and MetricsDaily StandupReports/ Metrics Business OwnerSprint BacklogStories TasksSprint/ IterationIncrement of ProductProduct BacklogSprint Progress Release Progress How are we doing?Product29Copyright © 2007 Net Objectives. All Rights Reserved.1 August 2007Burn‐Down Chart to Show ProgressEvery day throughout the iteration:– See how many stories you’ve completed – Add up the story‐points completed – Does the slope of the graph get you to zero at the end? raph et o eroIf not, do a midcourse correction (note removed story on day 7)Sprint Burndow n Graph 180 160 Story Points s/Tasks 140 120 100 80 60 40 20 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Days in Sprint30Copyright © 2007 Net Objectives. All Rights Reserved.1 August 2007

ScrumandtheBusinessAnalyst

Burn‐Up Chart to Show ProgressSame data as burn‐down chart, but easier to see what happenedSprint Burn Up Chart180 160 St tory Points/Tasks 140 120 100 80 60 40 20 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Days in Sprint31Copyright © 2007 Net Objectives. All Rights Reserved.1 August 2007info@ Scrum Meetings

ScrumandtheBusinessAnalyst

Sprint Planning MeetingReports/ MetricsDaily StandupSprint BacklogStories TasksSprint/ Iteration Increment of ProductProduct BacklogProduct33Copyright © 2007 Net Objectives. All Rights Reserved.1 August 2007Sprint Planning Meeting Rules1 day 1st ‐ 3 hours max. for DevTeam and Product Owner to set sprint goals and select subset of Product Backlog to work on (PO job – prioritize work todo) 2nd ‐ 3 hours max. for DevTeam and OnsiteCustomers to define Sprint Backlog to build functionality (decompose to tasks and provide estimates) 3rd – 1 hour max. Get back together and decide what we will actually doArrr! They be more what you'd call guidelines than actual rules.34Copyright © 2007 Net Objectives. All Rights Reserved.1 August 2007

ScrumandtheBusinessAnalyst

Daily Stand‐Up Meeting15 minutes every day Yep…standing (if physically possible) Three(+) questions:– – – – What did you do yesterday? What will you do today? What is standing in your way? + how many hours left on your current task? k? – + how are you feeling today (1‐5)?Daily StandupReports/ MetricsSprint/ IterationThink about “How is this valuable to the team?”35 Copyright © 2007 Net Objectives. All Rights Reserved. 1 August 2007Scrum Master Visibly Documents All ImpedimentsExamples:– – – – The test machine is not ready The build process requires too much “hand‐holding” Joe Stakeholder is not available to validate a Story Sally getting torn away for bug‐fixing on the current release36Copyright © 2007 Net Objectives. All Rights Reserved.1 August 2007

ScrumandtheBusinessAnalyst

Sprint ReviewReports/ MetricsDaily StandupSprint BacklogStories TasksSprint/ Iteration Increment of ProductProduct BacklogProduct37Copyright © 2007 Net Objectives. All Rights Reserved.1 August 2007Sprint ReviewThe Team presents Sprint results to Product Champion and other Stakeholders– – – – – Demonstrate th P d t D t t the Product Present results of Functional Tests Describe progress towards release Raise significant, unresolved impediments Show anything else you want to communicateNote – This is an informal presentation!– No powerpoint necessary, just show off the new features – Purpose is to provide visibility, and inspiration38Copyright © 2007 Net Objectives. All Rights Reserved.1 August 2007