-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add doc on key agile ceremonies | Agile handbook
- Loading branch information
1 parent
cf6c9e7
commit 3aa14c3
Showing
6 changed files
with
95 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
89 changes: 89 additions & 0 deletions
89
src/content/docs/agile-handbook/guide/meetings-and-ceremonies.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,89 @@ | ||
| --- | ||
| title: "Meetings and ceremonies" | ||
| template: basicDoc | ||
| topics: | ||
| - Docs agile handbook | ||
| --- | ||
|
|
||
| <table> | ||
| <thead> | ||
| <tr> | ||
| <th></th> | ||
| <th>Monday</th> | ||
| <th>Tuesday</th> | ||
| <th>Wednesday</th> | ||
| <th>Thursday</th> | ||
| <th>Friday</th> | ||
| </tr> | ||
| </thead> | ||
| <tbody> | ||
| <tr> | ||
| <td>_Week 1_</td> | ||
| <td>Sprint retro | ||
|
|
||
| Backlog grooming | ||
| </td> | ||
| <td>(end of sprint) | ||
|
|
||
| Sprint planning | ||
|
|
||
| (start of new sprint) | ||
| </td> | ||
| <td>Team meeting</td> | ||
| <td></td> | ||
| <td>Meeting-free day</td> | ||
| </tr> | ||
| <tr> | ||
| <td>_Week 2_</td> | ||
| <td></td> | ||
| <td></td> | ||
| <td>Team meeting</td> | ||
| <td></td> | ||
| <td>Meeting-free day</td> | ||
| </tr> | ||
| </tbody> | ||
| </table> | ||
|
|
||
| We break our work into two-week sprints. The new sprint starts on a Tuesday with Sprint Planning, where we commit to a set of stories that we're confident we can complete by the end of the sprint. Near the end of the sprint, we prepare for the next with Backlog Grooming. The sprint closes with a Retro where we discuss what went right and what went wrong, and then we kick off a new Sprint Planning meeting. | ||
|
|
||
| Each squad does their own Backlog Grooming and Sprint Planning, and manages their sprint backlog independently. We alternate between squad-specific retros and team-wide retros every other sprint. | ||
|
|
||
| (Why do we end sprints on Mondays and start Tuesdays? This funny schedule makes things easier to work across timezones. If we ended sprints on Fridays, our Barcelona-based writers would need to do retros and grooming on Friday evening, and who wants that?) | ||
|
|
||
| ## Sprint planning [#sprint_planning] | ||
|
|
||
| On the first Tuesday of a new sprint, we commit to a series of stories until we have filled our capacity for the sprint. This is the largest meeting in the sprint---about 60 to 90 minutes. | ||
|
|
||
| Before the sprint planning meeting, the scrum master for each squad calculates their point budget. Then, during the meeting: | ||
|
|
||
| 1. We select the highest priority item in the backlog, and start a five minute timer. | ||
| 2. The person who nominated the story introduces it, and the team asks questions until everyone feels ready to vote. | ||
| 3. The team plays [planning poker](3379_INSERT_LINK_HERE). Everyone secretly chooses a card, then we reveal them at the same time: | ||
| 1. If everyone picks the same card, that's the point value and we move on. | ||
| 2. If there's an even split between two cards, we choose the larger and move on. | ||
| 3. If it's mixed, the highest and lowest voters briefly explain their votes. Then we vote again. | ||
| 5. Once we're sure we can fit the story in, we subtract its Story Points from the sprint's points budget. | ||
| 6. We repeat the above steps until we've used up our points budget. | ||
| 7. Wrap up and make sure there are no outstanding questions. | ||
|
|
||
| We generally avoid pre-assigning people to stories during sprint planning. Instead, we pick up the next story or peer edit in the To Do column as stories are completed. | ||
|
|
||
| ## Backlog grooming [#backlog_grooming] | ||
|
|
||
| The day before the sprint starts, we do backlog grooming. The purpose of backlog grooming is to prioritize work for sprint planning, and identify stories that need to be fixed before sprint planning to match the [Checklist for story readiness](3379_INSERT_LINK_HERE). In the grooming, we: | ||
|
|
||
| 1. Each writer brings their personal "top five" tickets. | ||
| 2. Work together to prioritize those into a single, stack-ranked list for the team. | ||
| 3. Flag stories that don't look ready for sprint planning, and notify the liaison or requestor so they can improve the story before sprint planning. | ||
| 4. After grooming, the scrum master sends out a list of "homework" to everyone via #doc_talk. For example: | ||
|
|
||
| ## Retro [#retro] | ||
|
|
||
| At the end of the sprint, we conduct a 60 minute Retrospective meeting, where we discuss: | ||
|
|
||
| - How do we feel about the sprint? | ||
| - What went well? | ||
| - Where can we improve? | ||
| - Anything we should start or stop doing? | ||
|
|
||
| The goal of the Retro is to improve the way we work together. That could be related to the sprint process, to how we collaborate with SMEs, to peer edits, and so on. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters