Using ToC And JIT Practice To Coach Agile Teams

Using ToC and JIT Practice to Coach Agile Teams Naresh Jain naresh@agilefaqs.com Licensed under Creative Commons by Naresh Jain 1

Example Context • Large Enterprise clients [450 ppl + 30 teams] • Huge communication and delivery issues • Help teams adopt Agile thinking Licensed under Creative Commons by Naresh Jain 2

Consider this... Customer Signoff Bug reported 0 71 Time in days Licensed under Creative Commons by Naresh Jain 3

After Value Stream Mapping Licensed under Creative Commons by Naresh Jain 4

After Value Stream Mapping Time in days Licensed under Creative Commons by Naresh Jain 4

After Value Stream Mapping Bug reported 0 Time in days Licensed under Creative Commons by Naresh Jain 4

After Value Stream Mapping Reproduce Bug Bug reported 0 8 8 Time in days Licensed under Creative Commons by Naresh Jain 4

After Value Stream Mapping Write failing test Reproduce Bug Bug reported 0 8 10 8 2 Time in days Licensed under Creative Commons by Naresh Jain 4

After Value Stream Mapping Fix Bug Write failing test Reproduce Bug Bug reported 0 8 10 30 8 2 20 Time in days Licensed under Creative Commons by Naresh Jain 4

After Value Stream Mapping Regression Testing Fix Bug Write failing test Reproduce Bug Bug reported 0 8 10 30 38 8 2 20 8 Time in days Licensed under Creative Commons by Naresh Jain 4

After Value Stream Mapping Making a release Regression Testing Fix Bug Write failing test Reproduce Bug Bug reported 0 8 10 30 38 69 8 2 20 8 31 Time in days Licensed under Creative Commons by Naresh Jain 4

After Value Stream Mapping Customer Signoff Making a release Regression Testing Fix Bug Write failing test Reproduce Bug Bug reported 0 8 10 30 38 69 71 8 2 20 8 31 5 Time in days Licensed under Creative Commons by Naresh Jain 4

Identify Constraints/ bottleneck Subordinate everything else and Elevate the Set Goals Constraints/ bottleneck Licensed under Creative Commons by Naresh Jain 5

Agenda • Some background about ToC and JIT • Technique • Open Discussion with examples from audience Licensed under Creative Commons by Naresh Jain 6

Theory of Constraint is based on the premise that... “Every real system, such as a business, must have within it at least one constraint. If this were not the case then the system could produce unlimited amounts of whatever it was striving for, proﬁt in the case of a business.……………….” Dr Eli Goldratt Licensed under Creative Commons by Naresh Jain 7

“Theory of Constraints” Licensed under Creative Commons by Naresh Jain 8

“Theory of Constraints” Global optimization does not emerge from local optima Licensed under Creative Commons by Naresh Jain 8

“Theory of Constraints” Global optimization does not emerge from local optima Managing by cost (optimizing local performance) is usually at odds with managing by throughput (exploiting constraints) Licensed under Creative Commons by Naresh Jain 8

Signiﬁcance of bottlenecks • Maximum speed of the process is the speed of the slowest operation • Any improvements will be wasted unless the bottleneck is relieved • Bottlenecks must be identiﬁed and improved if the process is to be improved Licensed under Creative Commons by Naresh Jain 9

Assumes current constraints cannot be changed in the short-run Licensed under Creative Commons by Naresh Jain 10

Assumes current constraints cannot be changed in the short-run What should be produced now, with current resources, to maximize proﬁts? Licensed under Creative Commons by Naresh Jain 10

How to apply ToC? Licensed under Creative Commons by Naresh Jain 11

How to apply ToC? • Step 1: Identify the system's constraint(s). Licensed under Creative Commons by Naresh Jain 11

How to apply ToC? • Step 1: Identify the system's constraint(s). • Step 2: Decide how to exploit the system's constraint(s). Licensed under Creative Commons by Naresh Jain 11

How to apply ToC? • Step 1: Identify the system's constraint(s). • Step 2: Decide how to exploit the system's constraint(s). • Step 3: Subordinate everything else to the decisions of Step 2. Licensed under Creative Commons by Naresh Jain 11

How to apply ToC? • Step 1: Identify the system's constraint(s). • Step 2: Decide how to exploit the system's constraint(s). • Step 3: Subordinate everything else to the decisions of Step 2. • Step 4: Elevate the system's constraint(s). Licensed under Creative Commons by Naresh Jain 11

How to apply ToC? • Step 1: Identify the system's constraint(s). • Step 2: Decide how to exploit the system's constraint(s). • Step 3: Subordinate everything else to the decisions of Step 2. • Step 4: Elevate the system's constraint(s). • Step 5: Back to Step 1, identify next constraint. Licensed under Creative Commons by Naresh Jain 11

