From 30b604695a41e0d1724f5ee29475f9a7c0a5a624 Mon Sep 17 00:00:00 2001 From: Jeff Gehlbach Date: Tue, 18 Jun 2024 10:40:46 -0400 Subject: [PATCH] s/Cycle Backlog Review/Cycle Planning/ --- Development-Cycle.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Development-Cycle.md b/Development-Cycle.md index fbc5cf4..e41f622 100644 --- a/Development-Cycle.md +++ b/Development-Cycle.md @@ -47,8 +47,8 @@ Starting at the top of the Product Backlog, the team selects issues that they co - Does the issue have a _Milestone_ that matches its _Target Release_? If not, make it so. - Set the issue's _Status_ to _Backlog_ -## Cycle Backlog Review – First day of every cycle -The product manager and the developers review the cycle backlog, selecting issues from the cycle backlog for work during the new cycle. +## 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. Each issue in the cycle backlog goes through a process that subjects it to one of four fates: - Remain in the cycle backlog