Member and Team Trend Reports

Member and team trend reports show changes over time in key metrics including active members, workload distribution, estimates, effort, and test progression. Use these reports to identify patterns, forecast capacity needs, and make data-driven resource allocation decisions.

Understanding Trend Reports

Trend reports visualize how metrics change over time using line charts, bar charts, and stacked area charts. They help teams and leadership:

• Forecast future capacity needs based on historical patterns
• Identify workload imbalances before they become problems
• Track estimate accuracy and improvement trends
• Monitor test progression and quality metrics
• Validate process changes with before/after data
• Support sprint planning with historical capacity data

Available Trend Reports

Active Members Trend Report

Tracks the number of active (licensed) members using the system during a specific period.

Best for:

• License capacity planning
• Predicting future licensing needs
• Identifying usage patterns by period
• Budget forecasting for licenses

What it shows:

• Number of active licensed members over time (days, weeks, or months)
• Trend line indicating growth or reduction patterns

Key insight: The current value should match the number shown in the About Digital.ai Agility dialog (help icon → About). To see which users consume licenses, customize the Members grid to show "Uses a License" and "Last Access" columns.

Admin access required: This report requires Member Administration or System Administration privileges.

Effort Trend Report

Shows the accumulation of effort logged against all projects over time.

Best for:

• Tracking total effort investment
• Validating timesheet compliance
• Identifying effort logging patterns
• Cross-project effort analysis

What it shows:

• Cumulative effort logged over time
• Typically trends upward as effort accumulates
• Can be filtered by sprint, team, workitem type, member group, or individual member

Key insight: Each bar represents the cumulative effort on that date. Use the Effort Quicklist report to correlate and cross-check data points. This report helps ensure teams are consistently logging effort and can reveal periods of under- or over-utilization.

Estimate Trend Report

Tracks the total amount of open and closed estimate for projects, portfolio items, or sprints during a specific period.

Best for:

• Identifying scope change (scope creep)
• Monitoring remaining vs completed work
• Release planning and forecasting
• Portfolio-level capacity tracking

What it shows:

• Green section: Closed estimate (completed work)
• Red section: Open estimate (remaining work)
• Overall bar height: Total estimate
• Changes in bar height indicate scope additions or removals

Key insight: As teams close work items, the green section increases and red decreases. Changes to overall bar height reveal scope changes. This report helps distinguish between delivery progress and scope changes.

Aggregation options:

• Total Estimate: Sum of estimate values
• Workitem Count: Count regardless of estimate value

Detail Estimate Trend Report

Shows changes in total detail estimate and work done at the task/test level during a specific period.

Best for:

• Sprint execution monitoring
• Task-level tracking
• Detailed workload analysis
• Validating sprint commitments

What it shows:

• Blue line: Detail estimate trend over time
• Work done typically trends upward over time
• May surpass estimate if team underestimated workload

Key insight: This report tracks work at the task and test level, providing more granular insight than story-level estimates. Use it to identify estimation accuracy issues at the execution level.

Team Estimate Trend Report

Tracks changes in total estimate assigned to a team, amount completed, and amount remaining over time.

Best for:

• Team-specific workload tracking
• Multi-team comparison
• Team capacity planning
• Backlog health monitoring

What it shows:

• Total estimate assigned to team
• Closed estimate (trending upward)
• Open estimate (should trend downward)
• Impact of scope changes on team workload

Key insight: Closed estimate should trend upward over time. Changes to total estimates typically occur when items are added to or removed from the team's backlog, or when estimates change on existing items. This report helps assess whether a team's backlog is growing or shrinking.

Member Load Trend Report

Shows total detail estimate delivered (historical) or planned (future) for an individual member across selected sprints.

Best for:

• Individual capacity planning
• Sprint commitment validation
• Member workload balancing
• Historical capacity analysis

What it shows:

