s/Cycle Backlog Review/Cycle Planning/

Jeff Gehlbach 2024-06-18 10:40:46 -04:00
parent ba57fb7f3c
commit 30b604695a

@ -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. - 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_ to _Backlog_
## Cycle Backlog Review  First day of every cycle ## Cycle Planning  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. 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: Each issue in the cycle backlog goes through a process that subjects it to one of four fates:
- Remain in the cycle backlog - Remain in the cycle backlog