Integrating Six Sigma and Lean Manufacturing The Challenges & Benefits
Integrating Six Sigma Thinking Into Scrum Based Development Environments
-
Upload
drashid -
Category
Technology
-
view
1.913 -
download
1
description
Transcript of Integrating Six Sigma Thinking Into Scrum Based Development Environments
![Page 1: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/1.jpg)
Integrating Six Sigma THINKING into Scrum-Based Development Environments
Darian RashidAgile Trainer and [email protected]
![Page 2: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/2.jpg)
Lean Six Sigma THINKING in Software Development
• What is Six Sigma Thinking
• Six Sigma Myths and Misconceptions
• A Common Ancestry and Values
• Review role of the Scrum Master• Using Six Sigma Within a Development
Organization• Case Study
![Page 3: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/3.jpg)
Symptoms
![Page 4: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/4.jpg)
Lean Six Sigma is a Method to…
Solve complex problems by:– Establishing a measurable gap– Digging deep
– Finding root causes
![Page 5: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/5.jpg)
Root Causes
• Hidden
• Usually multiple
• Usually interacting
• Find the “vital few”
![Page 6: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/6.jpg)
Lean Six Sigma Thinking is…
Systems thinking
![Page 7: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/7.jpg)
![Page 8: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/8.jpg)
Lean Six Sigma Thinking Requires You To…
• Scale with the problem
• Compare before and after
![Page 9: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/9.jpg)
Perceptions in S/W Dev. Environment
• Tool blamed for misuse
• Misconceptions– Is for manufacturing
– Requires a degree in Statistics
• No cross-realm expertise
![Page 10: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/10.jpg)
Part of Continuous Improvement
• Lean methods have been evolving for the last several hundred years
• Lean Six Sigma is part of that evolution
• Common values – Continuous Improvement
![Page 11: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/11.jpg)
The FoundationWalter Shewhart
1924• Control charts• Statistical Process Control• Continuous Improvement
![Page 12: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/12.jpg)
The ScrumMaster
• Owns the process of Scrum
• Have impediments removed
• Agent of change!
SM
![Page 13: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/13.jpg)
Waste &
ValueValue
Stream Mapping Process
Maps
5S
Time Duration Analysis
Trends Analysis
Job Characterist
icModel
Programmatic
Change Avoidance
Structural vs
Attitudinal
Levels of Analysis
Contain, Correct, &
PreventSources of
Power
Resource Types
Open Systems
Model
Balanced Metrics
PFQT
Thinking Modes
Process Types
Data Management
Structure Trend
Accountable Hierarchies Differentiati
on & Integration
Size, Bureaucracy
& Life Cycles
Six Sigma
Gap Analysis
Levels of Learning
Culture Analysis Sustain
Ergo & Safety
Mistake Proofing
VisualMgmt
Metrics
CellularStructure
Flow & Motion
Balance & Leveling
Pull vs Push
Workflow
Spaghetti Diagrams
Problem Solving Root Cause
Analysis
KAIZENIssue
Resolution
Organizational Analysis
Value Add Analysis
Transparency
ABC vs RRR
Change, Awareness
& Fear
Job Analysis
Work Design
Value Add Analysis
Transparency
UniversalProcess
Structural vs
Attitudinal
Waste Analysis
Leadership
Change
Culture
Structure
Levels of Analysis
Many Tools in Change Arsenal
![Page 14: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/14.jpg)
ValidateGains
ReviseTransformation
Backlog
Gap Analysis
Take corrective actionusing the right method
Filter
Define Measure Analyze Improve Control
![Page 15: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/15.jpg)
The Roadmap
Mechanic Doctor Barrier-Buster
Define Car trouble Describe illness or injury Establish a gap
Measure Diagnostics, memory, codes
Temperature, blood pressure, history
Create hypotheses for causes,
Collect data
AnalyzeFlight test
Sensor Stimulator
Blood test, x-ray, scan, exploratory
Root cause analysis
Confirm factors
Improve Repair, tune, rework, replace
Surgery, medication, exercise, splint
Create improvements
ControlVerify,
maintain, and record
Follow-up visit, ongoing treatment, maintenance
drugValidate improvements
![Page 16: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/16.jpg)
Identifying the Right Problems
• Systemic issues
• Issues that were fixed that reappeared
• Issues where the root cause is unknown
![Page 17: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/17.jpg)
Exploring Gaps in Software Environments
• Easy to blame people
Quality level too lowConsistently
miss iteration goals
Most builds fail
Builds too slow
Miss release targets
![Page 18: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/18.jpg)
Possible Factors Causing Gaps
How can we be sure?
Others…
Problem / Gap
Knowledge
Lacking the right tools Incorrect
process
Environment
![Page 19: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/19.jpg)
Use Data
• Use data as a tool to get insights
• Simple charts usually reveal a lot about what is happening
• Measure only as long as you need– Short-term for diagnostics
– Long-term for control over regression
![Page 20: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/20.jpg)
Get to Root Causes - Ask “Why?”
SymptomProblem / Gap
Symptom
Root Cause
Symptom
Root Cause
Why?
Why?
Why?
Why?
Why?
Why?
Why?
Why?
Why?
Why?
Why?
Why?
Why? Why?
Why?
Why?
Why?
Why?
Why?
Why?
Why?
Why?
Why?
Why?
Why?
Why?
Why?
Why?
Why?
Why?
Why?
Why?
Why?
Why?
Why?
Why?
![Page 21: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/21.jpg)
The Journey
• Knowing the destination doesn’t mean the journey is mapped out
• If it were that easy, most would just do it
• Sometimes we need to prove we need to take the journey
![Page 22: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/22.jpg)
Case Study
• Large B2B enterprise
• Methodology at best “Scrum-ish”
• Current product 2 months from launch
• Release date was going to be missed– Projected delay of 5 months
![Page 23: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/23.jpg)
Case Study
• Slip wasn’t realized until 4 weeks prior
• Development group was blamed
• Working 60-80 hours since
![Page 24: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/24.jpg)
The Roadmap
Define Establish a gap
MeasureCreate hypotheses for causes
Collect data to reveal what
AnalyzeRoot cause analysis to reveal why
Confirm main factors
ImproveCreate improvements
May be phased
ControlValidate improvements
Create controls against regression
![Page 25: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/25.jpg)
Establish a Gap
Why is the release late?
Outstanding features
Why? No time to work on features. Fixing defects
during most of the iteration
![Page 26: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/26.jpg)
Establish a Gap
Why don’t you stop and burn down defects? “No time for that”
“Value is in features, not defects”
How many defects are currently open?
1200+ severity 1 & 2
Is this the first release like this?
No, last 3 releases were worse!
![Page 27: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/27.jpg)
Define Gaps
• Short term– Launch date projected to be missed by
5 months
– Number of defects at 1200+
• Longer term– No predictability of release
– Product integrity is below releasable standards
![Page 28: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/28.jpg)
The Roadmap
Define Establish a gap
Measure Collect data to reveal what the factors are
AnalyzeRoot cause analysis to reveal why
Confirm main factors
ImproveCreate improvements
May be phased
ControlValidate improvements
Create controls against regression
![Page 29: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/29.jpg)
Defect detection rate is stable over time
Day
Def
ects
sub
mit
ted
Each
Day
272421181512963
Defects Submitted Each Day
![Page 30: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/30.jpg)
Fixing less defects everyday
Day
Def
ects
Fix
ed E
ach
Day
2421181512963
Defects Fixed Each Day
![Page 31: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/31.jpg)
Number of open defects was increasing
24222018161412108642
Open Defects Per Day
![Page 32: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/32.jpg)
Median of 7 weeks from ‘find’ to ‘verify fix’…and increasing
Weeks
Defect Found
Fix Verified
![Page 33: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/33.jpg)
Hours per defect were going up
Day
Hou
rs P
er D
efec
t Ea
ch D
ay
222018161412108642
Hours Spent Per Defect Each Day
![Page 34: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/34.jpg)
The Roadmap
Define Establish a gap
Measure Collect data to reveal what the factors are
Analyze Root cause analysis to reveal why
ImproveCreate improvements
May be phased
ControlValidate improvements
Create controls against regression
![Page 35: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/35.jpg)
Symptom 1
• Still working on new features
• Q/A’s priority was to always test new features
• A fixed defect could wait on backlog to verify
Gap between ‘find’ and ‘verify fix’ was increasing
Cau
se 1
![Page 36: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/36.jpg)
Symptom 1
More pressure to get new features out– Sustained overtime
– Quality of code was worse over time
– Defects that were assigned to the team were ‘bounced’ back to buy time
• Ye olde ‘can’t replicate’. Works every time
• Resulted in entire test suite being rerun
Gap between ‘find’ and ‘verify fix’ was increasing
Cau
se 2
![Page 37: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/37.jpg)
Symptom 1
• Fixing less defects over time
• Still working on new features
• New features were full of defects
• Defect find rate > defect fix rate increasing gap
Gap between ‘find’ and ‘verify fix’ was increasing
Cau
se 3
![Page 38: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/38.jpg)
Symptom 1
More defects + Less feature progress = more status meeting and written reports
Gap between ‘find’ and ‘verify fix’ was increasing
Cau
se 4
![Page 39: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/39.jpg)
Symptom 1
• Only development was ‘doing Scrum’
• Q/A was not considered ‘eligible’
• Product Owners valued getting the product out over quality
Gap between ‘find’ and ‘verify fix’ was increasing
Cau
se 5
![Page 40: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/40.jpg)
Symptom 2
Why? We were cherry-picking the easy ones
The data showed the complexity of the defects were getting higher?
Why? To increase velocity. Defects count toward it
Why? Velocity is used to compare teams*
Rate of defects corrected is decreasing
Cause
![Page 41: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/41.jpg)
Symptom 3
Velocity used to compare teams– Defects, meetings and more counted toward
velocity
– Measured tasks, not forward progress or efficiency
No visibility into release delay until too late
Cau
se 1
![Page 42: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/42.jpg)
Symptom 3
Why? Did not track progress toward release plan
Product Owners were disengaged from each iteration
Why? Did not have a release plan
Why?ScrumMasters were not
allowed to work with them*
No visibility into release getting delayed until later stages
Cause2
![Page 43: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/43.jpg)
1. Development and Q/A seen as a separate function
– Even located in separate buildings
2. No universal definition of ‘Done’
3. No trust between managers and teams
Dig Deeper: Root Causes
![Page 44: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/44.jpg)
4. Iterations were a developer-only practice
5. Product Owner incentives based solely on number of features
6. Post-release patches made ‘heros’
Root Causes
![Page 45: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/45.jpg)
The Roadmap
Define Establish a gap
Measure Collect data to reveal what the factors are
AnalyzeRoot cause analysis to reveal why
Confirm main factors
ImproveCreate improvements
May be phased
ControlValidate improvements
Create controls against regression
![Page 46: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/46.jpg)
• ‘Stopped the line’!
• Reprioritized defects and features together with POs
• Q/A worked intimately with developers– Temporarily moved to same location
First Iteration: Triage
![Page 47: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/47.jpg)
• Reprioritized defects burned down in 4 weeks
• Productivity was higher on stable release
• Q/A continued to work along side dev.
• Release was only 1 month late
Results
![Page 48: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/48.jpg)
• Started “10 then 10” initiative– Lower maximum outstanding defects
by a factor of ‘10’
• WIP-cap was put into place– ScrumMaster and team alerted PO if
WIP-cap was reached
– Stories were suspended
– Root-cause analyses were performed
Second Iteration: Longer Term
![Page 49: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/49.jpg)
• Continuous Integration and automated tests infrastructure was built
• Internal Scrum team dedicated to infrastructure
• Took more than 1 year
Phase 2: Longer Term
![Page 50: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/50.jpg)
Current maximum number of open defects: 125 COMBINED
Down from over 1200
Results
![Page 51: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/51.jpg)
• Second 10x reduction
• Goal: no more than 15 open defects COMBINED
• Q/A mostly disbanded– Most working as part of team
– System strike force remains
Third Iteration: Currently In the Journey
![Page 52: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/52.jpg)
Larger Gap: Release Dates Constantly Missed
Features not completedMissed
Deadline
Defects were
ignored
Very late integration
Horizontal Stories
Horizontal Scrum teams
Management did not
want feature teams
Understood own
competencies
Separate Q/A group
No budget for servers
No infrastructure
No continuous integration
Not enough time
Estimates are done for
team
Team not involved in planning
No formal release plan
Set of loose goals
sufficedEvery
feature is Priority 1
Too many features
Too many defects
No timeNo automated
testing
Incentives based on
new features
Worried about advancement
REWARDS MISALLIGNED
Patches make heros!
Not important to
PO
Not important to developers
System not stable
No defined backlog to work from
Not defined well
Iteration goals not
met
CURRENT CULTURE
Didn’t trust team’s
estimates
![Page 53: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/53.jpg)
• Lean Six Sigma thinking means– Identify gaps
– Look past symptoms
– Use data to find causes
– Dig deeper to find root causes (and interactions)
• Agile and Lean Six Sigma have common ancestry and values
Key Points
![Page 54: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/54.jpg)
• Don’t let misconceptions keep you from a powerful tool
• ScrumMasters and change agents need good tools in their arsenal– The thinking can always be used
– Can scale with the problem
Key Points
![Page 55: Integrating Six Sigma Thinking Into Scrum Based Development Environments](https://reader034.fdocuments.in/reader034/viewer/2022042813/547ea73e5806b5db5e8b46f9/html5/thumbnails/55.jpg)
• Even if you know the final destination, using data-based decision-making and root cause analysis can help you find the best path
Key Points