I'm trying to get a gist of Value Stream Mapping and how to apply it to a suggestion to working software process that we have.
Since we are developing products, and don't do client work, there's no hard "pull" - customer requests something, and if sufficient number of people is interested we'll consider adding it.
Here are the steps:
- Customer requests a feature,
- Support records feedback and adds +1 for the feature,
- Support prepares a monthly report,
- Product owner reviews the suggestions report,
- Product owner decides that feature should be developed,
- Feature is analyzed and designed,
- We wait until one development team is free to take on the feature,
- Product owner presents the feature to the development team,
- Team has a (longish) meeting where feature is broken down to small tasks, and each task is given an estimate. Based on these estimates, due date is set,
- Team implements a feature,
- QA is done (feedback loop included, developers may need to correct the software)
- Code review is done (feedback loop included, developers may need to correct the software)
- Documentation is written
- Announcement data is written
- Feature is released
- Customers who requested the feature are informed
That's a lot of steps. I included everything, for the sake of an exercise. Which of these steps would you consider Value Adding and which Non-Value Adding and why?
One bit in particular pushed me to create this question: should we consider detailed estimation step VA or NVA? Developers do a lot of design work in that stage, so I'm not 100% sure where to put it.