Transition from Scrum to Flow

Transcription

1 Transition from Scrum to Flow Implementing change at a large multi-national software company

2 Transition from Scrum to Flow Phillip Cave / Kristin Poole 2

3 Introducing IEB Transition from Scrum to Flow Phillip Cave / Kristin Poole 3

4 1. Define Value 2. Create Visibility 5. Create Flow TIME 4. Establish Pull 3. Manage WIP Transition from Scrum to Flow Phillip Cave / Kristin Poole 4

5 1. Define Value 2. Create Visibility 5. Create Flow TIME 4. Establish Pull 3. Manage WIP Transition from Scrum to Flow Phillip Cave / Kristin Poole 5

6 Business Capability Value Stream Activity towards success Who works these activities? Upon what do we focus? Transition from Scrum to Flow Phillip Cave / Kristin Poole 6

7 Copyright Institut Lean France 2011 Transition from Scrum to Flow Phillip Cave / Kristin Poole 7

8 1. Define Value 2. Create Visibility 5. Create Flow TIME 4. Establish Pull 3. Manage WIP Transition from Scrum to Flow Phillip Cave / Kristin Poole 8

9 Transition from Scrum to Flow Phillip Cave / Kristin Poole 9

10 Transition from Scrum to Flow Phillip Cave / Kristin Poole 10

11 Transition from Scrum to Flow Phillip Cave / Kristin Poole 11

12 CCPM Critical Chain Project Management (CCPM) is a Project Management process to help: Identify bottlenecks at planning and during execution Drive focus towards critical few to manage the uncertainties Show IMPACT to due date Transition from Scrum to Flow Phillip Cave / Kristin Poole 12

13 CCPM Sample Transition from Scrum to Flow Phillip Cave / Kristin Poole 13

14 Manage WIP Transition from Scrum to Flow Phillip Cave / Kristin Poole 14

15 1. Define Value 2. Create Visibility 5. Create Flow TIME 4. Establish Pull 3. Manage WIP Transition from Scrum to Flow Phillip Cave / Kristin Poole 15

16 Work Breakdown Feature (Business Capability) As a Site Owner, I need the ability to capture content effectiveness as it correlates to a specific url. Stories As a Content Manager I can add a "feedback control" to my site which includes three parts: 1) Question; 2) Instruction Text; 3) Free-form field to receive feedback from consumer. As an Engineering Team, we need to deploy and test the sprint features in the integration environments prior to release Tasks Create Client Object Model (COM) Class Capture Data/ Site and List Schema Create build package Transition from Scrum to Flow Phillip Cave / Kristin Poole 16

17 Process Thinking Activity-driven vs. Value-driven BIG Batch Activity C small Incremental VALUE C Test Develop Design Infrastructure Test Develop Design Infrastructure INCREMENTAL BUSINESS VALUE Transition from Scrum to Flow Phillip Cave / Kristin Poole 17

18 Feature Thinking Batch-driven vs. Scenario/Feature/Deliverable-driven BIG Batch Technology C small Incremental VALUE C Experiences Services Info Arch Infrastructure Experiences Services Info Arch Infrastructure INCREMENTAL BUSINESS VALUE Transition from Scrum to Flow Phillip Cave / Kristin Poole 18

19 Incremental Business Value Focus on Business FEATURE Slices... NOT technology layers NOT THIS C 1 DO C THIS Experiences Services Info Arch Infrastructure Experiences Services Info Arch Infrastructure INCREMENTAL BUSINESS VALUE Transition from Scrum to Flow Phillip Cave / Kristin Poole 19

20 Lean Thinking Incremental VALUE C Test Develop Design High level Infrastructure INCREMENTAL BUSINESS VALUE Feed partner team product lifecycle Transition from Scrum to Flow Phillip Cave / Kristin Poole 20

21 Feature/Story Flow A new story prioritization would be done at the beginning of each release and reprioritization could occur before a new story is added to Envision. Only items moved from Team Queue (aka. Backlog) will be worked on. Kanban Board visualizes the iterative nature of work and status of each story. Can be Envisioning for one Story and Validating for a different Story. Iteration Path Examples: Retail Stores/Release 1/Team Queue Transition from Scrum to Flow Phillip Cave / Kristin Poole 21

22 Transition from Scrum to Flow Phillip Cave / Kristin Poole 22

23 Pull Transition from Scrum to Flow Phillip Cave / Kristin Poole 23

24 1. Define Value 2. Create Visibility 5. Create Flow TIME 4. Establish Pull 3. Manage WIP Transition from Scrum to Flow Phillip Cave / Kristin Poole 24