• Prior Average (blue line): Average detail estimate across all projects for previous sprints
• Capacity (Selected): Expected detail estimate in selected sprints
• Capacity (Other Projects): Expected detail estimate in other projects
• Detail Estimate (Selected): Sum of detail estimate in current project sprints
• Detail Estimate (Other Projects): Detail estimate in other projects (proportionally allocated when sprint schedules don't align)

Key insight: Use this report to understand an individual's proven capacity over time, which helps determine how much work to assign in the sprint being planned. The prior average provides a reliable baseline for future sprint planning.

Important: Capacity displayed is based on detail estimate assigned, not the same as entered capacity in Capacity Planning feature.

Member Group Load Trend Report

Tracks work assigned to a member group for selected sprints over time, comparing work in the current project vs other projects.

Best for:

• Shared resource management
• Cross-project capacity allocation
• Member group utilization tracking
• Identifying resource contention

What it shows:

• Capacity (Selected): Total capacity for sprints in selected context
• Capacity (Other Projects): Total capacity outside selected context
• Detail Estimate (Selected): Total detail estimate in selected context
• Detail Estimate (Other Projects): Detail estimate outside selected context
• Prior Average (blue line): Average detail estimate across all projects for previous sprints

Key insight: The comparison between work in the selected project and other projects indicates relative allocation of member group effort across projects. This helps identify when shared resources are over-allocated.

Prerequisites: To see Capacity values, Member Capacity must be enabled (Admin → System → Configuration → System).

Team Test Trend Report

Tracks acceptance tests by status for each item assigned to a team in a project.

Best for:

• Quality tracking over time
• Test progression monitoring
• Identifying testing bottlenecks
• Release readiness assessment

What it shows:

• Test counts broken out by status (Failed, Passed, etc.)
• Progression of tests to completion or passed status
• Stacked area chart showing status distribution over time

Key insight: This report helps track the number of tests and their progression to completion. Increasing failed tests may indicate quality issues, while increasing passed tests shows progress toward release readiness.

Customization: Status values (Failed, Passed, etc.) can be customized by System Administrators through custom List Types.

Choosing the Right Trend Report

Report	Primary Metric	Best For	Primary Users	Typical Duration
Active Members Trend	Licensed users	License planning, budget forecasting	Admins, Finance	3-12 months
Effort Trend	Logged effort	Timesheet compliance, utilization tracking	Managers, PMO	4-13 weeks
Estimate Trend	Open/closed estimate	Scope management, release tracking	Product Owners, RTEs	Project/release duration
Detail Estimate Trend	Task-level estimate	Sprint execution, detailed tracking	Scrum Masters, Teams	Sprint duration
Team Estimate Trend	Team workload	Team capacity, backlog health	Team Leads, Managers	4-13 weeks
Member Load Trend	Individual capacity	Personal workload, sprint planning	Scrum Masters, Members	4-8 sprints
Member Group Load Trend	Shared resources	Resource allocation, contention management	Resource Managers, PMO	4-8 sprints
Team Test Trend	Test status	Quality tracking, release readiness	QA Leads, Test Managers	Sprint or release duration

Accessing Trend Reports

From All Reports:

1. Click the hamburger menu → Reports → All Reports
2. Scroll to the Member and Team Tracking Reports section
3. Click the specific trend report you need

From Context Pages: Some trend reports are also available from relevant pages:

• Member Load Trend and Member Group Load Trend: Available from Sprint → Detail Planning, Member Planning, Detail Tracking, or Member Tracking
• Active Members Trend: Available from Admin → Members page

From Members Grid:

• Active Members Trend: While on Members page, click hamburger menu → Reports → Active Members Trend

Common Report Filters and Parameters

All trend reports share these common filters:

Start Date

The first date the report begins calculating data.

Defaults:

• Project-based reports: Project start date
• Sprint/iteration-based reports: Sprint/iteration start date
• Member-based reports: 13 weeks prior to current date

Note: If start date is set to current date or later, no data displays.

Duration

The number of days, weeks, or months to display.

Defaults:

• Project-based reports: Number of weeks from project start to today
• Sprint/iteration-based reports: Number of days in the sprint/iteration
• Member-based reports: 13 weeks

Note: Report ends at current date, so if selected start date and duration extend past current date, no data displays after current date.

Additional Filters (Report-Specific)

Sprint or Iteration: Shows data assigned to specific sprint/iteration (default: "All")

Team: Shows team-specific data (default: "All" or "Blank")

Member Group: Shows data for active members in selected member group only

Member: Shows data assigned to selected member

Workitem: Shows data for specific work item type (All, Backlog Items, Defects, Testsets)

Backlog Group: Shows data assigned to selected backlog group

Portfolio Item: Shows work items in selected portfolio item and children

Aggregation Type: Determines how data is aggregated (Total Estimate, Workitem Count)

Prerequisites

All Trend Reports Require:

Minimum two data points: All Digital.ai Agility trend reports require at least two data points. If not enough data is available, the report may be blank. Depending on the duration you select in the filters, at least one complete period of data must be available to draw a trend line. When selecting days, this means the minimum duration is actually 2 days, which includes 2 data points.

Weekend settings consideration: Your Show Weekend report settings may affect how much data is selected. For example, if you choose two days as duration and one day is a Saturday or Sunday, and you have elected to not Show Weekends, you may not have sufficient data to show a trend.

Report-Specific Prerequisites:

Active Members Trend:

• Requires Member Administration or System Administration privileges

Effort Trend:

• Requires effort tracking to be enabled

Member Group Load Trend:

• To see Capacity values, Member Capacity must be enabled (Admin → System → Configuration)

Using Trend Reports Effectively

For Sprint Planning

1. Review Member Load Trend for each team member to understand proven capacity
2. Check Member Group Load Trend if working with shared resources
3. Examine Detail Estimate Trend from previous sprints to validate estimation patterns
4. Use Team Estimate Trend to assess current team backlog health

For Release Tracking

1. Monitor Estimate Trend to identify scope changes early
2. Track Team Estimate Trend for each team's progress
3. Review Team Test Trend to assess quality and release readiness
4. Check Effort Trend to validate team utilization

For Capacity Planning

1. Analyze Member Load Trend over 6-8 sprints for reliable averages
2. Review Member Group Load Trend to identify resource contention
3. Use Active Members Trend for license and budget planning
4. Correlate Effort Trend with delivery to assess productivity

For Process Improvement

1. Compare Detail Estimate Trend before and after process changes
2. Track Team Test Trend to measure testing process effectiveness
3. Review Estimate Trend to assess scope management discipline
4. Analyze Effort Trend to identify logging compliance patterns

Common Patterns and Insights

Healthy Patterns

Effort Trend: Steady upward trend matching sprint cadence Estimate Trend: Green (closed) increasing, red (open) decreasing, total bar height stable Member Load Trend: Consistent delivery matching prior average Team Test Trend: Passed tests increasing, failed tests decreasing over time

Warning Patterns

Estimate Trend: Total bar height increasing significantly (scope creep) Member Load Trend: Consistently exceeding prior average (overcommitment) Member Group Load Trend: High load in "Other Projects" (resource contention) Effort Trend: Flat periods (effort logging compliance issues) Team Test Trend: Failed tests increasing (quality degradation)

Action Patterns

Scope creep detected (Estimate Trend): Hold scope review meeting, prioritize ruthlessly Overcommitment detected (Member Load Trend): Reduce sprint commitment, reassign work Resource contention detected (Member Group Load Trend): Coordinate with other projects, adjust allocations Quality issues detected (Team Test Trend): Increase test focus, hold quality reviews Effort compliance issues (Effort Trend): Remind team, simplify logging process

Best Practices

Review cadence:

• Daily: Detail Estimate Trend during sprint execution
• Weekly: Team Estimate Trend, Effort Trend for active projects
• Sprint review: Member Load Trend, Team Test Trend
• Monthly: Active Members Trend, Member Group Load Trend
• Quarterly: Long-term capacity analysis using all trends

Data quality:

1. Update work item status regularly for accurate trends
2. Log effort consistently (daily or at least weekly)
3. Maintain accurate sprint assignments
4. Keep team assignments current
5. Close completed work items promptly

Analysis tips:

• Look for patterns over 3-5 data points minimum
• Consider external factors (holidays, training, reorganizations)
• Compare trends across teams to identify best practices
• Use trends to validate, not replace, team conversations
• Combine multiple trend reports for complete picture

Avoid:

• Making decisions based on single data points
• Comparing members or teams without context
• Ignoring team feedback about data accuracy
• Using trends to pressure teams artificially
• Overlooking data quality issues

Technical Details

Data Points and Timeframes

• X-Axis: Represents time (days, weeks, or months)
• Y-Axis: Represents the metric value (count, estimate, effort, etc.)
• Each bar/point: Represents the value on that specific date
• Trend lines: Show patterns and averages over time

Report Performance

• Large datasets may take longer to generate
• Use filters to focus on relevant timeframes
• Export large reports for offline analysis
• Consider shorter durations for faster rendering

Data Refresh

• Most trend reports show real-time or near-real-time data
• Historical data requires time for aggregation
• Minimum 2 complete data points needed for trends
• Weekend data may be excluded based on settings

Related Topics

• Member and Team Tracking Reports: Overview of all member and team reports
• Load and Capacity Reports: Current workload and capacity analysis
• Sprint or Iteration Reports: Sprint-specific metrics
• Project or Release Reports: Project and release-level tracking
• Detail Planning: Breaking down stories into tasks
• Detail Tracking: Tracking task-level progress