THE THREE THINGS


The Presentation inside:

Slide 0

THE THREE THINGS You Need to Know to Transform Any Sized Organization into an Agile Enterprise


Slide 1

[email protected] 404-312-1471 www.leadingagile.com twitter.com/mcottmeyer facebook.com/leadingagile linkedin.com/in/cottmeyer MIKE COTTMEYER


Slide 2

Brief Agenda Discuss why adopting agile isn’t ‘one size fits all’ Explore the fundamentals of agile transformation How to craft an agile transformation roadmap


Slide 3

Brief Agenda Discuss why adopting agile isn’t ‘one size fits all’ Explore the fundamentals of agile transformation How to craft an agile transformation roadmap


Slide 4

Brief Agenda Discuss why adopting agile isn’t ‘one size fits all’ Explore the fundamentals of agile transformation How to craft an agile transformation roadmap


Slide 5

Brief Agenda Discuss why adopting agile isn’t ‘one size fits all’ Explore the fundamentals of agile transformation How to craft an agile transformation roadmap


Slide 6

ONE SIZE DOES NOT FIT ALL


Slide 7

Predictability Adaptability


Slide 8

Predictability Adaptability Emergence Convergence


Slide 9

Predictability Adaptability Emergence Convergence


Slide 10

Predictability Adaptability Emergence Convergence AE PC


Slide 11

Predictability Adaptability Emergence Convergence AE PE PC AC


Slide 12

Predictability Adaptability Emergence Convergence AE PE PC AC Ad-Hoc Quadrant One Predictive Emergent


Slide 13

Predictability Adaptability Emergence Convergence AE PE PC AC Ad-Hoc Traditional Quadrant Two Predictive Convergent


Slide 14

Predictability Adaptability Emergence Convergence AE PE PC AC Ad-Hoc Traditional Agile Quadrant Three Adaptive Convergent


Slide 15

Predictability Adaptability Emergence Convergence AE PE PC AC Ad-Hoc Traditional Agile Lean Startup Quadrant Four Adaptive Emergent


Slide 16

THE THREE THINGS


Slide 17


Slide 18

Backlog Backlog Backlog Backlog Backlogs


Slide 19

Teams Backlog Backlog Backlog Backlog Backlogs Teams


Slide 20

Teams Backlog Backlog Backlog Backlog Working Tested Software Backlogs Teams Working Tested Software


Slide 21

Teams Backlog Backlog Backlog Backlog Working Tested Software INVEST CCC Small enough for the team to develop in a day or so Everything and everyone necessary to deliver Meets acceptance criteria No known defects No technical debt What Do I Mean? Backlogs Teams Working Tested Software


Slide 22

Teams Backlog Backlog Backlog Backlog Working Tested Software INVEST CCC Small enough for the team to develop in a day or so Everything and everyone necessary to deliver Meets acceptance criteria No known defects No technical debt What Do I Mean? Backlogs Teams Working Tested Software


Slide 23

Teams Backlog Backlog Backlog Backlog Working Tested Software INVEST CCC Small enough for the team to develop in a day or so Everything and everyone necessary to deliver Meets acceptance criteria No known defects No technical debt What Do I Mean? Backlogs Teams Working Tested Software


Slide 24

Teams Backlog Backlog Backlog Backlog Working Tested Software INVEST CCC Small enough for the team to develop in a day or so Everything and everyone necessary to deliver Meets acceptance criteria No known defects No technical debt What Do I Mean? Backlogs Teams Working Tested Software


Slide 25

Teams Backlog Backlog Backlog Backlog Working Tested Software Why Are They Important? Clarity Accountability Measureable Progress People have clarity around what to build People understand how it maps to the big picture Teams can be held accountable for delivery No indeterminate work piling up at the end of the project 90% done, 90% left to do


Slide 26

Teams Backlog Backlog Backlog Backlog Working Tested Software Why Are They Important? Clarity Accountability Measureable Progress People have clarity around what to build People understand how it maps to the big picture Teams can be held accountable for delivery No indeterminate work piling up at the end of the project 90% done, 90% left to do


