Scraps from various sources and my own writings on Generative AI, AGI, Digital, Disruption, Agile, Scrum, Kanban, Scaled Agile, XP, TDD, FDD, DevOps, Design Thinking, etc.
Page Hits
Showing posts with label VSM. Show all posts
Showing posts with label VSM. Show all posts
Monday, July 13, 2020
Monday, June 10, 2019
Value Stream
This is for my own reference:
- You are able to tell all the product / services your unit / vertical produces / offers.
- You are able to map the products / services back to the teams (A 1-1 mapping or multiple teams that deliver a particular product / service. Efficiency decreases / time to market increases if there are multiple teams mapped to a product / service).
Wednesday, April 24, 2019
Wednesday, February 06, 2019
Value Stream Mapping (VSM) - How To
It shows the diagram of all the major steps involved in delivery a product or service from supplier to customer. 
How is it different from a Process Map?
It is a High-level process map, however with additional customer data, process data, information flows to get sense of where a value is added and where there is a waste.
It is used to:
- Map flow
- Understand dependencies
- Identify and Understand sources of waste
- Remove waste
- Re-create an efficient process
What if you don't have hard data?
- Walk the process
- Observe
- Obtain estimates from people
- Get collective estimates of project team
VSM Limitations
Limitations of VSM:
1. Finding deficiencies and getting rid of them is not the way for improving performance of a system.
2.The definition of what a value stream is, is itself fuzzy:
a. It doesn't capture all specific actions
b. VSM should be typically applied to product, but often gets applied to product families with little guidance about what constitutes those families.
c. VSM is cumbersome when product variety is high and volume is low (Media team has more than 20 product / product families; and we are looking at only the 10 important activities in each stream, not looking at all the activities in each stream).
Subscribe to:
Comments (Atom)
If we already have automation, what's the need for Agents?
“Automation” and “agent” sound similar — but they solve very different classes of problems. Automation = Fixed Instruction → Fixed Outcome ...
- 
Requirements Analysis -- Business requirements document or business requirements specification System Design -- Systems requireme...


 
 






 
