How to run a season-based project
Season Dates
- Sprint 1:
- Sprint 2:
- etc.
(**Horizontals:
Verticals:**)
Operating Model
Section titled “Operating Model”Cadence
Section titled “Cadence”Teams Channels / Communication
Section titled “Teams Channels / Communication”SharePoint
Section titled “SharePoint”The individual on point for the workstream.
This helps streamline communications and accelerate decision making.
DRIs are expected to attend meetings, provide status, show demos and ensure their workstream is moving forward. Given that most of this work is already in-flight we are NOT adopting strict Squad models here with the requirements of 80%-time commitment, however DRIs should have the capacity to meaningfully move the workstream forward.
DRIs are also expected to ESCALATE when things are stuck. Escalation is not a bad word here, instead it helps us move fast. If you are stuck, blocked or need help finding the right decision maker please escalate early and often. Lead person X is here to help.
| Cycle Mission: (Concrete and falsifiable outcome for this cycle, in 1 sentence – should be pithy and straight to the point) | |
|---|---|
| North-star goal: (1-3 sentences describing the “6-month” goal the squad is working backwards towards. This section will generally stay stable between cycles, and frames how the cycle success criteria works towards big, end-to-end value) | |
| Priority Justification: (why do we absolutely need this squad? What is the expected impact? - ex. We are building a foundational infra that products [X/Y] require. Without it, [risk/cost] - ex. Squad is prioritizing to address a perishable opportunity to do [x] - ex. Intent to drive [impact metric goal] toward [x] strategic priority | |
| Cycle Success criteria: (list of concrete deliverables for the cycle - Should be concrete (ex: “GA feature X”, ) or quantified (ex: “Grow usage by X%”. If you are reducing complexity or deprecating X, it can also be the success criteria) … | |
| DRI: (username) PM: (username – optional) | Squad Contact: (teams-channel name) |
| Squad Members: (list of squad member alias from Microsoft) … | Number of people in the squad: X |
| Problem: (Problem we are trying to solve) …. | Proposed approach: (How) …. |
| Ship Plan: Sprint 1: - … Sprint 2: - … Sprint 3: - … | Risks (What are the possible risks?) |
| Additional resources: (PRD, RFC, vision docs, figma, one-pagers, etc) | Dependencies: (Depends on Squad X, Enables Squad Y) |
| Out-of-scope/Non-Goals (List the features discussed which are out of scope or might be revisited later. What have you explicitly decided not to do and why?) |