Product Development Flow: Add `workflow::refinement` as optional step to build phase 1
Why is this change being made?
It was noted as part of feedback about the revised product development flow that some teams break out backlog refinement from planning breakdown. This addition allows them to focus their implementation plan and estimation activities on the portion of an issue which is slated to be delivered first. This MR documents this as an optional step as part of Planning phase of the Build track.
Related issues
Author Checklist
-
Provided a concise title for the MR -
Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what -
Assign this change to the correct DRI - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the "Maintained by" section in on the page being edited.
- If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies.
-
If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping(this requirement has been removed pending identification of a new DRI for the handbook)@gl-static-site-editor
in a comment for a review and merge. For example changes to.gitlab-ci.yml
, JavaScript/CSS/Ruby code or the layout files.
Edited by Farnoosh Seifoddini