From 82fcb4d5b06347b5c5e4f664b2529cd034aefc79 Mon Sep 17 00:00:00 2001 From: Jeff Gehlbach Date: Fri, 7 Jun 2024 17:35:32 -0400 Subject: [PATCH] Added Development-Cycle page --- Development-Cycle.md | 55 ++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 55 insertions(+) create mode 100644 Development-Cycle.md diff --git a/Development-Cycle.md b/Development-Cycle.md new file mode 100644 index 0000000..36b7c2a --- /dev/null +++ b/Development-Cycle.md @@ -0,0 +1,55 @@ +This page describes the mechanics of a NetBox development cycle. +It is a work in progress and always will be. + +# Ceremonies +The core team meets in a daily standup. Whenever possible, the following ceremonies are fit into that 30-minute slot. + +## Main Standup +Each team member answers three questions: +- What did I work on previously? +- What will I work on today? +- Is anything blocking my work? + +## Backlog Review +On the first day of a new cycle, the team conducts a backlog review. +The purpose of this ceremony is to select issues from the cycle backlog for work during the new cycle. + +Each issue in the cycle backlog goes through a process that subjects it to one of four fates: +- Remain in the cycle backlog +- Regress from cycle backlog to product backlog +- Assign and promote to Todo +- Break down into smaller issues + +In chart form: +```mermaid +flowchart TD + A[🎬 + Start] -->B{✋ + Any Takers?} + B -->|Yes| D{🤔 + Achievable + in 1 Cycle?} + B -->|No| E{🤔 + Still a Fit + for Milestone?} + E -->|Yes| H[🏁 + Keep in + Cycle Backlog] + E -->|No| I[🏁 + Remove to + Product Backlog] + D -->|Yes| J[🧑‍💻 + Assign] + J --> F[🏁 + Promote to Todo] + D -->|No| G[🧩 + Break Down + into Smaller Issues] + G -->B +``` + +## Retrospective +At the end of a cycle, the team may opt to hold a lightweight retrospective in which the team collaboratively answers the following: +- What worked well this cycle? +- What could have worked better? +- What should we change going forward?