Discussion: technical writing milestone planning process
Issue Description
@gl-docsteam Please review and add your process information for upcoming releases to this Google sheet by Wednesday, July 14. We’re happy to discuss processes in 1:1s, and if you see things that others are doing that you’d also like to do, try it out!
We’ve started discussions on how we plan our work for the next milestone. We wanted to bring that discussion into an issue, and get to an MVC set of changes - if we need them - to the existing planning process.
For added context, these are some of the ideas and questions we have in mind that having data might help with understanding:
- Get a better view of the incoming feature work before it arrives in our To Do’s as review requests. Identify areas that may need cross-group and cross-stage collaboration ahead of doing the work.
- Find a common view in GitLab of the next milestone work, that makes it easy for us to view the upcoming docs work and plan across stages and groups.
- Identify groups (early) that are likely to experience a particularly “docs heavy” milestone, and work as a team to mitigate the impact.
- Build experience and data to help with conversations about our gearing ratio.
As we learn more about how we as a team prepare and plan for each upcoming release, we’ll create new issues and process updates to discuss any available improvements.