Value Stream Map
"Lean thinking defines value as providing benefit to the customer; anything else is waste." – Eric Ries
Requirements
Development
Integration
Packaging
Certification
Deployment
Release
Implement testable task within story
Review acceptance tests
Run unit tests
Create pull request
Run static analysis
Run acceptance tests
Peer review code
Respond to review comments
Notes
What activities are being performed?
Who delivers those activities? How much of their time is dedicated to those activities?
What is the yield, i.e. ‘right first time’? What % of rework is generated? What causes rework?
What tools are required to complete the step? And what other inputs are required?
How many units (e.g. work packages) are ‘work in progress’ within this step?
How many units are waiting in the ‘inbox’? How will they be prioritized or scheduled? How long will they, typically, wait for?
How long does the step take? How much of that time is effort, or touch time, versus duration, or in-process lead-time?
Resource Checklist
Related Topics
See Also
Lean Value Stream Mapping for DevOps (Katie Sotheran)
Value Stream Mapping (Karen Martin and Mike Osterling)