SdV101 Value Stream Management: Difference between revisions
No edit summary |
|||
Line 19: | Line 19: | ||
=Mapping to SdV 101 Framework= | =Mapping to SdV 101 Framework= | ||
The following figure is mapping this module to the SdV 101 Framework. | The following figure is mapping this module to the SdV 101 Framework. | ||
[[File:SdV101 Fwk VSM.png|800px|frameless|center|SdV101 Fwk VSM]] | |||
=Motivation= | =Motivation= |
Revision as of 02:41, 5 November 2022
This module introduces the concept of two value streams moving at different speeds: the physical and the digital value streams for automotive. It also provides a discussion of constrains (e.g. functional safety) and prerequisites (e.g. vehicle abstraction). A deep dive on two speed development and DevOps for the digital value stream is provided. Finally, the perspective of platforms for Value Stream Management is discussed.
Mapping to SdV 101 Framework
The following figure is mapping this module to the SdV 101 Framework.
Motivation
Why is Value Stream Management so important to implement the SdV? And what does it have to do with sushi and bento boxes? Find out more in this lesson.
Value Streams in today`s software world
This lesson is looking at value streams in today`s software world and is building bridges to the SdV.
Why is automotive software different?
This lesson is addressing key differences between traditional software development and software development in the world of automotive.
Automotive features: The product manager`s per perspective
This session is looking at the product manager`s per perspective, and how the product manager can best utilize value stream management to implement new features utilizing SdV.
What does this mean for VSM + SdV?
This lesson is doing a deep dive on the relationship between Value Stream Management and the Software-defined Vehicle.