agile and toc - can oil and water mix
TRANSCRIPT
Agile & TOC
Aviram Eisenberg, CEO, Ignite
About Ignite
Ignite is a pure play software development companyOutsourcing Boutique targeting Israeli ISVsSpecialize in global delivery models of software developmentDistributed Agile development methodologySenior onsite Israeli R&D managersOffshore centers in Ukraine, Belarus, Russia and MexicoEngagement Models:
Fixed-priceODCMilestone-based pricing
Headed by Aviram Eisenberg, former Chief Architect at MIND CTI and chairman of the Israeli Software Development Managers Forum
Agile Highlights
Claims that SW development is a spiral process hence waterfall model is usually not effectiveDevelop in short iterations (sprints) that contain that each contain the spec analysis, estimations, design develop and testingWorking software must be delivered at each iterationDue dates are fixed, scope can be changedPareto: 80% of SW value comes from 20% of the featuresCustomer calibration – prioritization of backlogUser stories vs. feature specifications The R&D team has much more freedom of choiceTest AutomationContinuous integration – code cannot break!
Agile – take 1
Planning I0
Task 1
Task 2
Testing
Planning I1
Task 3
Task 4
Testing
Agile – take 2
Planning I0
Task 1
Task 2
Testing
Planning I1
Task 4
Task 3
Testing
HL Planning
Integration Planning
Integration
Testing
TOC Highlights
Improve throughput of complex projectsIdentify and protect the critical chainThe TOC process:
Identify the system’s constraint(s)Decide how to exploit the system’s constraint(s)Subordinate everything else to the decision in step 2 Solve the system’s constraint(s)Return to step 1 if the system’s constraints were changed
TOC Highlights
Plan all activities according to 50% probability estimations – Parkinson’s Law
Add time buffer at the end of each path (feeding/project buffers)
Add resource buffers to assist on bottlenecks
Avoid multitasking along the critical chain
Monitor buffer consumption as opposed to task schedule
TOC
Architecture
Management
Design
Design
Task 1
Task 2
Task 3
Task 4 Testing
Testing
Integration
Architecture
Design
Task 4
Architecture
Design
TestingTask 4
Architecture
Design Integration
TestingTask 4
Architecture
Design
TOC
Architecture
Management
Design
Design
Task 1
Task 2
Task 3
Task 4 Testing
Resource Pool
Testing
Integration
ArchitectureArchitectureArchitectureArchitecture
FB
FB PB
TOC vs Agile
Criteria TOC Agile
Target verticals Any type of complex project
Software development
Type of projects Multi team complex project Simpler projects
Nature of projects Any type of multi project Spiral type
Primary target Enhance throughput Deliver working software on time
Focus Bottlenecks Inherent problems of SW development
Research Vs Development
Excels at development project
Excels at research projects
Strategic vs Tactic Strategic planning Tactic Planning
Statistics
The standard stats:More than 60% projects fail to meet budget and due date objectives by more than 200%30% of projects are cancelled70% fall short of scope
Agile stats:99% chance to meet due dateBetter quality softwareImproved customer satisfaction
TOC:10% to 50% improvement on throughput90 to 95% to meet due date and budget
Agile or TOC
So, Agile or TOC?It depends on project characteristics
Why not use both?
TOC with Agile
Planning I0
Task 1
Task 2
Testing
Planning I1
Task 4
Task 3
Testing
HL Planning
Integration Planning
Integration
Testing
Iteration 0
Iteration 1Iteration 1Integration PB
FB
Q&AAviram Eisenberg
Ignitewww.igniteoutsourcing.com