Define outcomes and activities for Validation phase 4: Solution Validation
Problems to solve:
-
Doesn’t Encourage Cross-Functional Collaboration
Currently, the problem development flow outlines a very detailed plan of solution validation. I believe that this plan appears to clearly articulate the cross functional collaboration, so I believe that this isn't a major concern for this section.
-
Too Many Steps
There are far too many steps within the Product Development flow for this section. I would like to propose moving the Solution Validation steps to a separate page as it's really a separate procedure within itself.
-
Too Prescriptive
In progress
Detailed problems to solve for reference: https://docs.google.com/presentation/d/1BxUVcoPyjYkR7MOHn1aZGllMCqlH5eb27JKM_bb_uDA/edit#slide=id.g94724597ab_3_0
Requirements: (can fall into multiple MRs)
-
Do not remove or change workflow labels -
Maintain or add clarity on what is REQUIRED per #9090 (closed)
Add a first cut at activities and outcomes as well as clarified what is required under !63496 (merged)
-
Maintain or add clarity on who the cross-functional collaborators in the phase are -
Consider referencing the current step by step as a sample flow -
Incorporate link outs to handbook resources that support activities to achieve outcomes
Potential template to leverage: !61793 (merged)