Slide 27

Teams Backlog Backlog Backlog Backlog Working Tested Software Why Are They Important? Clarity Accountability Measureable Progress People have clarity around what to build People understand how it maps to the big picture Teams can be held accountable for delivery No indeterminate work piling up at the end of the project 90% done, 90% left to do


Slide 28

Teams Backlog Backlog Backlog Backlog Working Tested Software Why Are They Important? Clarity Accountability Measureable Progress People have clarity around what to build People understand how it maps to the big picture Teams can be held accountable for delivery No indeterminate work piling up at the end of the project 90% done, 90% left to do


Slide 29

Teams Backlog Backlog Backlog Backlog Working Tested Software Why Are They Important? Purpose Autonomy Mastery Understanding the backlog gives meaning to work Local decision making gives people a sense of power and control over their work People can demonstrate that they are good at what they do


Slide 30

Teams Backlog Backlog Backlog Backlog Working Tested Software Why Are They Important? Purpose Autonomy Mastery Understanding the backlog gives meaning to work Local decision making gives people a sense of power and control over their work People can demonstrate that they are good at what they do


Slide 31

Teams Backlog Backlog Backlog Backlog Working Tested Software Why Are They Important? Purpose Autonomy Mastery Understanding the backlog gives meaning to work Local decision making gives people a sense of power and control over their work People can demonstrate that they are good at what they do


Slide 32

Teams Backlog Backlog Backlog Backlog Working Tested Software Why Are They Important? Purpose Autonomy Mastery Understanding the backlog gives meaning to work Local decision making gives people a sense of power and control over their work People can demonstrate that they are good at what they do


Slide 33

Teams Backlog Backlog Backlog Backlog Working Tested Software What Do They Look Like at Scale? Governance Structure Metrics & Tools Governance is the way we make economic tradeoffs in the face of constraints They way we form teams and foster collaboration at all levels of the organization What do we measure, how do we baseline performance and show improvement?


Slide 34

Teams Backlog Backlog Backlog Backlog Working Tested Software What Do They Look Like at Scale? Governance Structure Metrics & Tools Governance is the way we make economic tradeoffs in the face of constraints They way we form teams and foster collaboration at all levels of the organization What do we measure, how do we baseline performance and show improvement?


Slide 35

Teams Backlog Backlog Backlog Backlog Working Tested Software What Do They Look Like at Scale? Governance Structure Metrics & Tools Governance is the way we make economic tradeoffs in the face of constraints They way we form teams and foster collaboration at all levels of the organization What do we measure, how do we baseline performance and show improvement?


Slide 36

Teams Backlog Backlog Backlog Backlog Working Tested Software What Do They Look Like at Scale? Governance Structure Metrics & Tools Governance is the way we make economic tradeoffs in the face of constraints They way we form teams and foster collaboration at all levels of the organization What do we measure, how do we baseline performance and show improvement?


Slide 37

STRUCTURE


Slide 38

Team Team Team Team Team Team Team Product & Services Teams


Slide 39

Team Team Team Team Team Team Team Team Team Team Product & Services Teams Program Teams


Slide 40

Team Team Team Team Team Team Team Team Team Team Team Product & Services Teams Program Teams Portfolio Teams


Slide 41

GOVERNANCE


Slide 42

Team Team Team Team Team Team Team Team Team Team Team Product & Services Teams Program Teams Portfolio Teams


Slide 43

Product & Services Teams Scrum Team Team Team Team Team Team Team Team Team Team Team Program Teams Portfolio Teams


Slide 44

Product & Services Teams Program Teams Portfolio Teams Scrum Kanban Team Team Team Team Team Team Team Team Team Team Team


Slide 45

Product & Services Teams Program Teams Portfolio Teams Scrum Kanban Kanban Team Team Team Team Team Team Team Team Team Team Team


Slide 46

METRICS


Slide 47

Product & Services Teams Program Teams Portfolio Teams Scrum Kanban Kanban Team Team Team Team Team Team Team Team Team Team Team


Slide 48

