Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: 📝 update iteration.qmd #227

Merged
merged 6 commits into from
Mar 4, 2025
Merged

docs: 📝 update iteration.qmd #227

Changes from 5 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
f3858c1
docs: :fire: remove assign timekeeper from agendas
signekb Mar 4, 2025
73abb6a
docs: :memo: add description of what we do during a retrospective
signekb Mar 4, 2025
ca8a98a
docs: :adhesive_bandage: update current iteration durations (one month)
signekb Mar 4, 2025
4193f3f
docs: :memo: add that we have multiple aims and usually one per person
signekb Mar 4, 2025
3a077fb
docs: :memo: update expected duration of debrief and retrospective
signekb Mar 4, 2025
effd427
docs: :pencil2: suggestions from review
lwjohnst86 Mar 4, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 14 additions & 6 deletions how-we-work/iteration.qmd
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,10 @@ Team lead sets everything up for the next two or three iterations.
iterations a few days before major holidays start.
- Will plan and decide on how long the future iterations should be
(can range from 2-6 weeks, but prefer shorter iterations over longer
ones). So far, we find that 3 week iterations work the best.
ones). Currently, we find iterations with a duration of one month
work the best for us. This way, we have the planning meeting at the
beginning of the month and the debrief and retrospective meeting at
the end of the month.

## Start of iteration

Expand All @@ -69,11 +72,14 @@ specifics of the iteration.
::: callout-note
A basic agenda for the meeting might be:

- Assign a timekeeper.
- Review and agree on the iteration aim and end date.
- Review and agree on the iteration aims and end date.
- Review the list of tasks already listed.
- Brainstorm and add any other issues as needed.
- Schedule the next iteration's end and start meetings.

We usually have separate aims for each person in the team, and each of
us will add tasks to the board relevant to that aim aim as needed. This
usually happens as the iteration progresses.
:::

::: panel-tabset
Expand Down Expand Up @@ -104,7 +110,7 @@ the iteration as well as the distribution of priority labels of the
tasks.

Then, we agree on and schedule the end date debrief and retrospective
meeting, which should be approximately 2-3 hours and preferably before
meeting, which should be approximately 1-2 hours and preferably before
lunch, as well as the next iterations planning meeting. The next
planning meeting should either be on the same date after lunch, to
ensure a proper break before moving to a new iteration, or the next day
Expand All @@ -131,12 +137,14 @@ during the planning meeting.
::: callout-note
A basic agenda is:

- Assign timekeeper.
- Demo (internally or externally) the progress of the iteration.
- Evaluate the iteration aim.
- Go over what we accomplished and how we felt we did (including
struggles).
- Do a retrospective.
- Do a retrospective reflecting on what we each think we should keep
doing and what we should stop doing or improve on. Afterwards, we'll
group the notes into topics and add action items to each of the
topics.
:::

During the debrief and retrospective meeting, we will:
Expand Down