DevDynamics
  • Overview
    • 💡Getting Started
    • ❓FAQ
    • Configuration
      • Best Practices
      • Setting Up Issue Management System in DevDynamics
      • Setting Up Version Control
      • Setting Up Investment Categories in DevDynamics
      • Configuring Communication Channels in DevDynamics
      • Change Failure
      • Deployment
      • Manage Contributors
      • Manage Teams
  • Integrations
    • GitLab
    • GitHub
    • BitBucket
    • On-Premises BitBucket
    • On-Premises GitHub
    • Jira
    • Slack
    • Linear
    • Pagerduty
    • Microsoft Teams
    • Sonar Cloud
    • Sonar Qube
    • CI/CD
    • Azure Repo
    • Azure Board
    • Opsgenie
    • ClickUp
    • Outlook
    • Google Calendar
    • Shortcut
    • OpenProject
    • Asana
    • Test Suite
  • Installations
    • On-Premises Agent Installation Guide
  • Features
    • Metrics
      • Cycle Time Metrics
      • DORA Metrics
      • Git Dashboard
        • Feedback Responsiveness Index (FRI)
        • Review Responsiveness Index (RRI)
        • Review Completion Index (RCI)
        • Reviewer Distribution
        • Average Active Days
        • PR Review Health
        • Open PR Age
        • Work Breakdown: Distribution of Work (Lines of Code)
      • Ticket Dashboard
        • Issue Throughput
        • Open Issue Age
        • Backward Momentum
        • Issue Cycle Time Spread
        • Requirement Stability Index
      • Issue Closed Count/Task Velocity
      • Story Points Completed
      • Bug Closed Count
      • Bug Opened Count
      • Pull Request Merged Count
      • PR Comment Count
      • Pull Request Size
      • Pull Request Open Count
      • Pull Request Review Count
      • Contributors Working on Non-Working Days
      • Contributors working out of office hours
      • Contributors getting burnout
    • Team Insights
    • Initiatives
Powered by GitBook
On this page
  • 1. Introduction:
  • 2. Definitions:
  • 3. Explanation of Charts:
  • 4. Interpretation:
  • 5. Key Points:
  • 6. Conclusion:
  • 7. Analytics Features:
  1. Features
  2. Metrics

Contributors working out of office hours

PreviousContributors Working on Non-Working DaysNextContributors getting burnout

Last updated 11 months ago

1. Introduction:

This document outlines how to analyse and visualise the workload of contributors working outside of designated office hours. This metric, referred to as "Contributors working out of office hours," sheds light on the commitment and risks to your Team’s Health, specifically for those who regularly contribute beyond their core working hours.

2. Definitions:

  • Contributor: An individual who submits changes (pull requests, PRs) to the codebase.

  • After-Hours: The time period outside of your organisation's standard office hours. This timeframe can be customised based on your specific work schedule (e.g., evenings, weekends).

3. Explanation of Charts:

The Line Chart provides a combined view of Comments within certain date range:

  • Horizontal axis: Represents time (e.g., weeks).

  • Vertical axis (left): Number of contributors.

  • Blue line: Cumulative change of number of contributors.

4. Interpretation:

  • Identifying Potentially Burnt-out Contributors: Helps recognize individuals who consistently contribute outside of regular working hours.

  • Workload Insights: Provides a general understanding of the team's overall after-hours workload.

  • Motivation and Recognition: Can be used to acknowledge and appreciate contributors who put in extra effort.

5. Key Points:

  • Identify Engaged Contributors: This analysis helps recognize individuals who consistently log work outside of regular office hours, potentially getting burnout due to workload and passion for the project.

  • Workload Visibility: Provides insights into the overall volume of work logged by contributors after-hours within a specific timeframe..

  • Work-Life Balance Awareness: Helps assess potential workload imbalances and identify contributors who might be putting in excessive after-hours efforts.

6. Conclusion:

Tracking After-Hours Throughput offers valuable insights into your team's workload patterns. This metric, alongside open communication and a culture of appreciation, can help motivate contributors and foster a positive work environment.

7. Analytics Features:

Descriptive Statistics:

  1. Increased Average Contributors:

  • Growing team size or increased project activity leading to more contributors working after-hours.

  • Consider offering flexible work arrangements or acknowledging contributors' extra effort.

  1. Decreased Average Contributors:

  • Reduced project activity leading to less need for after-hours work.

  • Changes in team composition or work culture potentially impacting after-hours workload.