During Q3 planning, we held sessions about each objective with all the teams contributing to the objective present. The goal of that meeting was to identify gaps, dependencies, risks and for all teams to have a general understanding of what other teams were doing to help inform their work.
Andrea led these sessions a bit on the fly and most teams found them valuable and productive. But if Andrea gets hit by a bus or someone else wants to lead those sessions, we need to write documentation about how to lead them. It could also be more valuable for Platform teams if we have clearly written what we expect of them and what they should expect in those sessions.
Acceptance Criteria
[x] Documentation is written on how to lead the big room planning sessions
[ ] Document how to capture dependencies between initiatives or epics in output of those plans
[ ] Documentation is written about how Platform teams should prepare and what they can expect
[ ] Documentation is written about what Platform teams should do with the information they learn in quarterly planning -- how is it represented on their roadmap
[ ] Documentation is written about the value and goals of big room planning
[ ] Documentation is socialized and we allow for feedback/iteration based on the feedback
Description
During Q3 planning, we held sessions about each objective with all the teams contributing to the objective present. The goal of that meeting was to identify gaps, dependencies, risks and for all teams to have a general understanding of what other teams were doing to help inform their work.
Andrea led these sessions a bit on the fly and most teams found them valuable and productive. But if Andrea gets hit by a bus or someone else wants to lead those sessions, we need to write documentation about how to lead them. It could also be more valuable for Platform teams if we have clearly written what we expect of them and what they should expect in those sessions.
Acceptance Criteria
Subject Areas