Scale: Time Period and Aggregation

This functionality will help you set the right time frame and data aggregation. Depending on what you do and how you account for the time, you can set different aggregation types. For example, if a project has a due date and your team members work overtime to deliver it on time, you will see a capacity overload from a weekly perspective. Still, there will be no capacity overload visible from the monthly perspective. Also, you can customize the colors and aggregations to see as much data as you need, even from the semiannual perspective.

Time Period

Use the arrows in the App's header to move to the previous or next period. Adjust the scale to fit more tasks into the current view.

There are four views available:

Week

Month

Quarter

Half a Year

Aggregation

You can change the way data is aggregated. Set aggregation based on:

• Daily, weekly, or monthly intervals
• Sequential sub-Boxes (timeboxes)

Information about the aggregation time period is listed in the workload details dialog.

Daily

Weekly

Monthly

By timeboxes

When data is aggregated by timeboxes, it is easier to plan tasks for individuals in iterations, increments, etc.

• Timebox aggregation is a sum of daily aggregations.
• Aggregation is based on the length of the chosen period.

Turn on the aggregation

Method 1:

Go to scale > select aggregation by timeboxes:

Method 2:

Click on a timebox (in the header row) to activate the aggregation. 

Conditions:

Before you set aggregation by timeboxes, select the Timeboxes in the View menu.

Limitations

If box periods overlap, aggregation by timeboxes is NOT available.

Timeboxes don't exist in a given time period

If there are no timeboxes for a given time period, the "No timeboxes in this period" message appears.

• For the time between defined timeboxes, data is aggregated based on the length of that period, e.g. if time slot between periods is nine days, data from nine days will be aggregated.
• Aggregation before and after defined time periods are based on the corner time periods, e.g. if in the project lasting two years there were two weeks sprints at the beginning of the project and 1 week sprint at the end of the project the aggregation will be visualized:
  • as 2 week periods before the project starts
  • as 1 week periods after the project ends

Navigation options