diff --git a/Development-Cycle.md b/Development-Cycle.md index e41f622..b0d1f0e 100644 --- a/Development-Cycle.md +++ b/Development-Cycle.md @@ -37,6 +37,11 @@ Each team member answers three questions: - What will I work on today? - Is anything blocking my work on an assigned issue? +### Bug Blitzes +Bug blitzes are periods during which the team suspends all planned feature work to focus exclusively on bugs. + +The team may declare a bug blitz any time the count of [open issues with a severity assessed](https://github.com/netbox-community/netbox/issues?q=is%3Aissue+is%3Aopen+label%3A%22type%3A+bug%22+label%3A%22severity%3A+low%22%2C%22severity%3A+medium%22%2C%22severity%3A+high%22) exceeds 50. The blitz ends when that figure drops to 40. + ## Cycle Backlog Refinement – Last day of every other cycle, as needed The product manager and the developers refine the issues in the Product Backlog so that they make progress toward the Cycle Backlog. @@ -45,7 +50,7 @@ Starting at the top of the Product Backlog, the team selects issues that they co - Which category fits the issue? - What should be the issue's priority? - Does the issue have a _Milestone_ that matches its _Target Release_? If not, make it so. -- Set the issue's _Status_ to _Backlog_ +- Set the issue's _Status_ property in the project to _Backlog_ ## Cycle Planning – First day of every cycle The product manager and the developers review the cycle backlog, selecting issues from the _Backlog_ column for work during the new cycle, confirming their readiness, and ideally moving them to the _Todo_ column. @@ -56,13 +61,15 @@ Each issue in the cycle backlog goes through a process that subjects it to one o - Assign and promote to Todo - Break down into smaller issues -In chart form (`TODO`: Add a bit more granularity upstream of _Any Takers?_): +In chart form: ```mermaid flowchart TD A[🎬 - Start] -->B{βœ‹ - Any Takers?} - B -->|Yes| D{πŸ€” + Start] -->B[🎟️ + Backlog Column] + B -->C{βœ‹ + Any Takers?} + C -->|Yes| D{πŸ€” Achievable in 1 Cycle?} B -->|No| E{πŸ€”