Product & Services Teams Program Teams Portfolio Teams Scrum Kanban Kanban Team Team Team Team Backlog Size Velocity Burndown Escaped Defects Commit % Ratio Acceptance % Ratio Scope Change


Slide 49

Product & Services Teams Program Teams Portfolio Teams Scrum Kanban Kanban Team Cycle Time Features Blocked Rework/Defects Backlog Size Velocity Burndown Escaped Defects Commit % Rate Acceptance % Ratio Scope Change


Slide 50

Product & Services Teams Program Teams Portfolio Teams Scrum Kanban Kanban Backlog Size Velocity Burndown Escaped Defects Commit % Ratio Acceptance % Ratio Scope Change Cycle Time Features Blocked Rework/Defects Takt Time/Cycle Time Time/Cost/Scope/Value RIO/Capitalization


Slide 51

Teams Backlog Backlog Backlog Backlog Working Tested Software What Gets in the Way? Business Dependencies Organizational Dependencies Technical Dependencies Requirements management Process flow Value streams Bottlenecks Too much in process work Matrixed Organizations Non instantly available resources Lack of SME Technical Debt Defects Loose Coupling Low Cohesion


Slide 52

Teams Backlog Backlog Backlog Backlog Working Tested Software What Gets in the Way? Business Dependencies Organizational Dependencies Technical Dependencies Requirements management Process flow Value streams Bottlenecks Too much in process work Matrixed Organizations Non instantly available resources Lack of SME Technical Debt Defects Loose Coupling Low Cohesion


Slide 53

Teams Backlog Backlog Backlog Backlog Working Tested Software What Gets in the Way? Business Dependencies Organizational Dependencies Technical Dependencies Requirements management Process flow Value streams Bottlenecks Too much in process work Matrixed Organizations Non instantly available resources Lack of SME Technical Debt Defects Loose Coupling Low Cohesion


Slide 54

Teams Backlog Backlog Backlog Backlog Working Tested Software What Gets in the Way? Business Dependencies Organizational Dependencies Technical Dependencies Requirements management Process flow Value streams Bottlenecks Too much in process work Matrixed Organizations Non instantly available resources Lack of SME Technical Debt Defects Loose Coupling Low Cohesion


Slide 55

Team


Slide 56

Matrixed Organizations Team


Slide 57

Matrixed Organizations Non-instantly Available Resources Team


Slide 58

Matrixed Organizations Limited Access to Subject Matter Expertise Non-instantly Available Resources Team


Slide 59

Matrixed Organizations Limited Access to Subject Matter Expertise Non-instantly Available Resources Shared Requirements Between Teams Team


Slide 60

Matrixed Organizations Limited Access to Subject Matter Expertise Non-instantly Available Resources Too Much Work In Process Shared Requirements Between Teams Team


Slide 61

Matrixed Organizations Limited Access to Subject Matter Expertise Non-instantly Available Resources Too Much Work In Process Shared Requirements Between Teams Large Products with Diverse Technology Team


Slide 62

Matrixed Organizations Limited Access to Subject Matter Expertise Non-instantly Available Resources Too Much Work In Process Shared Requirements Between Teams Technical Debt & Defects Large Products with Diverse Technology Team


Slide 63

Matrixed Organizations Limited Access to Subject Matter Expertise Non-instantly Available Resources Too Much Work In Process Low Cohesion & Tight Coupling Shared Requirements Between Teams Technical Debt & Defects Large Products with Diverse Technology Team


Slide 64

Teams Backlog Backlog Backlog Backlog Working Tested Software How Do I Need to Change? Known and knowable requirements How to deal with unknowns Estimating Fungible resources Individual utilization Productivity metrics Activity over outcome Defining Work Allocating People Measuring Progress


Slide 65

Teams Backlog Backlog Backlog Backlog Working Tested Software How Do I Need to Change? Known and knowable requirements How to deal with unknowns Estimating Fungible resources Individual utilization Productivity metrics Activity over outcome Defining Work Allocating People Measuring Progress


Slide 66

