Goals:
1. Enable the team to say what they did last week and what they are working on this week.
2. Prevent the team from feeling overwhelmed. Estimate and assign tasks that fit in the timebox.
3. Inspire collaboration in the team. Prioritize helping teammates deliver their tasks before starting something from the backlog.
4. Avoid scope creep. Make sure tasks in the timebox are well defined, and don't prioritize new tickets without deep consideration.

AC:

• [x] Sprint length: 2 weeks, and all reporting based on this
• [x] all work is tracked
• [x] report sprint velocity based on weights
• [x] issues that get closed without any work in the current sprint (previous work, won't do, notabug) should have a weight of 0
• [ ] all closed issues are tagged with `CWF::Type`, and sprints should have a balanced distribution of them
• visibility:
• [x] see planned work for the current sprint: Current Sprint (Scrum) board at https://gitlab.com/groups/cki-project/-/boards/9212206, but needs a proper label filter to exclude unplanned work, and epic-based swimlanes
• [x] see total work for the current sprint
• [x] provide a way to easily move issues of refined/in-progress epics from the backlog into a sprint, in the best case properly aligned with epic-based swimlanes
• [x] automatic duplication of recurring issues into next sprint

GitLab iterations should work, eg by replacing the current label-based approach by automated iteration assignment. Reporting on these in GitLab is pretty bad though, so might need a custom reporter and an Applecrumble dashboard.

GitLab milestones could also be used to replace the current labels for quarterly planning, but eg would be something to check to see whether epic boards with columns per milestone would still be possible.

More ideas:

• have a label with tshirt sizes, that is synced down into weight
• have a label for close status (done/previous/won't do/notabug), that will set the weight to 0 if needed
• use milestones for the quarterly planning

Old ideas:

• when an issue is tagged into the current iteration, make sure it is either closed, or tagged as ~"CWF::Stage::Refined" or ~"CWF::Stage::In Progress"; if not, add ~"CWF::Stage::Refined"; the opposite automation is not desired. Tickets can be ~"CWF::Stage::In Progress" and outside of the current iteration.

Delivery until 2025Q3

1. 1. Relevant material

• https://scrumguides.org/docs/scrumguide/v2020/2020-Scrum-Guide-US.pdf

Jira: CKI-7060