Commit 505d9055 authored by Dominique Barton's avatar Dominique Barton 🦄
Browse files

DOC: Update ScrumC guidelines

parent 4e6cb6e5
Pipeline #10236 passed with stage
in 33 seconds
This diff is collapsed.
......@@ -17,8 +17,8 @@ ScrumC Guidelines
- **Meeting lead** has ``dbarton``, with ``rbrem`` as backup
- The meeting lead is responsible for the **calendar invitations**
- The meetings have a hard **time boxing**
- **PO's** are ``dbarton`` & ``rbrem``
- We've no dedicated **SM's**
- We've no **PO's**, but we've **TL's**
- Language is always **English**
.. _Scrum DoR:
......@@ -27,7 +27,7 @@ Definition of Ready (DoR)
-------------------------
- The PBI is written as **formal US** (i.e. *"As a {kind of user} I want {feature} so that {benefit}"*)
- The **Business value** is clearly articulated
- The **business value** is clearly articulated
- The PBI is **understood by the team**
- **AC's are sufficiently defined** and understood by the team
- **Dependencies** are identified
......@@ -62,33 +62,30 @@ ScrumC Meetings
Review
~~~~~~
The review meeting takes 30 minutes, bi-weekly on Mondays **from 10:30 until 11:00**.
The review meeting takes 30 minutes, bi-weekly on Mondays **from 13:00 until 13:30**.
The goals are:
- Look back on the last sprint
- Identify what we **achieved**
- **Demonstrate** everything in front of the team
Basically check out the ``to review`` issues.
- **Update** the team on ongoing US'
- **Demonstrate** finished US' to the team
- **Close** finished & demonstrated US'
.. important::
For the review meeting, **US' must've been reviewed by a second party**.
This can happen either during the sprint, or on the Monday morning right before the review
meeting, as the sprint is finished on the Sunday before. This ensures a streamlined review
meeting.
This can happen either during the sprint, or on the Monday morning right before the review meeting.
Retrospective
~~~~~~~~~~~~~
The retrospective meeting takes 30 minutes, bi-weekly on Mondays **from 11:00 until 11:30**.
The retrospective meeting takes 30 minutes, bi-weekly on Mondays **from 13:30 until 14:00**.
The goals are:
- Look back on the last sprint
- Identify **unplanned** US' and find out why we've had them and if/how we can avoid them in the future
- Identify **spill over** US' and find out why we've them and how we can avoid them in the future
- Identify **impediments** and find out how we can avoid them in the future
- Talk about any other **improvements** for future sprints
- Identify **unplanned** US' and find out why we've had them and how we can avoid them
- Identify **spill over** US' and find out why we've them and how we can avoid them
- Identify **impediments** and find out how we can avoid them
In this meeting, all US' of the sprint will be updated accordingly. This means:
......@@ -97,44 +94,55 @@ In this meeting, all US' of the sprint will be updated accordingly. This means:
- **Touched (i.e. in progress) spill over** US' will be closed and new US' with the incomplete tasks will be created in the PB or next SB
- The **SB** is moved to the next sprint
Entitlement
~~~~~~~~~~~
.. important::
Apart from the typical Scrum retrospective, we also do a **team retrospective**.
Everyone should answer the following 2 questions:
1. Are there any **highlights**?
2. Are there any potential **improvements**?
The entitlement meeting takes 30 minutes, bi-weekly on Mondays **from 13:30 until 14:00**.
All team members can write answers to these questions on Post-it's, then we will cluster them and discuss them in the team.
Refinement
~~~~~~~~~~
The refinement meeting takes 30 minutes, bi-weekly on Mondays **from 14:30 until 15:00**.
The goals are:
- Look ahead on the next sprint
- Identify **urgent topics** for the organisation (big picture) by skimming through the SB
- An **collective agreement** is made for the direction / priorities of the next sprint (big picture)
- Identify **objectives** & **goals** which need to have resources assigned in the next sprint
- Find, write and **refine** the required US' for the next sprint
- Make sure US' are ready according our :ref:`DoR <scrum dor>`
Basically check out the next SB and identify the most important US'.
Basically prepare the next SB and identify the most important US'.
.. important::
This is usually done by the **PO's**.
However, **goal & objective leaders** can/should/must also pro-actively attend to this meeting if they need resources in the next sprint.
Planning
~~~~~~~~
The planning meeting takes 30 minutes, bi-weekly on Mondays **from 14:00 until 14:30**.
The planning meeting takes 30 minutes, bi-weekly on Mondays **from 15:00 until 15:30**.
The goals are:
- The planning of the next sprint
- The planning is made according to the **priorities of the entitlement** meeting
- The planning is made according to the **priorities of the refinement** meeting
- US' are planned into the sprint until the team's **capacity is reached**
- Each planned US must be moved from the SB into the **to do** state
- Each planned US must be **assigned** to a user
Basically just assign & move some US from the PB & SB into the **to do** swimlane.
.. important::
For the **entitlement/planning meeting, US' should be prepared as far as possible**, i.e. mostly matching the :ref:`DoR <scrum dor>`. This ensures streamlined entitlement/planning
meetings.
Basically just assign & move some US' from the SB into the **to do** swimlane.
ScrumC GitLab issues
--------------------
- Epic's are maintained as GitLab issues and are labeled with the ``ScrumC epic`` label
- US' are maintained as GitLab issues and are labeled with the ``ScrumC US`` label
- US' ready for planning are labeled with ``ScrumC ready``
- US' which were unplanned but worked on during a Sprint are labeled with ``ScrumC unplanned``
- Epic's are maintained as GitLab issues and are labelled with the ``ScrumC epic`` label
- US' are maintained as GitLab issues and are labelled with the ``ScrumC US`` label
- US' ready for planning are labelled with ``ScrumC ready``
- US' which were unplanned but worked on during a Sprint are labelled with ``ScrumC unplanned``
ScrumC Terms
------------
......@@ -158,5 +166,7 @@ ScrumC Terms
+----------------------+-----+
| Scrum Master | SM |
+----------------------+-----+
| Topic Lead | TL |
| Objective Lead | OL |
+----------------------+-----+
| Goal Lead | GL |
+----------------------+-----+
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment