I’m really sorry about this late reply. Too many fires this sprint!
Yeah that’s a great point.
Although people who want to work ahead can work ahead on the tasks, the checklist should indicate that it is possible to work ahead on stuff by specifying a timeframe instead of just a deadline.
This also helps with the “My Week” view.
I added them back 
Actually, seeing the next change makes me wonder why we don’t standardize around the gantt view, rather than the default table? Would this make the choice between these two views moot?
I love this idea, but the only reason I think twice about it is because monday.com’s UI feels laggy.
But yeah, it’s more useful to provide a Gantt Chart than struggle with organizing the checklist in groups.
Also, yeah we would just then be able to group them by week in the actual table, since a better detailed view would be possible in the Gantt Chart.
For some of the others, have we carefully considered the effects of removing them? I’m not copying all of the items, but for example…
Yeah, I thought about it and I agree. The points you highlighted are the ones I couldn’t remove to be honest, because they feel important as a documentation for the process.
“Check if you are overcommitted” Task
- **Check if you are overcommitted, and if so pass on tasks to people** with room, or further reduce/split the scope of your tasks as necessary. (extra “overcommitted” check)
Although I removed this task, it was a duplicate. There’s another task identical to this one.
“Pre-assign all tasks” Task
- Pre-assign all tasks that need to be included in the upcoming sprint at least tentatively (arbitrarily if needed) and - assign CAT-1 priority to them to mark them as required for next sprint. Flag tickets to mark them as tentatively assigned. To flag a ticket, right-click a task from the backlog or sprint view and select "Add flag".The ticket will then appear in orange in the backlog. Or when Editing a ticket, tick the Impediment checkbox
Although I removed the task mentioned above, I added it’s description to another task, which is shown below.
Finish to create & move tickets to the upcoming sprint.
Thursday of week 2 is the ticket creation cutoff, no ticket created after the end of that day can make it in the upcoming sprint, except as described in task insertion.
Pre-assign all tasks that need to be included in the upcoming sprint at least tentatively (arbitrarily if needed) and
- assign CAT-1 priority to them to mark them as required for next sprint.
- Flag tickets to mark them as tentatively assigned. To flag a ticket, right-click a task from the backlog or sprint view and select “Add flag”.The ticket will then appear in orange in the backlog. Or when Editing a ticket, tick the Impediment checkbox
“Ping other potential task assignees” task
It seems like I forgot to include that in one of the descriptions, so I just added it to the task mentioned above, which makes it:
Finish to create & move tickets to the upcoming sprint.
Thursday of week 2 is the ticket creation cutoff, no ticket created after the end of that day can make it in the upcoming sprint, except as described in task insertion.
Pre-assign all tasks that need to be included in the upcoming sprint at least tentatively (arbitrarily if needed) and
- assign CAT-1 priority to them to mark them as required for next sprint.
- Flag tickets to mark them as tentatively assigned. To flag a ticket, right-click a task from the backlog or sprint view and select “Add flag”.The ticket will then appear in orange in the backlog. Or when Editing a ticket, tick the Impediment checkbox
- Ping other potential task assignees on the tasks you have assigned or been assigned on (especially arbitrarily), as well as potential reviewers
If people stop doing this type of steps, wouldn’t this break the process, or at the minimum create more work for sprint planning managers to chase people to do these?
You’re right, if people stop doing the steps, we won’t benefit. But what I’m trying to do is decrease the steps and expand the documentation about it.
So instead of having a lot of subtasks regarding a specific item, move that into the description or documentation of the task.
Let me know though if you disagree, maybe we can try approaching this with the Workflow Manager instead, since it would have documentation, and not just a description box.
And even if existing core team members remembered to do these without being reminded, how would newcomers know to do any of this in the first place, if this isn’t in the process description and steps? emember that this is also our primary source of truth and documentation about the sprint planning process.
I didn’t intend to delete anything important. The main reason I shared the difference in the task descriptions is so that members can call me out in case I deleted something important.
I’ll wait to see your thoughts about moving the details out of the actual tasks and into the task description. And I’ll either proceed with the changes or revert them