25 Feature (Business Capability) As a Site Owner, I need the ability to capture content effectiveness as it correlates to a specific url. Business Stories Delivery Tasks As a Content Manager I Create Client Queue can add a "feedback Queue Object Model control" to my site which (COM) Class Features and includes three parts: Estimated 1) Stories Stories Question; 2) Instruction (value size, Prioritized Text; 3) Free-form field complexity, Capture Data/ to receive feedback from sequence) Sequenced(priority, Site and List dependencies, consumer. Tasks (< 24 hours) Schema effort) Monitor work flow of story completion As an Engineering Team, Can be used for we need to deploy and Release Planning test the sprint features Used in to monitor flow Create build the integration of work package environments prior to release Transition from Scrum to Flow Phillip Cave / Kristin Poole 25

26 Kanban Pull/Flow Project : <Project X> Version 1.0 MMF Backlog Envision Prototype Build Validate Ship Ready Completed Customer Management Product Management Create Order View Order Define Requirements and Test and iteratively If applicable create Functional Specs for the fix bugs prototypes. Iteratively Build solution selected stories Minor CRs absorb modify Requirements Create Test plans Major CRs move to / Spec UML / FlowCharts Product Backlog and prioritize Transition from Scrum to Flow Phillip Cave / Kristin Poole 26

27 Flow Transition from Scrum to Flow Phillip Cave / Kristin Poole 27

28 1. Define Value 2. Create Visibility 5. Create Flow TIME 4. Establish Pull 3. Manage WIP Transition from Scrum to Flow Phillip Cave / Kristin Poole 28

29 Business Planning Solution Architecture Time Box (2-3 weeks) Iteration (Sprint) Release Planning Execution Planning Daily Feedback Review Product Backlog Feature Feature Feature Story Story Release Backlog Feature Story Story Feature Story Story Iteration Backlog Story Story Story Story Story Transition from Scrum to Flow Phillip Cave / Kristin Poole 29

30 Business Planning Solution Architecture Release Planning Feature Planning Feature Execution WIP & Impediment Management Feature Review / Release Business Queue Feature Feature Feature Story Story Delivery Queue Feature Story Story Feature Story Story Release Queue Feature Feature Feature Feature Feature Transition from Scrum to Flow Phillip Cave / Kristin Poole 30

31 Feature Flow Measures Activity States Feature Backlog Envision (Arch/Lean Specs) Prototype (Tangible POC) Build (Dev/Test) Validate (SIT/UAT) Ship Ready Completed Feature End-to-End Cycle Time Feature Demonstrable Value Cycle Time Feature Value Delivery Cycle Time Feature Activity State Capacities Transition from Scrum to Flow Phillip Cave / Kristin Poole 31

32 Velocity / Flow / Cycle Time Deliverables in progress Cycle 1 Cycle 2 Cycle 3 Cycle 4 Cycle 5 Velocity Avg Velocity Avg. Flow # Velocity can be used to measure how close to the estimates the actuals are, and what to project going forward Historical data on flow can be used to estimate future projects simply by knowing the number of deliverables. Transition from Scrum to Flow Phillip Cave / Kristin Poole 32

33 TOC Applied Business Queue Dev/Test Delivery Cycle Queue System Infrastructure Transition from Scrum to Flow Phillip Cave / Kristin Poole 33

34 Time Transition from Scrum to Flow Phillip Cave / Kristin Poole 34

35 1. Define Value 2. Create Visibility 5. Create Flow TIME 4. Establish Pull 3. Manage WIP Transition from Scrum to Flow Phillip Cave / Kristin Poole 35

36 Target end date (90% probability) Alert Normal execution pattern Alert Alert need buffer recovery plan % Buffer used = Watch Cruise Cruise Uncertainties are fewer Advance due date? % Chain complete = NOTE: See chapter 17 of Mike Cohn s book Agile Estimating and Planning for an example of CCPM Earliest end date (50% probability) Transition from Scrum to Flow Phillip Cave / Kristin Poole 36

37 Relative Sizing Estimates Small Size Big Deliverables Transition from Scrum to Flow Phillip Cave / Kristin Poole 37

38 Lead Time Lead Time Delivery Cycle Time Due Date Given Average Cycle Time, Lead time is calculated based on Type of work ( Feature Size ) Average cycle time for that type Transition from Scrum to Flow Phillip Cave / Kristin Poole 38

39 Organization Transformation Transition from Scrum to Flow Phillip Cave / Kristin Poole 39

40 Organization Thinking Toolbox Scrum Iterations (timebox) Project Tracking Sprint Lean ScrumBan Practices Toolbox Visibility WIP Control Flow Work Product Breakdown Daily Meeting Estimation CCPM Kanban Feature Flow Project Tracking Pull Transition from Scrum to Flow Phillip Cave / Kristin Poole 40

41 Transition from Scrum to Flow Phillip Cave / Kristin Poole 41

42 Transition from Scrum to Flow Phillip Cave / Kristin Poole 42

43 Transition from Scrum to Flow Phillip Cave / Kristin Poole 43

44 Copyright Institut Lean France 2011