Teams Backlog Backlog Backlog Backlog Working Tested Software How Do I Need to Change? Known and knowable requirements How to deal with unknowns Estimating Fungible resources Individual utilization Productivity metrics Activity over outcome Defining Work Allocating People Measuring Progress


Slide 67

Teams Backlog Backlog Backlog Backlog Working Tested Software How Do I Need to Change? Known and knowable requirements How to deal with unknowns Estimating Fungible resources Individual utilization Productivity metrics Activity over outcome Defining Work Allocating People Measuring Progress


Slide 68

A THEORY OF TRANSFORMATION


Slide 69

A Theory of Transformation Agile is about forming teams, building backlogs, and regularly producing increments of working tested software


Slide 70

A Theory of Transformation Agile at scale is about defining structure, establishing governance, and creating a metrics and tooling strategy that supports agility


Slide 71

A Theory of Transformation Anything that gets in the way of forming teams, building backlogs, and producing working tested software is an impediment to transformation


Slide 72

TRANSFORMATION IS A JOURNEY


Slide 73

Predictability Adaptability Emergence Convergence AE PE PC AC Ad-Hoc Traditional Agile Lean Startup


Slide 74

Predictability Adaptability Emergence Convergence AE PE PC AC Ad-Hoc Traditional Agile Lean Startup Low Trust


Slide 75

Predictability Adaptability Emergence Convergence AE PE PC AC Ad-Hoc Traditional Agile Lean Startup Low Trust Become Predictable


Slide 76

Predictability Adaptability Emergence Convergence AE PE PC AC Ad-Hoc Traditional Agile Lean Startup Low Trust Become Predictable


Slide 77

Predictability Adaptability Emergence Convergence AE PE PC AC Ad-Hoc Lean/Agile Agile Lean Startup Low Trust Become Predictable


Slide 78

Predictability Adaptability Emergence Convergence AE PE PC AC Ad-Hoc Lean/Agile Agile Lean Startup Low Trust Become Predictable Reduce Batch Size


Slide 79

Predictability Adaptability Emergence Convergence AE PE PC AC Ad-Hoc Lean/Agile Agile Lean Startup Low Trust Become Predictable Reduce Batch Size Fully Decouple


Slide 80

Predictability Adaptability Emergence Convergence AE PE PC AC Ad-Hoc Lean/Agile Agile Lean Startup Teams Low Trust Become Predictable Reduce Batch Size Fully Decouple


Slide 81

Predictability Adaptability Emergence Convergence AE PE PC AC Ad-Hoc Lean/Agile Agile Lean Startup Teams Low Trust Become Predictable Reduce Batch Size Fully Decouple Phase One Phase One Stabilize the System


Slide 82

Predictability Adaptability Emergence Convergence AE PE PC AC Ad-Hoc Lean/Agile Agile Lean Startup Teams Low Trust Become Predictable Reduce Batch Size Fully Decouple Phase One Phase Two Phase Two Reduce Batch Size


Slide 83

Predictability Adaptability Emergence Convergence AE PE PC AC Ad-Hoc Lean/Agile Agile Lean Startup Teams Low Trust Become Predictable Reduce Batch Size Fully Decouple Phase One Phase Three Phase Two Phase Three Break Dependencies


Slide 84

Predictability Adaptability Emergence Convergence AE PE PC AC Ad-Hoc Lean/Agile Agile Lean Startup Teams Low Trust Become Predictable Reduce Batch Size Fully Decouple Phase One Phase Three Phase Four Phase Two Phase Four Increase Local Autonomy


Slide 85

Predictability Adaptability Emergence Convergence AE PE PC AC Ad-Hoc Lean/Agile Agile Lean Startup Teams Low Trust Become Predictable Reduce Batch Size Fully Decouple Phase One Phase Three Phase Four Phase Two Phase Five Phase Five Invest to Learn


Slide 86

[email protected] 404-312-1471 www.leadingagile.com twitter.com/mcottmeyer facebook.com/leadingagile linkedin.com/in/cottmeyer MIKE COTTMEYER


Slide 87

THE THREE THINGS You Need to Know to Transform Any Sized Organization into an Agile Enterprise


×

HTML:





Ссылка: