-
Speed, Quality, Low Cost
- Starting with low cost has limited value, causes poor decisions
- Starting with quality may not add value
- Starting with speed with quality gives insights
- Requires quality for stability
- Speed and quality result in lower cost
-
Lean Principles
- Optimize the whole
- Eliminate Waste
- Build Quality In
- Deliver Fast
- Defer Commitment
- Create Knowledge
- Respect People
-
Fast-Flexible-Flow
- Value defined
-
Pipeline of production
- Ideas in, value out
-
Smooth (fast) flow requires
- Quality (remove impediments)
- Proper Management
- The flow from beginning to end of creating the value
- Often cuts across companies, virtually always cuts across organizations
- It should look at the sequence of steps that transform the original idea into value in the customers’ hands
-
Creating Value Maps
- Step1: Identify Actions
- Step2: Determine Calendar Time
- Step 3: Calculate Time Actually worked on action
- Step 4: Identify Time Between Actions
- Step 5: Identify Loop Backs Required
- Step 6: Identify how many items are waiting before an action starts
-
Step 7: Compute Process Cycle Efficiency
- Time Worked/Total Cycle Time
-
Focus on Time
- Focusing on delays uncovers problems
- Goal is to optimize the whole, not just parts
- Delays, context/task switching that causes delays... gives insights into speeding up process and eliminating waste
-
Goal of Lean-Agile Software Development
- Lean Software Development enables the discovery, prioritization, and delivery of highest business value
- Agile methods enable the incremental delivery of business value based on the team’s capabilities
-
Three Kinds of Work
- Adds Value
- Does not add value
- Incorrectly adds value (req. for process but does not improve product directly)