This page is maintained for older versions of Spira only. The latest documentation can be found at: https://spiradoc.inflectra.com

SpiraTest Administration Guide Help Viewer

1. Introduction
2. Installing SpiraTeam®
3. System Administration
4. Appendices
Search:
1. Introduction
2. Installing SpiraTeam®
3. System Administration
4. Appendices

3.1.3. Planning Options

This screen is available for installations of SpiraPlan® and SpiraTeam® only (not SpiraTest®) and allows you to configure the schedule and calendar options for the various project estimation and planning modules. The settings are specific to each project:

This page allows you to make changes to the following settings:

  • Work Hours Per Day – this setting allow you to specify how many work hours should be used when converting an effort calculation from hours to calendar days. For example a 12 hour task will occupy two days if you set the working hours per day to 6 hours, whereas the same task will occupy 1 ½ days only if you set the working hours per day to 8 hours.
  • Work Days Per Week – this setting allows you to specify how many days in the week are typically worked on the project. By default the system assumes a 5-day (Mon-Fri) working week, but if your organization works Saturdays (for example), you may want to switch to a 6-day working week. If you want to use partial days, then just round up to the nearest day and add non-working hours (see below) to compensate.
  • Non-Working Hours Per Month – this setting allows to specify how many non-working hours typically need to be accounted for. This is useful if you want to have a working week that contains a fractional number of days or if you have recurring activities that need to be removed from each month. Note that if you have specific holidays, vacation days that need to be accounted for, it is better to use the Release/Iteration non-working time feature instead.
  • Effort Calculations – When calculating how much effort has been scheduled in a release or iteration, the system will aggregate the individual effort values (both estimated and actual) for all the task and incident artifacts associated with the release/iteration. This setting allows you to specify if you want only task or incident effort values to be included in the release/iteration total. This is useful if your project management methodology requires that incident effort values be excluded from the total.
  • Time Tracking – SpiraTeam® has an integrated time tracking system that allows the easy entry of the hours spent on all assigned incidents and tasks in one place (see the SpiraTeam User Manual for more details on this feature). This setting allows administrators to specify if they want the integrated time tracking features enabled for both incidents or tasks (or neither).
  • Default Effort – Normally when you create a new Requirement or Task in the system it will be given an empty initial estimated effort. However if many requirements or tasks are typically based on a standard size, then as a time-saver, the system will let you specify a default estimated effort that will be used when a new requirement or task is created.
  • Auto-Create Tasks – When you change the status of a Requirement in the system to “In-Progress” the system will automatically add a default Task to that requirement if no tasks already exist. This is a useful shortcut that makes planning with requirements easier in the case when the requirements are of a size where they don’t need to be formally decomposed into multiple developer tasks. However if you don’t want the system to automatically create tasks in, you can deselect the option for the current project and it will turn off the feature.