Skip to main content

Team Management

PanDev Metrics lets you organise developers into teams, configure roles, and control access to data.

Creating a Team​

Basic Settings​

  1. Team name – a unique identifier.
  2. Description – short summary of the team’s purpose.
  3. Owner – team lead or manager.
  4. Projects – linked projects and repositories.

Metric Configuration​

  • Data types – choose which metrics to capture.
  • Collection cadence – how often data is refreshed.
  • Level of detail – depth of the reports provided.

Team Members​

Adding Members​

  1. By email – send invitations to join.
  2. By username – add existing PanDev users.
  3. Bulk import – upload a CSV file.

Team Roles​

  • Administrator – full control over team settings.
  • Manager – view metrics and manage membership.
  • Analyst – access reports and analytics.
  • Developer – view personal metrics.

Access Management​

Access Levels​

  • Public metrics – visible to everyone.
  • Team metrics – visible to team members.
  • Personal metrics – visible only to the individual engineer.
  • Administrative features – restricted to admins.

Permissions​

  • View – read-only access to metrics.
  • Export – download datasets.
  • Configure – adjust metric settings.
  • Manage – modify team membership.

Organising Teams​

Hierarchy​

  • Departments – high-level groups (Backend, Frontend, QA).
  • Teams – working squads within departments.
  • Projects – temporary teams for specific initiatives.

Relationships​

  • Parent teams – higher-level groups.
  • Subteams – child units within a parent.
  • Joint projects – teams collaborating together.

Team Metrics​

Aggregated Metrics​

  • Overall performance – combined output of the team.
  • Averages – typical values per member.
  • Distribution – spread of metrics across the team.
  • Trends – how metrics evolve over time.

Comparative Analysis​

  • Across teams – benchmark different squads.
  • Within a team – explore individual differences.
  • Against benchmarks – compare with industry standards.

Team Notifications​

Notification Types​

  • Weekly summaries – key metric digest.
  • Alerts – critical changes that need attention.
  • Achievements – highlight positive trends.
  • Reminders – upcoming deadlines and tasks.

Configuration​

  • Frequency – how often notifications arrive.
  • Channels – email, Slack, Teams, mobile push.
  • Filters – choose which updates to receive.

Team Analytics​

Reports​

  • Weekly – recurring snapshots of performance.
  • Monthly – in-depth reviews.
  • Quarterly – strategic outlook.
  • Custom – ad hoc analysis.

Dashboards​

  • Team dashboard – key metrics at a glance.
  • Comparison – side-by-side team comparisons.
  • Trend – long-term evolution.
  • Deep dive – drill into specific aspects.

Integrations​

Work Management​

  • Jira – sync with issues and sprints.
  • Trello – connect to task boards.
  • Asana – integrate with ongoing projects.

Version Control​

  • GitHub – analyse commits and pull requests.
  • GitLab – work with merge requests.
  • Bitbucket – attach repositories.

Communication Platforms​

  • Slack – bots and notifications.
  • Microsoft Teams – collaborate in channels.
  • Discord – great for open-source or gaming teams.

Best Practices​

Structuring Teams​

  • Team size – aim for 5–9 members.
  • Clear roles – align responsibilities.
  • Regular retrospectives – continuously improve processes.

Working with Metrics​

  • Process focus – use metrics to improve, not police.
  • Transparency – discuss metrics openly with the team.
  • Actionable follow-up – turn insights into change.

Next Steps​