We saw:
- Controlling decision logic on multiple levels
- Tradeoffs ("good enough" rules, bug score)
- Self organization + System level alignment
Big benefit:
- Many quick, good decisions at the team level
More potential in Reinertsen's Decision Rules, but:
- Requires a comprehensive economic framework:
Value/Cost of features, defect fix, cost of delay
- Has to be semi-accurate
Scrum, Apples & Oranges
Different Classes of Service
How do you prioritize?!
Decision Rules
Scrum backlogs
Principles of Decision Rules:
Criteria for success
Self Organized Self Directed
1. Decentralize economic control
2. Control decision logic - not process
Ah HA! You CAN compare them!
Example: Boeing 777
How to do it?
=$1.15
=$2.30
1 Lb
$300
AG
Case Study: Software - webMethods Suite
100% Tests Pass to promote build
Stop & Fix
Root Cause Analysis
Visualization helps Self-Organization (of teams!) Towards a Goal
Customer Issues
OK,
so customer
Issues are #1...
Done
In Progress
Results:
New status quo (recent 15 months):
Queue size (blue): 70-80% less
Age in queue (yellow): 70-80% less
TO DO
Experiment #1: Scrum by the Book
Catching up (8 months)
Customer
Issues
-Urgent issues can't wait
-Triage and schedule is waste
-Interrupting the experts
OK: Less than 15
Tests /
Integration
Critical = 8 pts
High = 5 pts
Medium = 2 pts
Severity
Based
Score:
Low = 1 pt
OK: 100% of tests pass
Internal
Defects
OK: Score is within Plan
Experiment #2: Do it Immediately
Feature
Work
+Faster response
-Lost feature work focus
Experiment #3: Round Robin "Fire Fighter"
+/-Fast response time (unless high load)
+Learn by doing
+Others can focus
+Fair
Experiment #4: "Fire Fighter" + Help Threshold
Suite-Wide
Continuous Integration
Reduce Known Defects
Features
Suite Wide Backlog