Support both MVC and exploration ideation efforts, and document dedicated involvement from key stakeholders for feedback into the validation track
Why is this change being made?
The current product development workflow is less clear about how key stakeholders are involved in the workflow::design phase. In order for PD's to do successful ideation, they need dedicated support from, amongst others, engineering and PM.
This amendment intends to document this more clearly as the involvement of key stakeholders should be scheduled for in terms of availability. Their availability should be regarded as design reviewers only, ready to give feedback and fuel conversations. PD's continue to be the DRI's though.
The current product development workflow is somewhat ambiguous about supporting exploratory design efforts extending beyond just the first MVC. This edit intends to document that a bit more clearly. Exploratory design efforts are useful to create the context needed for successful first and potential second release design artifacts.
Lastly, this merge request implements a divider to give the workflow::design phase a little more visibility.
Does this MR meet the acceptance criteria?
Conformity
-
Added description to this MR explaining the reasons for the proposed change, per say-why-not-just-what