Remove sprint concept and center the coordination in the backlog #408
Conversation
…urposes. Use the cycle board for tracking and post-visibility
| about: Conduct a Sprint Planning meeting. | ||
| labels: "type: team-sync, :label: meeting:sprint-planning" | ||
| title: "Sprint Planning Meeting: {{ date | date('add', 1, 'days') | date('dddd, MMMM Do') }}" | ||
| name: "🚀 Coordination Planning Meeting" |
There was a problem hiding this comment.
Maybe just "Coordination Meeting"? It seems redundant to have both coordination and planning. Or maybe "cycle planning meeting" to match the "cycle-planning" label?
There was a problem hiding this comment.
I've always called this meeting just "planning meeting" 🤷🏼♀️
There was a problem hiding this comment.
It seems redundant to have both coordination and planning.
In fact, we are doing both things in the meeting 😉 (and we should decouple that in the future, IMHO).
"Cycle planning meeting" was the obvious choice, but I thought that title was not communicating enough info.
I would be willing to use whatever name the majority agrees on...
| title: "Sprint Planning Meeting: {{ date | date('add', 1, 'days') | date('dddd, MMMM Do') }}" | ||
| name: "🚀 Coordination Planning Meeting" | ||
| about: Conduct a Coordination Planning meeting. | ||
| labels: "type: team-sync, :label: meeting:cycle-planning" |
There was a problem hiding this comment.
We should make sure to rename this in our issues labels list
| --- | ||
|
|
||
| # 2i2c Sprint Planning meeting | ||
| # 2i2c Coordination Planning meeting |
There was a problem hiding this comment.
Weren't we planning on removing this issue template in general?
There was a problem hiding this comment.
I think so, but I did not address that idea in this PR.
| (coordination:sprint-board)= | ||
| ### The Sprint Board | ||
| (coordination:cycle-board)= | ||
| ### The Cycle Board |
There was a problem hiding this comment.
We don't use this board much anymore, right? Isn't your intention to sunset it? Or do you plan to start using it again?
There was a problem hiding this comment.
See my comment here: #408 (comment)
| We **should not have more backlog items than this amount**. | ||
|
|
||
| You can estimate the number of items on the board at any one time by assuming that **each team member (at 100% FTE) can accomplish about 2 items per sprint**. | ||
| You can estimate the number of items on the board at any one time by assuming that **each team member (at 100% FTE) can accomplish about 2 items per cycle**. |
There was a problem hiding this comment.
In practice I think that this math is pretty off - maybe we should just remove this section?
There was a problem hiding this comment.
I've left a few comments, @damianavila. Thanks a lot for updating these 🚀
| about: Conduct a Sprint Planning meeting. | ||
| labels: "type: team-sync, :label: meeting:sprint-planning" | ||
| title: "Sprint Planning Meeting: {{ date | date('add', 1, 'days') | date('dddd, MMMM Do') }}" | ||
| name: "🚀 Coordination Planning Meeting" |
There was a problem hiding this comment.
I've always called this meeting just "planning meeting" 🤷🏼♀️
| @@ -30,9 +30,9 @@ For each operations or support item, we should: | |||
|
|
|||
| For each project, its champion does the following: | |||
|
|
|||
| - Share accomplishments since the last sprint, demos, etc | |||
| - Share accomplishments since the last cycle, demos, etc | |||
There was a problem hiding this comment.
+1 on switching to cycle
| However, our work within a sprint is a **team commitment**, and we are all responsible for helping one another accomplish our tasks. | ||
| To begin each cycle, we collectively choose items to work on (or continue working) in the next cycle. | ||
| Each item should have a person assigned to it, who will be responsible for ensuring that the work gets done and a another person as a helper. | ||
| However, our work within a cycle is a **team commitment**, and we are all responsible for helping one another accomplish our tasks. |
The idea is to keep 2 boards:
|
Co-authored-by: Georgiana Elena <[email protected]>
Co-authored-by: Georgiana Elena <[email protected]>
|
Quick thought from me on:
If you think this board would be useful for the PM, then we should try it out! As long as we have a clear persona of who it is for, and why it is useful to them, I am on board with trying this out! What I want to avoid is "technically" saying that we use something, but in practice not using it because it isn't as helpful as we think |
Sure, that makes sense. I am totally on board to use (be the persona for) the "cycle" board (using my PM hat). |
|
gentle ping on this one @damianavila - do you think we have enough experience with the current system to document it in the Team Compass? |
|
@damianavila can we just close this one? I think we should update or coordination documents but not sure if this is up to date anymore anyway. |
|
This is old and no longer relevant because we are now again in a sprint-like process, so let's close it. |
Since we are not actually doing sprints in a classic way, I realized we should adjust the documentation to reflect what we are actually doing 😉.
The changes focus on getting rid of the "sprint" as a concept and replacing it with cycles.
We center the coordination at the backlog board level and use the "cycle" board just for tracking purposes.
Btw, this is in a draft state for early feedback.