SolarWinds Orion Core Case Study

Transcription

1 SolarWinds Orion Core Case Study Robert Batusek, agile coach

2 SolarWinds 2

3 Monitoring Software That Technology Professionals Love SIMPLE POWERFUL AFFORDABLE More than marketing speak, these three elements are the foundation of our business model Over 250,000 customers in 170 countries. From SMB to Fortune 500 More than 85% (425) of the Fortune 500 are customers Network and Systems Management Applications Performance Management General Network Monitoring Tool Bandwidth/ Traffic Monitoring SQL Tool Virtual Management/ Optimization #1 in network monitoring market share Over 800 R&D engineers building the future of monitoring 2017 SOLARWINDS WORLDWIDE, LLC. ALL RIGHTS RESERVED. 3

4 Worldwide Leader in Network Management Software 4

5 Core Modules VIM NPM SAM NCM NTA SRM Platform Core Agent Apollo HA Cortex 6 Scrum teams 3 teams + 3 teams + Stakeholders 6

6 Agile Transition - Start Waterfall

7 Introduction Monday, Week 1 Petr (Dev): Hi David, do you already know what I will be doing in the next weeks? David (Dev Lead): Yes. I planned the iteration for you. Here is the task list. Petr: Okay, it seems reasonable. How long is the iteration? David: It s planned for four weeks. Petr: Okay, so I have full four weeks to finish my tasks? David: Of course not. The QA team needs your code a week in advance so that they can properly test it. Petr: That would be a problem. I don t think it s possible to finish the coding in three weeks. David: That s why Steve from the Austin office will join you. I ve already identified some tasks for him. The whole feature s SWAG was 100 hours so you should be fine. Petr: Okay, I ll start then. 8

8 Introduction Wednesday, Week 4, last week of the iteration Petr: David, I don t think we can finish this in this iteration. David: Why not? Petr: QA started testing this week and found 10 bugs. I need at least a couple of days to fix them. David: Ooph. Okay, we will prolong the iteration by two days. The feature is really important because it has been committed for the Q1 release. Petr: I will do my best. David: Please also keep in mind that you only implement a platform part. Modules need some time to implement their plugins later. And by the way, there is an urgent customer issue that needs to be taken care of. Can you look into it today? 9

9 Agile Transition Sprints Definition of Done Automation Teams Roles Tools Backlog Refinement Build pipeline Communities Componentization Waterfall Scrum LeSS Future

10 Multi-team Scrum events I planned the iteration for you

11 Scrum Events - Sprint Review UX Review Tech Review Bug Jury 12

12 Scrum Events Sprint Review 13

13 Scrum Events Sprint Review Experiment: Showed everything in sprint demo Assessment: Very diverse set of stakeholders, annoyed most of the time. 13

14 Scrum Events Sprint Review Experiment: Showed everything in sprint demo Assessment: Very diverse set of stakeholders, Experiment: Selected only annoyed most of the user-centric time. items for sprint demo Assessment: Very few presentable items, looked like the team did nothing valuable 13

15 Scrum Events Sprint Review Experiment: Showed everything in sprint demo Experiment: Internal and public sprint review Assessment: Very diverse set of stakeholders, Experiment: Selected only annoyed most of the user-centric time. items for sprint demo Assessment: Very few presentable items, looked like the team did nothing valuable Assessment: Internal review turned into status reporting. Still too little to show on public review. Using phone conference limited communication. 13

16 Scrum Events Overall Retrospective 14

17 Scrum Events Overall Retrospective Experiment: Management retrospectives 20 people in four groups. Assessment: Scope too broad (included Core and Initiatives), not too many common topics. Died slowly. 14

18 Scrum Events Overall Retrospective Experiment: Management retrospectives 20 people in four groups. Assessment: Scope too broad (included Core and Initiatives), not too many common topics. Died slowly. Experiment: Topics coming from team retrospectives. Voting. Assessment: Did not identify systemic issues. 14

19 Scrum Events Overall Retrospective Experiment: Management retrospectives 20 people in four groups. Experiment: Used mind mapping tool to record ideas during retrospectives Assessment: Scope too broad (included Core and Initiatives), not too many common topics. Died slowly. Experiment: Topics coming from team retrospectives. Voting. Assessment: Visualization helps drive the discussion. Assessment: Did not identify systemic issues. 14

20 Scrum Events Overall Retrospective Experiment: Management retrospectives 20 people in four groups. Assessment: Scope too broad (included Core and Initiatives), not too many common topics. Died slowly. Experiment: Topics coming from team retrospectives. Voting. Assessment: Did not identify systemic issues. Experiment: Used mind mapping tool to record ideas during retrospectives Experiment: Overall retrospective with SMs and managers only. Assessment: Visualization helps drive the discussion. Assessment: Better focus on systemic issues. Still felt like an artificial meeting. 14

21 Scrum Events - Sprint planning 15

22 Handling Maintenance Load There is an urgent customer issue that needs to be taken care of

23 Handling Maintenance Load InFlow

24 Handling Maintenance Load Book cover by Goodreads 19

25 Handling Maintenance Load Book cover by Goodreads 19

26 Handling Maintenance Load Book cover by Goodreads 19

27 Handling Maintenance Load Book cover by Goodreads 19

28 Handling Maintenance Load Book cover by Goodreads 19

29 Handling Maintenance Load Book cover by Goodreads 19

