Add backlog refinement process for Create:Editor
Why is this change being made?
Part of our weekly process for the Create:Editor BE team is to do a backlog refinement process. I wanted to document this process to increase transparency, share learnings, and to identify any areas for improvement.
Note: This is a very similar process for the Create:Knowledge BE team. I will document that in a separate MR after this one has been reviewed/merged.
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][transparency] -
Assign this change to the correct DRI - If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
- 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][mr-buddies-slack].
- If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping
@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.