Scheduling
The following scheduling settings are available for configuration in your plan:
Sample scheduling settings in a plan
Estimation
You can choose which unit to use when estimating issues in your plan.
| Days |
|
| Hours | |
| Story points |
|
The estimation unit that you choose for your plan impacts the types of teams that you can create in your plan.
- If you're using days or hours (time-based estimation), you can create both Scrum and Kanban teams in your plan.
- For Scrum and Kanban teams, the default capacity is set to 200 weekly hours.
- For Scrum teams, the default iteration length is set to 2 weeks.
- If you're using story points, you can only create Scrum teams in your plan. The default team velocity is set to 30 story points, and the default iteration length is set to 2 weeks.
See Creating teams for more details.
Dependencies
Regardless of the estimation unit being used in the plan, you can choose how dependent issues can be scheduled.
| Scheduling behavior | Description |
| Sequential | Dependent issues cannot be worked on at the same time, whether the issues are manually scheduled or auto-scheduled. |
| Concurrent | Dependent issues can be worked on at the same time, whether the issues are manually scheduled or auto-scheduled. |
For example, you have the following in your plan:
- You have dependent stories TIS-1 and TIS-2, with TIS-1 blocking TIS-2.
- You have Sprint 1 as the immediate sprint in your plan, and Sprint 2 and Sprint 3 following it.
- Both issues have the same target start and end dates.
- Both issues are estimated at 30 story points.
- Both issues are assigned to the same team, and team velocity is at 30 story points.
- Both issues are not currently assigned to any sprint.
While the issues have no assigned sprint, the badges will turn red. This is because the dependent issues have the same target dates, which is not a realistic schedule because TIS-1 is blocking TIS-2. Thus, the badges will turn red.
Last modified on Jul 28, 2019
Powered by Confluence and Scroll Viewport.