30 Handling Maintenance Load Book cover by Goodreads 19

31 Handling Maintenance Load 20

32 Handling Maintenance Load Experiment: Fill template before hand over. 20

33 Handling Maintenance Load Experiment: Fill template before hand over. Experiment: Supportability team 20

34 Handling Maintenance Load Experiment: Avengers Experiment: Fill template before hand over. Experiment: Supportability team 20

35 Handling Maintenance Load Experiment: Avengers Experiment: Fill template before hand over. Experiment: Supportability team Experiment: Initiatives involved in maintenance. 20

36 Handling Maintenance Load Experiment: Avengers Experiment: Fill template before hand over. Experiment: Supportability team Experiment: Handover some areas to other teams. Experiment: Initiatives involved in maintenance. 20

37 Handling Maintenance Load Experiment: Fill template before hand over. Experiment: Avengers Experiment: Supportability team Experiment: Pushback on support Experiment: Handover some areas to other teams. Experiment: Initiatives involved in maintenance. 20

38 Handling Maintenance Load Experiment: Fill template before hand over. Experiment: Avengers Experiment: Supportability team Experiment: Regular hotfixes each month Experiment: Pushback on support Experiment: Handover some areas to other teams. Experiment: Initiatives involved in maintenance. 20

39 Handling Maintenance Load Experiment: Fill template before hand over. Experiment: Avengers Experiment: Supportability team Experiment: Regular hotfixes each month Experiment: Pushback on support Experiment: Handover Experiment: Supportability some areas to other teams. team v2 Experiment: Initiatives involved in maintenance. 20

40 Handling Maintenance Load Experiment: Fill template before hand over. Experiment: Avengers Experiment: Regular hotfixes each month Experiment: Pushback on support Experiment: Training Application Experiment: Engineers Initiatives involved in maintenance. Experiment: Supportability team Experiment: Handover Experiment: Supportability some areas to other teams. team v2 20

41 7/15 8/15 9/15 10/15 11/15 12/15 1/16 2/16 3/16 4/16 5/16 6/16 7/16 8/16 9/16 10/16 11/16 12/16 1/17 2/17 3/17 4/17 5/17 Queue size Handling Maintenance Load Experiment: Avengers Experiment: Regular Open CIs hotfixes each month Experiment: Pushback on 200 Experiment: Fill template support Experiment: Training 150 before hand over. Experiment: 100 Application Engineers Initiatives Experiment: Supportability 50 involved in maintenance. 0 team Experiment: Handover Experiment: Supportability some Date areas to other teams. team v2 20

42 Handling Maintenance Load 21

43 Handling Maintenance Load Experiment: Stop rotating maintenance Assessment: Teams came up with their own proposal and defended it. Metrics indicate that the situation is improving. 21

44 7/15 9/15 11/15 1/16 3/16 5/16 7/16 9/16 11/16 1/17 3/17 5/17 7/17 9/17 Queue size Handling Maintenance Load Experiment: Stop rotating maintenance Assessment: Teams came up with their own proposal and defended it. Metrics indicate that the situation is improving Date 21

45 Estimates The whole feature s SWAG was 100 hours

46 Estimates Separate Dev and QA estimates Estimate in hours +- 20% SWAG in days +- 50% 23

47 Estimates 24

48 Estimates Experiment: Calibrated team estimates with known backlog items. Assessment: Troubles with finding representative items. 24

49 Estimates Experiment: Calibrated team estimates with known backlog items. Experiment: Did not estimate Assessment: Troubles with bugs. finding representative items. Assessment: Bugs represent more than 50% of the backlog. Velocity distorted. 24

50 Estimates Experiment: Calibrated team estimates with known backlog items. Experiment: Did not estimate Assessment: Troubles with bugs. finding representative items. Assessment: Bugs represent more than 50% of the backlog. Velocity distorted. Experiment: Used reduced scale for bugs 0.5,1,2,3,<needs grooming> Assessment: Estimates not calibrated. 24

51 NoEstimates Book cover by Goodreads 25

52 Occurrence of items NoEstimates Health check small items 800 Histogram Story Points Avg:

53 # of items Story Points NoEstimates Health check all charts look the same Comparing # of items and story points # SP 27

54 # of items NoEstimates Calculate velocity in backlog items Backlog items finished per sprint Sprint # stories Optimistic average Pessimistic average 28

55 # of items NoEstimates Calculate in-flow rate InFlow rate Sprint # stories Pessimistic average Optimistic average 29

56 NoEstimates Forecast based on data 140 Burndown chart and 3 predictions FC R1 R2 R3 Remaining Optimistic Realistic Pessimistic 30

57 Estimates estimating epics Columns with T-shirt labels Sample epics from previous releases for comparison List of potential epics available 31

58 Estimates estimating epics Columns are assigned sizes based on sample epics of known size At the end of the session, all epics are distributed to columns, usually forming a bell curve 32

59 Contact

60 The SolarWinds, SolarWinds & Design, Orion, and THWACK trademarks are the exclusive property of SolarWinds Worldwide, LLC or its affiliates, are registered with the U.S. Patent and Trademark Office, and may be registered or pending registration in other countries. All other SolarWinds trademarks, service marks, and logos may be common law marks or are registered or pending registration. All other trademarks mentioned herein are used for identification purposes only and are trademarks of (and may be registered trademarks) of their respective companies.