Commit bbcff45b authored by Dominique Barton's avatar Dominique Barton 🦄
Browse files

DOC: Add new ScrumC meeting guidelines

See also #17 & #18
parent 505d9055
Pipeline #10327 passed with stage
in 27 seconds
......@@ -5,7 +5,7 @@ What is ScrumC
``ScrumC`` is confirm-flavoured `Scrum <>`_.
It's basically Scrum, but our `oDNA <>`_ and the topic leads also play an important role.
It's basically Scrum, but our goals & objectives also play an important role.
ScrumC Guidelines
......@@ -13,7 +13,9 @@ ScrumC Guidelines
- We're maintaining a **Scrum light** approach rather than an *all-in* approach
- We maintain our PB, epics & US in **GitLab issues**
- Our **sprint length** is 2 weeks
- Our meetings will be held **bi-weekly** on **Mondays**
- There's are short **dialy meetings**
- There are longer meetings will be held **bi-weekly** on **Mondays**
- All employees must be **present in the office**
- **Meeting lead** has ``dbarton``, with ``rbrem`` as backup
- The meeting lead is responsible for the **calendar invitations**
- The meetings have a hard **time boxing**
......@@ -21,6 +23,10 @@ ScrumC Guidelines
- We've no dedicated **SM's**
- Language is always **English**
.. important::
When the *Meeting-Monday* is a holiday or alike, the meetings will be postponed to the next workday.
.. _Scrum DoR:
Definition of Ready (DoR)
......@@ -59,6 +65,19 @@ We're using the following ScrumC workflow:
ScrumC Meetings
The daily meetings take 15 minutes **from 09:45 until 10:00**.
Each team member will answer the following questions in front of the team:
- What did I **plan for today**?
- Did I had any **issues yesterday** with the planned tasks?
- Am I **blocked** or are there any **impediments**?
- Do I need **any help** from anybody?
- Do I have **enough US'** for the rest of the Sprint?
- Do I have any **absences** within the next week?
......@@ -74,7 +93,11 @@ The goals are:
.. 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.
This must happen during the sprint and the **assignee is responsible** to get the review done.
.. important::
If there's an absence of a team member, **the team member (aka assignee) must refer his/her US' to a representative**.
......@@ -97,12 +120,12 @@ In this meeting, all US' of the sprint will be updated accordingly. This means:
.. important::
Apart from the typical Scrum retrospective, we also do a **team retrospective**.
Everyone should answer the following 2 questions:
Everyone must **come prepared** with Post-it's which answer the following 2 questions:
1. Are there any **highlights**?
2. Are there any potential **improvements**?
All team members can write answers to these questions on Post-it's, then we will cluster them and discuss them in the team.
There should be 1 Post-it per question and during the meeting, we'll do a clustering and discuss them.
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