Member and Team Tracking Reports

Member and team tracking reports help you understand how work is allocated across teams and members, identify capacity constraints, track estimation accuracy, and manage resource utilization. Use these reports to balance workloads, forecast capacity needs, and make data-driven decisions about team effectiveness and resource allocation.

Report Categories

Member and team tracking reports fall into several key categories:

Trend Reports

Track changes over time in member activity, workload, estimates, effort, and test progression:

• Member and Team Trend Reports: Comprehensive trend analysis including active members, effort, estimates (detail, team, general), member load, member group load, and team test trends

Load and Capacity Reports

Provide snapshot and forward-looking views of workload distribution:

• Load and Capacity Reports: Current member load, load by sprint, estimation accuracy, and member actuals

Cross-Project Team Reports

Track team progress across multiple projects and releases:

• Team Burndown Report: Team remaining and completed backlog estimate across projects or releases

Administrative Reports

Specialized reporting for compliance and administration:

• Timesheet Audit Report: Timesheet submission history by team member and week (requires Member Admin or System Admin privileges)

Choosing the Right Report

By Use Case

Use Case	Recommended Reports	Frequency
Sprint Planning	Member Load Trend, Load by Sprint, Estimation Accuracy	Sprint planning sessions
Daily Workload Balancing	Current Member Load	Daily during sprint
Capacity Forecasting	Member Load Trend, Member Group Load Trend, Active Members Trend	Monthly or quarterly
Estimation Improvement	Estimation Accuracy, Detail Estimate Trend	Sprint retrospectives
Resource Management	Member Group Load Trend, Current Member Load, Load by Sprint	Weekly
Timesheet Compliance	Member Actuals, Timesheet Audit, Effort Trend	Weekly or monthly
License Planning	Active Members Trend	Quarterly or annually
Quality Tracking	Team Test Trend	Sprint or release cycle
Cross-Project Tracking	Team Burndown, Member Group Load Trend	PI planning, monthly reviews

By User Role

Scrum Masters:

• Current Member Load (daily workload balancing)
• Load by Sprint (sprint planning)
• Member Load Trend (capacity planning)
• Estimation Accuracy (retrospectives)

Team Leads/Managers:

• Team Estimate Trend (team workload trends)
• Team Burndown (cross-project progress)
• Member Group Load Trend (shared resource management)
• Member Actuals (utilization tracking)

Resource Managers:

• Member Group Load Trend (resource allocation)
• Current Member Load (capacity availability)
• Load by Sprint (forward capacity planning)
• Member Actuals (utilization analysis)

Product Owners:

• Team Estimate Trend (team capacity trends)
• Estimation Accuracy (planning accuracy)
• Team Test Trend (quality metrics)

Administrators:

• Active Members Trend (license planning)
• Timesheet Audit (compliance tracking)
• Effort Trend (system usage patterns)

QA/Test Managers:

• Team Test Trend (test progression)
• Detail Estimate Trend (task-level tracking)

Report Types Explained

Trend Reports (Historical Analysis)

Trend reports visualize how metrics change over time using line charts, bar charts, and stacked area charts. They answer questions like:

• How has team capacity changed over the last quarter?
• Are we improving our estimation accuracy?
• What are typical workload patterns for our shared resources?
• Is effort logging compliance improving?

Best for: Forecasting, pattern identification, process improvement validation, long-term planning

Load Reports (Current State)

Load reports provide snapshot views of current and near-term workload. They answer questions like:

• Who has capacity for additional work right now?
• Is work evenly distributed across the team?
• How much is each member committed to in upcoming sprints?
• How accurate were our estimates?

Best for: Sprint planning, daily workload balancing, immediate capacity decisions, sprint execution

Capacity Reports (Future Planning)

Capacity reports combine historical patterns with forward-looking commitments. They answer questions like:

• Do we have enough capacity for the planned work?
• Are shared resources over-allocated?
• What's a realistic commitment based on historical data?
• Where are capacity bottlenecks?

Best for: Multi-sprint planning, resource allocation, dependency management, capacity forecasting

Common Use Cases

Sprint Planning

Before Planning Session:

1. Review Member Load Trend reports to understand proven individual capacity
2. Check Member Group Load Trend if working with shared resources
3. Examine Estimation Accuracy from previous sprint to adjust approach
4. Review Detail Estimate Trend to identify task-level patterns

During Planning Session:

1. Use Load by Sprint to distribute work evenly
2. Reference historical capacity data when discussing commitments
3. Validate that planned load aligns with velocity and capacity
4. Check Current Member Load if sprint is already in progress

After Planning Session:

1. Verify balanced distribution using Load by Sprint
2. Document capacity baseline for retrospective
3. Set up regular Current Member Load reviews for sprint

Daily Workload Management

During Sprint Execution:

1. Review Current Member Load daily during standups
2. Identify team members who are blocked or have capacity
3. Redistribute work to maintain balance
4. Track against Load by Sprint planned capacity

Mid-Sprint Adjustments:

1. Use Current Member Load to guide redistribution decisions
2. Check impact on future sprints using Load by Sprint
3. Update to-do values regularly for accurate reporting
4. Monitor Team Test Trend if quality concerns emerge

Capacity Planning and Forecasting

Multi-Sprint Planning:

