Make number of FF tickets and hour allocations configurable [BB-6396]
Story
"As a sprint manager, I want to be able to configure the number of FF tickets that are generated for my cell so that I don't have to create additional tickets (or archive superfluous ones) manually."
"As a sprint manager, I want to be able to configure hour allocations for FF tickets for my cell so that I don't need to update them every sprint."
Full description
Configuring number of FF tickets
For full context see this forum thread.
We are looking to increase the number of FFs per sprint for generalist cells (or, more generally, we are looking to move to a more flexible firefighting model that allows cells to adjust the number of firefighters based on fluctuating factors such as cell size, time zone coverage, and average number of firefighting hours needed per sprint.)
To support this through automation we'll need sprint managers to be able to specify the number of firefighting tickets to create each sprint, as they would otherwise have to manually create additional tickets (if the number of tickets created by default is lower than the number of tickets needed), or archive superfluous ones (if the number of tickets created by default is higher than the number of tickets needed).
Configuring hour allocations
See this comment:
I almost forgot to mention: while you are covering for me you'll need to reduce the FF ticket estimates to 6h for FF1 and 4h for FF2 (Crafty will schedule two 15h tickets).
Depending on cell size, the number of hours to pre-allocate for FF work might differ from the current default of 15h (another example).
This creates manual work for sprint managers (or FFs themselves); they'll need to adjust hour allocations on FF tickets each sprint to match cell-specific targets.
We should find a way to allow sprint managers to set custom defaults for their cell.
Completion criteria
- Sprint Managers are able to customize (for their cell):
- The default number of FF tickets that will be created for each sprint.
- The default number of hours that will be allocated to FF tickets each sprint.
- Relevant section(s) of the handbook mention this functionality.
- Create PRs as necessary.
- Deploy changes.
Documentation updates & improvements criteria
- See above. The handbook should describe how to set cell-specific defaults for FF tickets and corresponding hours -- or link to parts of SprintCraft's own documentation that describe the process.