Definitions: Release, Sprint, Backlog
A release is any top-level item in a release-type tracker. By default, each project has one such tracker, but you can add any number of them later. A release may or may not have children.
A sprint is any non-top-level item in a release-type tracker. In most situations, you will only use two levels: topmost for tracking releases and their children to track sprints. You can nest sprints in random depths if two levels do not support your processes correctly. The term subversion is used interchangeably for these items. There is no real difference between the two. In this aspect, the agile world breaks a release into sprints, while other methods break them into sub-releases.
Sprint (or subversion) is any non-top-level item in a Release type tracker. In simplest case, you only use two levels: topmost for tracking releases, and their children to track sprints. You can nest sprints in arbitrary depth if two levels are not supporting your processes correctly. We also use the term subversion interchangeably for these items. There is no real difference between the two. In this aspects, the agile world breaks a release into sprints, while other methods break them into subreleases.
A backlog is the
ordered list of open work items that need to be done.There are multiple types of backlogs:
• Project Backlog comprises the open work items that are not assigned to any release or sprint. Therefore, their Target field is left blank.• Project Backlog comprises the open work items that are not assigned to any release or sprint. Therefore, their Target field is left blank.
• Release Backlog comprises the open work items assigned to a release, not a sprint.
• Sprint Backlog comprises the open work items assigned to a sprint but have not been done yet.