'

THE THREE THINGS

Понравилась презентация – покажи это...





Слайд 0

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


Слайд 1

mike@leadingagile.com 404-312-1471 www.leadingagile.com twitter.com/mcottmeyer facebook.com/leadingagile linkedin.com/in/cottmeyer MIKE COTTMEYER


Слайд 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


Слайд 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


Слайд 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


Слайд 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


Слайд 6

ONE SIZE DOES NOT FIT ALL


Слайд 7

Predictability Adaptability


Слайд 8

Predictability Adaptability Emergence Convergence


Слайд 9

Predictability Adaptability Emergence Convergence


Слайд 10

Predictability Adaptability Emergence Convergence AE PC


Слайд 11

Predictability Adaptability Emergence Convergence AE PE PC AC


Слайд 12

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


Слайд 13

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


Слайд 14

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


Слайд 15

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


Слайд 16

THE THREE THINGS


Слайд 17


Слайд 18

Backlog Backlog Backlog Backlog Backlogs


Слайд 19

Teams Backlog Backlog Backlog Backlog Backlogs Teams


Слайд 20

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


Слайд 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


Слайд 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


Слайд 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


Слайд 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


Слайд 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


Слайд 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


Слайд 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


Слайд 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


Слайд 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


Слайд 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


Слайд 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


Слайд 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


Слайд 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?


Слайд 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?


Слайд 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?


Слайд 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?


Слайд 37

STRUCTURE


Слайд 38

Team Team Team Team Team Team Team Product & Services Teams


Слайд 39

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


Слайд 40

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


Слайд 41

GOVERNANCE


Слайд 42

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


Слайд 43

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


Слайд 44

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


Слайд 45

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


Слайд 46

METRICS


Слайд 47

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


Слайд 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


Слайд 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


Слайд 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


Слайд 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


Слайд 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


Слайд 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


Слайд 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


Слайд 55

Team


Слайд 56

Matrixed Organizations Team


Слайд 57

Matrixed Organizations Non-instantly Available Resources Team


Слайд 58

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


Слайд 59

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


Слайд 60

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


Слайд 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


Слайд 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


Слайд 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


Слайд 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


Слайд 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


Слайд 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


Слайд 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


Слайд 68

A THEORY OF TRANSFORMATION


Слайд 69

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


Слайд 70

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


Слайд 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


Слайд 72

TRANSFORMATION IS A JOURNEY


Слайд 73

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


Слайд 74

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


Слайд 75

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


Слайд 76

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


Слайд 77

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


Слайд 78

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


Слайд 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


Слайд 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


Слайд 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


Слайд 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


Слайд 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


Слайд 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


Слайд 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


Слайд 86

mike@leadingagile.com 404-312-1471 www.leadingagile.com twitter.com/mcottmeyer facebook.com/leadingagile linkedin.com/in/cottmeyer MIKE COTTMEYER


Слайд 87

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


×

HTML:





Ссылка: