Conclusion

Factors for decision-making

1. Does a feature-level estimation process already exist, and have teams been trained on the process?
2. Does a story-level estimation process already exist, and have teams been trained on the process?
3. How is team member allocation managed across teams, and who is accountable for it?
4. Are people on the program allocated across multiple teams, and are they properly allocated across each team in Jira Align?
5. Does program leadership want to track progress by story points or by task hours at the team level?
6. Do teams use sub-tasks to track work even if the program is measuring by story points?
7. How much time does each team member spend a day on actual development (e.g. burn hours in Jira Align)?
8. Does the program plan to track and allocate capacity to defects in Jira Align?
9. Does the program want to measure capacity and availability of specific skills?
10. Have teams been executing long enough to have a stable story point velocity?
11. Does the program plan to 100% capacity or leave room for emergent work (e.g. bugs, innovation)?

References

• Program and Solution Backlogs - Scaled Agile Framework
• Plan capacity for forecasting
• Capacity planning
• Estimation methods overview
• Configure estimation settings

Congratulations!