Track how your team is doing with its projects. Team measurement reports include:
Cycle Time chart
The Cycle Time chart (also known as the Lead Time chart) helps you use past history to estimate how long it might take for work to pass through various Rally schedule states to acceptance.
This chart displays the average number of days it takes work to flow through your process to acceptance for each week, and a metrics summary (in days) over the past 12 months.
Use this chart to detect trends and consider questions like:
- How long does it take, on average, for a work item to pass from an idea to completion?
- Once completed, how long does it take to accept a work item?
- What is the nature of outliers?
- How many stories or defects of similar size should we be able to accept in a given time period?
How is this chart calculated?
The average time it takes the work items measured from the time they cross the boundary to the left of the start state (specified in the report request), to the time they cross the boundary to the left of the end state (specified at report run time). The x-axis INTERVAL and INTERVALS_BACK parameters (available on the dashboard UI) are one factor that determines which work items are included in the report. A work item must have crossed the end state boundary in the timeframe for that point on the chart in order to be included in that point. The summary metrics include data in all the points.
Does the chart pull the first or last time a state is set to the selected value?
For example, a defect is marked In-Progress, then handed off by a team and placed back in Defined. The new team later sets it back to In-Progress. Where does the clock start? The clock restarts once it crosses the boundary the second time. It is measured from the last time that it crosses the first boundary to the last time it crosses the second boundary.
- The start schedule state (any value other than the custom final schedule state) and the begin date of the chart (default is 12 months back) determine when you begin the clock for the average calculation.
- The final schedule state (Accepted or the final custom schedule state) and the end date of the chart (default is the previous complete month) determine when you stop the clock for the average calculation.
- Work items are only included in the chart if they are set to the final schedule state (Accepted or custom value after accepted) within the time period specified by the report.
- In order to display a period of time on the chart, the period of time must have completed. If the chart is showing weekly data, the current week must complete before it will appear on the chart. This creates a lag in the chart to produce like measurements across similar time periods.
- If a work item crosses both boundaries at the same time, it is included, but its lead time is zero. The Throughput and Cycle/Lead Time charts are not using different data; rather, the work item displays as non-zero on the Throughput chart but zero on the Cycle/Lead Time chart.
- If you run the Kanban board, the chart processes non-null values in the field you use to organize in your Kanban board. This FILTER_FIELD parameter is not exposed in the dashboard version at this time, and is only available from the Kanban board.
The Throughput chart helps you use past history to predict how much work your teams may accept in a similar time period.
The chart displays the number of work items that your teams have accepted over the past 12 months and a metrics summary (number of work items) over the reporting period. Note that if you would like to set a custom date range, you will need to add the Throughput app.
If defects are displayed on the chart, both defects associated to user stories and standalone defects that have been accepted will be included. However, if a defect is associated to an accepted user story, but the defect itself is not accepted, it will not be counted.
The chart helps you detect trends and consider questions like:
- How many work items of similar size should we be able to accept in a similar, future time period?
- What factors might affect throughput?
My Availability chart
The My Availability chart reflects your personal capacity levels across all projects for the current iteration in the workspace. This chart displays all current iterations for all projects in which you have tasks assigned or are a team member. Use this chart to track your available individual resources, view your cumulative task estimate assignments, and view or set your individual capacity per project for the current iteration. This information enables you to predict your ability to meet your commitments for the current iteration.
Click any column for a description.
The My Availability chart displays:
- A list of all projects contained within the current iteration.
Each project name is hyperlinked to the project's detail page. Click the project header to sort the list alphabetically in ascending or descending order.
- The current iteration name for each listed project.
Click on the iteration name to access the Iteration Detail page. Click the column heading to sort your display by iteration name.
- A color-coded, individual load box that displays an at-a-glance indication of the percentage of stated individual capacity taken up by tasks assigned to you.
Green indicates your individual load is within an acceptable range, while red indicates your individual load exceeds your capacity. Your individual load percentages are rolled up for all projects and reflected at the top of the column.
- Your capacity for each project.
This information reflects your availability per project for the current iteration and is rolled up for a total workspace wide calculation and displayed at the top of the column. You can set or adjust your capacity at any time by clicking the edit icon.
- Task estimates for all tasks per project within the current iteration that have been assigned to you.
These figures are rolled up for a total workspace-wide calculation and displayed at the top of the column.
If a project has no current iterations defined, My Availability chart displays the following message There are no current iterations on the project line.