Product Development Flow v1.1 (Milestone 13.6) Changelog
Link to specific changes in review app
Why is this change being made?
What is the problem we're trying to solve?
As indicated by the Product Survey the current product development flow:
- Doesn’t Encourage Cross-Functional Collaboration
- Has too Many Steps
- Is too Prescriptive
What are the changes we've made to try to solve the problem?
For v1 (Milestone 13.5) we pushed a beta with the following changes to the pd-flow draft page for initial dogfooding by 5 product teams:
- Introduced key participants table to clarify collaborators at each phase
- Replaced specific step by step instructions in each phase with potential activities to achieve specific outcomes
- Specified what’s required in each phase to labels and outcomes, leveraging Required
🔎
For v1.1 (this MR), we have introduced the following changes to the pd-flow draft page for dogfooding by the rest of the product development teams:
- Introduce interactive/improved visuals for workflow table and required items*
- Clarify required outcomes and optimize resources/links for activities as well as alternate issues types such as bugs
- Find opportunities to reduce/remove content from the page to create better focus on the flow
- Review and improve cross-functional from TWs, UXRs and stakeholders
*The workflow diagram will be visible in production and clickable pending the resolution of #10052 (closed)
Why are you being notified?
On December 4, 2020, we will merge this MR to replace the current pd-flow page with the draft pd-flow page. Product managers will be asked to work with their teams to leverage the "new" pd-flow starting with milestone 13.8.
What action is needed from you?
We ask for your patience and collaboration as we continue to optimize and update the "new" pd-flow per feedback from 13.6 dogfooding and as we collect and incorporate your feedback as well.
- Please watch the overview video
- Please check out the feedback issue for review guidance #10054 (closed). You're welcome to drop feedback into this MR till December 4 and into the feedback issue after this MR is merged on December 4.
- Please start referencing the new pd-flow no later than 13.8, and continue to provide feedback in issue: #10054 (closed). You're also welcome to raise MRs to the pd-flow page via the existing change process, if that's an easier way for you to collaborate on your feedback.
- Please attend one of the AMA sessions to help you onboard (invites forthcoming for the week of December 7, 2020): https://docs.google.com/document/d/1vrTu-dbBm5N7elKWa5HVofBu9kbzGz6jR50VfOLbq5A/edit#
Further references:
Epic: &938 (closed)
13.6 related issues/MRs:
Release notes
As indicated by the Product Survey the current product development flow:
- Doesn’t Encourage Cross-Functional Collaboration
- Has too Many Steps
- Is too Prescriptive
This leads to inefficiency and lack inconsistency in process due to lack of clarity on what is required vs not required. It also results in less focus on value to customers, as teams sift through what processes to follow (outputs) rather than how to better outcomes for the product. With v1 of the product development flow draft, we made a shift in the model to better align with best Agile/Lean practices by introducing an activities/outcomes based structure for the content, helping focus product teams on the outcomes each phase should achieve, rather than the outputs. We also clarified what is required in each phase, so product teams can more quickly understand what is necessary vs. optional, minimizing confusion, inconsistency and waste in the system. With v1.1, we have now further optimized in this direction by sweeping the content to further clarify collaboration opportunities, maximize resources to achieve outcomes and minimize content clutter and verbosity.
Related to: #9971 (closed)