Why use Release in TFS Iteration tree [closed]

Question

Closed. This question is opinion-based. It is not currently accepting answers.

---

Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.

Closed 4 years ago.

Improve this question

We are doing a lot of maintenance work for previous versions of the product that we are developing and it feels stupid to have the release in the iteration path. Even if we wouldn't do any maintenance work, it feels unnecessary to have the release in the iteration path so can someone explain me the reason why it is there by default? Is there a caveat on removing the release level from the tree?

What I would suggest is to have it like this? Does this make sense? We would only have sprints after another and the release is not related to them.

• Root
  • Sprint 1
  • Sprint 2
  • ...

How would you structure the iteration tree in a project where you do a lot of maintenance work for previous versions?

Answer 1

If you don't wish to use a Release layer in your Iteration hierarchy you're free to remove it, and everything will still work fine.

Most teams don't release every Sprint, so in practice several sprints make up a single release, and people like to track this information using the Iteration Hierarchy. They can then use it for reporting, to do things like "show me all PBI's included in Release 3".