Iterations (Sprints) and Team Iterations
There are two types of Iterations: Iterations (Project Iterations, Sprints, Project Sprints) and Team Iterations (Team Sprints). Both are planning Entities. They represent a short time during which planned work needs to be completed.
Iterations and Team Iterations help you in organizing work for planning, tracking, and reporting. The main difference between them is the scope of work each contains.
An Iteration is a part of a Project and Release by default. It can contain
work only from one Project and a single project Release. Take a look at an example of a sprint
planning board. 
Team Iterations are similar to Iterations, but are not related to a
Project. A Team Iteration is related to a Team and can contain work from many different Projects and
Releases.
| Iteration (Sprint) | Team Iteration (Team Sprint) | |
|---|---|---|
| Contain stories, tasks,and bugs assigned to | one project | many projects |
| Contain stories, tasks, and bugs assigned to | many teams | one team |
| Contain stories, tasks, and bugs assigned to | one release, always | many release |
| Belongs to parent Release | one release assigned to one project only, always | one release, can be assigned to many projects |
| Belongs to parent Project | one project, always | never |
| Belongs to parent Team | never | one team, always |
Effort Units
The total assigned effort and velocity of Iterations and Team Iterations are measured using a single planning unit (points or ideal hours) across all assigned entities (work items).
For iterations, you can define the effort unit in the process settings of the project to which the iteration belongs.
For Team Iterations, the Default Process settings marked in your global settings (Settings → Processes) override the effort unit.
Assign Features, Epics, and Releases
Starting Targetprocess version 3.13.0, you can link a Feature to a Team Iteration in the same way a User Story, Bug, or Test Plan Run can. It’s possible to set Team Iteration for Features either manually or to calculate as the Team Iteration of the latest User Story in the Feature. So you can plan Features by Team Iteration then build views with Features cards and Team Iterations as an axis, etc.
Iterations cannot contain Features and Epics. However, the sprint and release planning software allows Iterations to contain Stories, Tasks, and Bugs that are part of Features and Epics.
Iterations cannot be assigned to cross-project Releases.
Filters for Sprints and Team Iterations
In Targetprocess sprint iteration planning tool, you can select, hide or highlight data in views and visual reports by Sprints (Iterations) or Team Iterations and related properties using Advanced Filters for Sprints and Team Iterations. For more information, see Advanced Filters for Sprints (Iterations) and Team Iterations.
Team Iterations and Releases
If multiple-related projects run together, you can coordinate them with cross-project Releases. When a team is working on many projects at the same time, you can plan and organize the team’s work with cross-project Team Iterations. Team Iterations are not directly connected to Releases and cannot be assigned to them. However, it is still possible to link Team Iterations with Releases. For more information, see How to link Team Iterations and Releases.
Reports
Sprint planning is an essential factor in the success of any agile project. Your team’s agility depends on your tactical and strategic approach to sprint iteration planning. With Targetprocess sprint and release planning software, you gain full visibility into a project’s progress and facilitate both communication and accountability within your company. You can create clear and intuitive sprint planning boards to share with your entire team in a matter of minutes.