Add use cases to Iterations docs
The following discussion from !31335 (merged) should be addressed:
-
@gweaver commented on a discussion: (+5 comments) @msedlakjakubowski @psimyn do you think it is important to describe how it behaves AND the use cases it solves for teams?
I've gotten lots of feedback from users that our documentation on how our product works is great, but we have a lot of room to improve on documenting how to use our product to accomplish common use cases.
For example, we are adding iterations to the product so that we can then calculate velocity and volatility metrics for teams.
Beyond
☝ , adding iterations allows teams to track issues across both:- Milestones for Program Increments which span 8-12 weeks
- Iterations for Sprints, which are typically ~2 weeks.
It's also worth noting on the differences (similar to date range can't overlap but said in a slightly different way):
- You can only have one active iteration at a time within a given group.
This is one step towards working towards these user needs - &69