1. Analyze Member Load Trend over 6-8 sprints for reliable averages
2. Review Member Group Load Trend for shared resources
3. Use Load by Sprint to visualize capacity across next 3-4 sprints
4. Compare Team Estimate Trend with historical velocity

Resource Allocation:

1. Check Member Group Load Trend for resource contention signals
2. Review Current Member Load across all active projects
3. Use Load by Sprint to identify over-allocated members
4. Balance work based on capacity data, not assumptions

License and Budget Planning:

1. Review Active Members Trend over past year
2. Project growth patterns for future license needs
3. Correlate with Effort Trend to understand active usage
4. Plan budget based on utilization trends

Process Improvement

Estimation Improvement:

1. Track Estimation Accuracy report sprint over sprint
2. Identify consistent over or under-estimators
3. Discuss patterns in retrospectives
4. Compare Detail Estimate Trend before/after process changes

Efficiency Analysis:

1. Correlate Effort Trend with delivery metrics
2. Review Team Test Trend to assess testing effectiveness
3. Compare Member Actuals with planned capacity
4. Use trends to validate process improvement initiatives

Resource Management

Weekly Reviews:

1. Check Current Member Load across active projects
2. Review Member Actuals for timesheet compliance
3. Identify shared resources with high load in multiple projects
4. Address capacity issues proactively

Monthly Analysis:

1. Analyze Member Actuals trends for utilization patterns
2. Review all Load and Trend reports for capacity insights
3. Forecast capacity needs for next quarter
4. Adjust resource allocation based on data

Best Practices

Data Quality

For Accurate Reporting:

1. Update to-do values regularly (daily is ideal)
2. Log effort consistently (at least weekly)
3. Maintain accurate sprint assignments
4. Keep team and ownership assignments current
5. Close completed work items promptly

Common Data Issues:

• Stale to-do values make load reports inaccurate
• Inconsistent effort logging skews actuals reports
• Incorrect ownership affects load distribution
• Unclosed items inflate remaining work

Review Cadence

Daily:

• Current Member Load during sprint execution
• Quick check of Detail Estimate Trend for sprint health

Sprint Planning:

• Member Load Trend for capacity planning
• Load by Sprint for work distribution
• Estimation Accuracy from previous sprint
• Team Estimate Trend for backlog health

Sprint Review:

• Estimation Accuracy for completed sprint
• Team Test Trend for quality assessment
• Current Member Load final snapshot

Weekly:

• Member Actuals for timesheet compliance
• Current Member Load if managing multiple projects
• Member Group Load Trend for shared resources

Monthly:

• All trend reports for pattern analysis
• Capacity forecasting using historical data
• Utilization analysis with Member Actuals
• Cross-project capacity review with Team Burndown

Quarterly:

• Active Members Trend for license planning
• Long-term capacity analysis across all reports
• Process improvement validation with trends

Analysis Tips

Context Matters:

• Consider external factors (holidays, training, reorganizations)
• Account for varying work complexity and types
• Understand team member partial allocation scenarios
• Factor in non-tracked work (meetings, support, etc.)

Pattern Recognition:

• Look for patterns over 3-5 data points minimum
• Compare trends across teams to identify best practices
• Use trends to validate, not replace, team conversations
• Combine multiple reports for complete picture

Decision Making:

• Don't make capacity decisions based on single data points
• Validate data accuracy with team before acting
• Use reports to facilitate conversations, not dictate actions
• Balance quantitative data with qualitative feedback

Avoiding Common Pitfalls

Don't:

• Compare members or teams without context
• Use load to measure productivity or performance
• Make workload decisions without team consultation
• Force perfect balance without considering work type differences
• Ignore team feedback about data accuracy
• Pressure teams based on trends alone

Do:

• Balance workload considering individual capacity differences
• Use reports to identify conversations needed with team
• Consider trends as indicators, not absolute truths
• Regularly validate data quality with team
• Factor in non-measurable work (technical debt, support, etc.)
• Combine reports for comprehensive understanding

Prerequisites

Global Requirements

Most member and team reports require:

• Active projects with work items
• Team and member assignments configured
• Sprint/iteration schedules defined

Feature-Specific Requirements

Effort-Based Reports:

• Effort tracking must be enabled globally
• Team members must log effort regularly

Capacity Planning:

• Member Capacity feature must be enabled
• Capacity values must be set for members/teams

Timesheet Reports:

• Timesheet feature must be enabled
• Member Admin or System Admin privileges required

Active Members Trend:

• Member Administration or System Administration privileges

Technical Considerations

Report Performance

• Trend reports over long periods may take longer to generate
• Use filters to focus on relevant timeframes and teams
• Export large reports for offline analysis
• Consider shorter durations for faster rendering

Data Refresh

• Most reports show real-time or near-real-time data
• Historical data may require time for aggregation
• Trend reports need minimum 2 complete data points
• Weekend data may be excluded based on settings

Common Filters

Across Most Reports:

• Sprint or Iteration
• Team
• Member Group
• Member
• Workitem type
• Start Date and Duration (trend reports)

Specialized Filters:

• Allocate by Owner (load reports)
• Show Closed Items (load reports)
• Backlog Group
• Portfolio Item
• Aggregation Type

Related Topics

• Member and Team Trend Reports: Historical analysis and forecasting
• Load and Capacity Reports: Current workload and capacity analysis
• Team Burndown Report: Cross-project team progress
• Timesheet Audit Report: Compliance tracking
• 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