Wikimedia Apps/Team/Android/Development Cycle
The Android team recently moved away from Scrum towards Kanban to manage their development process.
Rituals
editName | Frequency | Duration | Description | Goals | Resources | Attendees | Notes |
---|---|---|---|---|---|---|---|
Iteration Review/Kickoff | Biweekly on Monday | 25 min | Team meets to review the last two weeks of development and clarifies goals for the next two weeks of work. |
|
|
||
Story Prioritization (Planning) | Biweekly on Monday | 50 min | Team meets to plan the coming two week's work. Planning involves reviewing and estimating stories on the kanban board. |
|
|
||
Retrospective | Weekly on Monday | 50 min | Team meets to discuss topics proposed by team members, mostly process-related. |
|
|
||
Combined Apps Standup | Weekly on Monday | 15 min | Apps teams, Android and iOS, meet to exchange quick status updates.
Everyone but Facilitator answers three questions:
After giving their update, each person chooses who goes next by saying the other person's name. |
|
|
||
Standup | Weekly on Wednesday and Friday | 15 min | Team meets to exchange quick status updates.
Everyone but Facilitator answers three questions:
After giving their update, each person chooses who goes next by saying the other person's name. |
|
|
||
Grooming and Triage | Weekly on Wednesday | 25 min | Team meets to either clean up the kanban board or triage tasks in the backlog. |
|
|
Optional |