Step 1: Identify the system’s constraint(s). Licensed under Creative Commons by Naresh Jain 12

Step 1: Identify the system’s constraint(s). • Goal? Licensed under Creative Commons by Naresh Jain 12

Step 1: Identify the system’s constraint(s). • Goal? • Throughput? Licensed under Creative Commons by Naresh Jain 12

Step 1: Identify the system’s constraint(s). • Goal? • Throughput? • Inventory? Licensed under Creative Commons by Naresh Jain 12

Step 1: Identify the system’s constraint(s). • Goal? • Throughput? • Inventory? • Operating Expense? Licensed under Creative Commons by Naresh Jain 12

Step 2: Decide how to exploit the system’s constraint(s). Licensed under Creative Commons by Naresh Jain 13

Step 3: Subordinate everything else to the decisions of Step 2 Licensed under Creative Commons by Naresh Jain 14

Step 4: Elevate the system’s constraint(s). Licensed under Creative Commons by Naresh Jain 15

Step 5: Back to Step 1, identify next constraint. What might happen if the constraint is elevated? Licensed under Creative Commons by Naresh Jain 16

ToC : 3 things can increase proﬁtability of a plant • Decrease Inventory • Decrease Operating Expense • Increase Throughput Licensed under Creative Commons by Naresh Jain 17

How does ToC apply to Software projects? Licensed under Creative Commons by Naresh Jain 18

How does ToC apply to Software projects? • Inventory Licensed under Creative Commons by Naresh Jain 18

How does ToC apply to Software projects? • Inventory • Features requested but not speciﬁed • Features speciﬁed and documented but not built • Code that's written but not tested • Code that's tested but not deployed to users • Code that's deployed but not used Licensed under Creative Commons by Naresh Jain 18

How does ToC apply to Software projects?... Licensed under Creative Commons by Naresh Jain 19

How does ToC apply to Software projects?... • Operating expenses Licensed under Creative Commons by Naresh Jain 19

How does ToC apply to Software projects?... • Operating expenses • Idle team members - Phased approach • Commercial Tools • Cost of change curve - rework • Constant thrashing of ideas • Technical Debt Licensed under Creative Commons by Naresh Jain 19

How does ToC apply to Software projects?... • Throughput • Large batch Size - Queuing Theory Licensed under Creative Commons by Naresh Jain 20

Queuing Theory Utilization (%) Source: Beyond Agile Software Development Becoming Lean, Mary Poppendieck, Poppendieck.llc Licensed under Creative Commons by Naresh Jain 21

How does ToC apply to Software projects?... Licensed under Creative Commons by Naresh Jain 22

How does ToC apply to Software projects?... • Throughput Licensed under Creative Commons by Naresh Jain 22

How does ToC apply to Software projects?... • Throughput • Large batch Size - Queuing Theory • Heavyweight methodology • Poor choice of tools • Real resource shortage Licensed under Creative Commons by Naresh Jain 22

Using Lean principles to Identify Waste Licensed under Creative Commons by Naresh Jain 23

Using Lean principles to Identify Waste • Overproduction = Extra Features Licensed under Creative Commons by Naresh Jain 23

Using Lean principles to Identify Waste • Overproduction = Extra Features • Inventory = Requirements Licensed under Creative Commons by Naresh Jain 23

Using Lean principles to Identify Waste • Overproduction = Extra Features • Inventory = Requirements • Extra Processing Steps = Extra Steps Licensed under Creative Commons by Naresh Jain 23

Using Lean principles to Identify Waste • Overproduction = Extra Features • Inventory = Requirements • Extra Processing Steps = Extra Steps • Motion = Finding Information Licensed under Creative Commons by Naresh Jain 23

Using Lean principles to Identify Waste • Overproduction = Extra Features • Inventory = Requirements • Extra Processing Steps = Extra Steps • Motion = Finding Information • Defects = Defects Not Caught by Tests Licensed under Creative Commons by Naresh Jain 23

Using Lean principles to Identify Waste • Overproduction = Extra Features • Inventory = Requirements • Extra Processing Steps = Extra Steps • Motion = Finding Information • Defects = Defects Not Caught by Tests • Waiting = Waiting, Including Customers Licensed under Creative Commons by Naresh Jain 23

Using Lean principles to Identify Waste • Overproduction = Extra Features • Inventory = Requirements • Extra Processing Steps = Extra Steps • Motion = Finding Information • Defects = Defects Not Caught by Tests • Waiting = Waiting, Including Customers • Transportation = Handoffs Licensed under Creative Commons by Naresh Jain 23

Just In Time Licensed under Creative Commons by Naresh Jain 24

