Scrum for Managers, Zurich March 2010

Transcription

1 Scrum for Managers Microsoft Corporation / TechTalk Zurich Switzerland March 2010 About Mitch Lacey Mitch Lacey 13+ years of program and project management experience Microsoft Program Manager Released large backend core services for Windows Live & MSN Worked as Agile Coach, onboarding teams to Scrum and Agile principles and practices Project Management Professional (PMP) Certified Scrum Trainer (CST) 2 Copyright Mitch Lacey. mitch@mitchlacey.com for re use permission. 1

2 Question What is the role of the manager? In Scrum? 3 4 Copyright Mitch Lacey. mitch@mitchlacey.com for re use permission. 2

3 What is Agile? A set of Values & Principles (The Manifesto) A set of Practices (The Methods) Most Importantly, agile is a Mindset and Different way of working to realize business value sooner 5 What Agile is Not It is not a silver bullet Nor is it a single method Also, it is not a set of tools 6 Copyright Mitch Lacey. mitch@mitchlacey.com for re use permission. 3

4 Scrum Principles Focus Respect Commitment Openness Courage 7 The Agile Manifesto 2001 We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. Authors: Kent Beck, Mike Beedle, Arie van Bennekum, Alistair Cockburn, Ward Cunningham, Martin Fowler, James Grenning, Jim Highsmith, Andrew Hunt, Ron Jeffries, Jon Kern, Brian Marick, Robert C. Martin, Steve Mellor, Ken Schwaber, Jeff Sutherland, Dave Thomas 8 Copyright Mitch Lacey. mitch@mitchlacey.com for re use permission. 4

5 Agile Practices the Agile Umbrella Scrum Crystal Clear extreme Programming DSDM Feature Driven Development 9 10 Copyright Mitch Lacey. mitch@mitchlacey.com for re use permission. 5

6 Why Choose Agile? Far from Agreement Anarchy Requirements Complex Close to Agreement Simple Close to Certainty Technology Far from Certainty Source: Strategic Management and Organizational Dynamics by Ralph Stacey. 11 Why Agile? I ve got work to do, I don t have time for this. Raise your hand if you have ever Missed a release date Missed your customer s expectations Gone over budget Had requirements change mid project Lose people in the middle of a project 12 Copyright Mitch Lacey. mitch@mitchlacey.com for re use permission. 6

7 Einstein on Insanity Doing the same thing over and over again and expecting different results 13 Defined (Traditional) Approach, AKA Waterfall 14 Copyright Mitch Lacey. for re use permission. 7

8 Hurdles with Defined Approaches Stakeholders Not Sure What They Want As Product Develops, Minds / Business Goals Change Details Often Revealed During Development Internal & ExternalForces Leadto Changes or Enhancements 15 Empirical Approach 16 Copyright Mitch Lacey. mitch@mitchlacey.com for re use permission. 8

9 Daily, Weekly, Monthly Checkpoints Requirements are Gathered Over Time The Project can Adapt To Meet Business Need Course Corrections Made as Product Develops 17 Agile versus Waterfall 18 Copyright Mitch Lacey. for re use permission. 9

10 Agile in Practice Sprint 3 Sprint 2 Sprint 1 RTM 1.0 Release able Pro oduction grade ness Us efulness Time Functional capacity Copyright Mitch Lacey. mitch@mitchlacey.com for re use permission. 10

11 The Scrum Framework 21 What is Scrum? An agile, lightweight framework for Project Management Wraps existing engineering practices Is used to manage and control software and product development using iterative, incremental practices Is driven by daily and monthly feedback loops Is ideally suited for projects with rapidly changing or highly emergent requirements. And most of all, Scrum is FUN! 22 Copyright Mitch Lacey. for re use permission. 11

12 Scrum Focus Focus on customer value Deliver small chunks of value and in short cycles Be predictable by gathering gdata and adjusting, rather than betting on the perfect plan Empower people and teams to be self managing 23 Managing Risk Risk of not pleasing the customer Mitigated through frequent delivery and feedback Risk of poor predictability (estimation & planning) Mitigated through constant prioritization and estimation Risk of not resolving issues promptly Mitigated by daily progress meetings Risk of not being able to ship Mitigated by monthly releases Risk of over commitment and interruption Mitigated by locking and loading for the Sprint duration 24 Copyright Mitch Lacey. for re use permission. 12

13 Scrum Promotes Transparency and Exposes Impediments Bad practices exposed as impediments If your project is on track The reliability of your work estimates A better way to do things 25 Which do you Prefer? 26 Copyright Mitch Lacey. mitch@mitchlacey.com for re use permission. 13

14 The Scrum Team Product Owner ScrumMaster Core Team 27 The ScrumMaster Specially formulated to provide outstanding Protection Guidance Leadership Impediment Removal Will ensure a long lasting, high performing team 28 Copyright Mitch Lacey. mitch@mitchlacey.com for re use permission. 14

15 The Product Owner Providing the Fuel & Direction 29 The Scrum Team 30 Copyright Mitch Lacey. for re use permission. 15

16 Scrum for Managers, Zurich March 2010 Progress in Scrum Workitem Hours Pending In Progress Complete Remaining Trend Calendar Days 31 Sprint Backlog Data Analysis Calendar Day Date 16 Apr Apr Apr Apr Apr Apr Apr 07 Total Hours Remaining Hours Worked Today Total Hours Worked To Date Total Worked & Remaining Hours Average Hours Worked Per Day Est Completion Date (Burndown) 23 Apr Apr Apr Apr Apr Apr Apr 07 Est Completion Date (Task Completion) 29 Apr Apr Apr Apr Apr Apr Apr 07 Task Hours Pending Task Hours In Progress Task Hours Complete Count of Workitems Pending Count of Workitems In Progress Count of Workitems Complete Copyright Mitch Lacey. mitch@mitchlacey.com for re use permission. 16

17 Transparency in Reporting Copyright Mitch Lacey. for re use permission. 17

18 How does Agile Apply to Managers? Understanding estimation & multitasking Know your role Trust your team Let people grow Support and encourage failure, but only if it is early Accept the transition cost Commitment 35 Estimation Estimates are not commitments just like Availability not being a skillset. 36 Copyright Mitch Lacey. mitch@mitchlacey.com for re use permission. 18

19 What Impacts Estimates? Multitasking Lateness is passed down Lack of a common understanding And more 37 Clark and Wheelwright (1993) found: determined that when working on more than two tasks, a person s time spent on value adding work drops rapidly. 38 Copyright Mitch Lacey. mitch@mitchlacey.com for re use permission. 19

20 Multitasking A B C A B C A B C 20 Multitasking causes delays Instead of multitasking, use small units of work You want work to flow as fast as possible More efficient transfers to next person Deferring Work (Student Syndrome) The estimate is based on this: Task Local Safety But we behave like this Local Safety Task Task 40 Copyright Mitch Lacey. mitch@mitchlacey.com for re use permission. 20

21 Lateness is Passed Down the Schedule TASK A TASK B TASK D TASK C To start early, all of these must occur Task A, B and C must finish early Tester for Task D must be available early To start late, any of these can occur Task A, B or C finish late Tester is not available 41 Validate your Build Types Build like this Not like this 42 Copyright Mitch Lacey. mitch@mitchlacey.com for re use permission. 21

22 Reward for Failiing Early Success is subjective People are typically risk averse People typically y seek out work that suits their skill sets Causes people to stay in their comfort zone Limits growth opportunity 44 Reward for Failing Early Taking on change is to take on risk of the unknown Incentive structures are not setup to reward for taking on the unknown Compensation for taking on additional risk is not proportionate to the risk itself 45 Copyright Mitch Lacey. mitch@mitchlacey.com for re use permission. 22

23 Reward for Failing Early Reward for tries & success, even if they end in failure Think about research how often are breakthroughs encountered? Reward for going outside the comfort zone Learn from failures to grow 46 Provide Protection Protection (allowing people to ) Break old habits Question the status quo Seek out new ways of working Learn to self sustain 47 Copyright Mitch Lacey. mitch@mitchlacey.com for re use permission. 23

24 Accept the Transition Cost Any change introduces instability With change, performance declines before it returns to baseline Maybe it returns at a lower level Maybe it returns at a higher level (which we always assume) Decrease in productivity Baseline achieved Long term improvement 48 Promote Transparency Highlight failure and success Publish status daily Hold retrospectives during projects,, not only at project end (note, these are not post mortems ) Use burndowns Show working software on a regular basis 49 Copyright Mitch Lacey. mitch@mitchlacey.com for re use permission. 24

25 50 Getting Started Get a senior Sponsor in the company Get a champion to drive the effort Agree on who will play the roles Create a Transition Product Backlog Set a date to start and manage to that date Build a Sprint Backlog and start working Use Burndowns Hold Company demos on how the transition is progressing Inspect and Adapt 51 Copyright Mitch Lacey. mitch@mitchlacey.com for re use permission. 25

26 What Causes Failure? Making changes out of the gate Thinking that this can t work in our company Not having honest retrospectives Falling into old habits Lacking authority and being empowered Business culture does not support Agile Principles and Values 52 Be Warned Most projects deliver every 6 18 months. Agile, and Scrum, reduces this through inspect and adapt Things will be stressful Fight the urge to be lazy Stay disciplined 53 Copyright Mitch Lacey. mitch@mitchlacey.com for re use permission. 26

27 Scrum Resources Websites: My Website: Mountain Goat Software Scrum Alliance Agile Alliance Books: Agile Project Management with Scrum, 2004 The Enterprise and Scrum, 2007 Ken Schwaber, Microsoft Press ScrumDevelopment Yahoo Group 54 Copyright Mitch Lacey. for re use permission. 27