Just In Time • A pull system, driven by actual demand. The goal is to produce or provide one part just-in-time for the next operation. Reduces stock inventories, but leaves no room for schedule error. As much a managerial philosophy as it is an inventory system. Licensed under Creative Commons by Naresh Jain 24

Just In Time • A pull system, driven by actual demand. The goal is to produce or provide one part just-in-time for the next operation. Reduces stock inventories, but leaves no room for schedule error. As much a managerial philosophy as it is an inventory system. • Last Responsible Moment Licensed under Creative Commons by Naresh Jain 24

Just In Time • A pull system, driven by actual demand. The goal is to produce or provide one part just-in-time for the next operation. Reduces stock inventories, but leaves no room for schedule error. As much a managerial philosophy as it is an inventory system. • Last Responsible Moment • Just-In-Time Training - Training provided to individuals or units just before the skills or function taught will be used in a practical application. Typically used to teach perishable or infrequently used skills Licensed under Creative Commons by Naresh Jain 24

Licensed under Creative Commons by Naresh Jain 25

Can we beneﬁt more from ToC, JIT and Lean? Licensed under Creative Commons by Naresh Jain 25

What if... • We consider software team members as the machines in our software factories? • Can we apply ToC and beneﬁt? Licensed under Creative Commons by Naresh Jain 26

Consider this... Licensed under Creative Commons by Naresh Jain 27

Consider this... Time in days Licensed under Creative Commons by Naresh Jain 27

Consider this... Bug reported 0 Time in days Licensed under Creative Commons by Naresh Jain 27

Consider this... Reproduce Bug Bug reported 0 8 8 Time in days Licensed under Creative Commons by Naresh Jain 27

Consider this... Write failing test Reproduce Bug Bug reported 0 8 10 8 2 Time in days Licensed under Creative Commons by Naresh Jain 27

Consider this... Fix Bug Write failing test Reproduce Bug Bug reported 0 8 10 30 8 2 20 Time in days Licensed under Creative Commons by Naresh Jain 27

Consider this... Regression Testing Fix Bug Write failing test Reproduce Bug Bug reported 0 8 10 30 38 8 2 20 8 Time in days Licensed under Creative Commons by Naresh Jain 27

Consider this... Making a release Regression Testing Fix Bug Write failing test Reproduce Bug Bug reported 0 8 10 30 38 69 8 2 20 8 31 Time in days Licensed under Creative Commons by Naresh Jain 27

Consider this... Customer Signoff Making a release Regression Testing Fix Bug Write failing test Reproduce Bug Bug reported 0 8 10 30 38 69 71 8 2 20 8 31 5 Time in days Licensed under Creative Commons by Naresh Jain 27

Challenges making a Release • Developers not checking in frequently • Complicated and non-standard build process • Real Build owned by Conﬁg Mgmt Team • ... Licensed under Creative Commons by Naresh Jain 28

Fixing Release issues by applying JIT Practice Licensed under Creative Commons by Naresh Jain 29

Fixing Release issues by applying JIT Practice • Standardize build process for the whole team Licensed under Creative Commons by Naresh Jain 29

Fixing Release issues by applying JIT Practice • Standardize build process for the whole team • Manual integration on developers machines before checking in Licensed under Creative Commons by Naresh Jain 29

Fixing Release issues by applying JIT Practice • Standardize build process for the whole team • Manual integration on developers machines before checking in • Manual integration on an independent server machine Licensed under Creative Commons by Naresh Jain 29

Fixing Release issues by applying JIT Practice • Standardize build process for the whole team • Manual integration on developers machines before checking in • Manual integration on an independent server machine • Continuous integration using CI servers like CruiseControl Licensed under Creative Commons by Naresh Jain 29

After optimizing biggest bottleneck... Customer Signoff Making a release Regression Testing Fix Bug Write failing test Reproduce Bug Bug reported 0 8 10 30 38 44 49 8 2 20 8 5 6 Time in days Licensed under Creative Commons by Naresh Jain 30

After recursively applying ToC Licensed under Creative Commons by Naresh Jain 31

After recursively applying ToC • Total time to ﬁx any bug was 10 days...one two-week iteration Licensed under Creative Commons by Naresh Jain 31

After recursively applying ToC • Total time to ﬁx any bug was 10 days...one two-week iteration • Find practices or techniques that help solve this problem and recurse. Licensed under Creative Commons by Naresh Jain 31

Summary • ToC and JIT can be applied to software team’s “business” process • Using Retrospectives and other techniques Identify biggest stinkers [bottlenecks] • Use a JIT practice to elevate the bottleneck • Baby Steps - No Silver Bullets! • Recurse Licensed under Creative Commons by Naresh Jain 32

Thank You naresh@agilefaqs.com Licensed under Creative Commons by Naresh Jain 33

Using ToC And JIT Practice To Coach Agile Teams

1 comments

Notes on slide 1

6 Favorites