📖
Typo Help Docs
  • Welcome
  • Getting Started
    • Onboarding
    • Integrations
      • Git
        • GitHub
        • GitLab
        • BitBucket
        • Azure Repos
        • Gitlab On-prem
      • Issue Tracker
        • JIRA
        • Linear
        • GitHub Issue
        • Shortcut
        • ClickUp
      • CI/CD Tool
        • Circle CI
        • Jenkins
        • Heroku
        • GitHub Actions
        • Azure DevOps
        • Custom Deployment Webhook
      • Slack
    • How Requestly setup Typo in a few days
  • Platform
    • Dev Analytics
      • DORA
      • Insights
        • Teams
        • Members
        • Sprints
        • Pull Requests
        • Deployments
      • Incident
      • Goals
      • Investment
      • Initiative
      • WorkLog
      • Custom Reports
      • Settings
        • Teams
        • Member
        • Repository
        • Projects
        • Manage Access
        • Notifications
    • Code Health
      • Code Review
      • Code Coverage
    • DevEx
  • Implementation Plan
    • Phase 1 - Setting Up Data Sources
    • Phase 2 - Metric Configuration
      • Dev360
      • Code Health
      • DevEx
    • Phase 3 - Team Rollout
  • Engineering Metrics
    • DORA
      • Cycle Time
      • Deployment PRs
      • Change Failure Rate
      • Mean Time to Restore
    • Pull Request Metrics
      • Avg. Commits During PR Review
      • Coding Days
      • Coding Time
      • Merge frequency
      • Merge Time
      • Pickup Time
      • PR Size
      • PRs Merged without Review
      • Review Time
      • Efficiency Score
    • Sprint Metrics
      • Carry over
      • Developer Workload
      • Issue Cycle Time
      • Issues At-Risk
      • Scope creep
      • Team Velocity
      • Work Breakup
      • Work Progress
    • Code Quality Metrics
      • OWASP Top 10
      • Vulnerability
      • Security
      • Performance
      • Duplication
      • Code Smell
    • Deployment Metrics
      • Deployment - Failure
      • Deployment - Frequency
      • Time to Build
    • Incident Metrics
      • Incident - Opened
      • Avg Resolution Time
    • DevEx Metrics
      • DevEx Score
      • Space mood
      • Response Rate
      • Manager Support
      • Developer Flow
      • Product Management
      • Development & Releases
      • Culture & Values
  • Configurations
    • Cycle Time
    • Deployment PRs
    • Change Failure Rate (CFR)
    • Mean Time To Restore (MTTR)
    • CI/CD - Deployment
    • Incident
    • Initiative
    • Investment Distribution
    • PR Labels
    • Code Health
    • Code Coverage
    • DevEx
    • Notifications
    • Manage Access
  • FAQ's
    • Data Security
      • GitHub App Permissions Details
      • Why does Typo need write permission to my code?
      • Does Typo has access to my code?
      • What data security guidelines does Typo follow?
    • Integrations
      • Can Typo application work with on-prem Gitlab?
      • How do I get Issue Tracker data?
      • How do I get Git data?
    • Pricing
      • How does the pricing work?
      • How do I upgrade my plan?
    • Access Management
      • My team member is not able to login to Typo
    • Metrics
      • How does Typo predict developer burnout?
      • Is there a way to change the branch that Deployment PRs are measured against?
      • Synchronize “CFR” & “MTTR” without incident management?
      • How quick does the pull-request page update? I closed a PR but the Typo still shows Awaiting Review
      • How do I add any new repo?
      • How to Configure Typo Code Health Checks to Block a PR Merge in Git
      • Can I exclude a person from metrics calculation?
      • Can I track the Cycle time based on the status of the JIRA tickets?
      • How do I unlink the JIRA tracker & integrate Linear?
      • How to exclude a PR from any metric calculation?
      • My data is not visible, I have synced the repo
    • Platform
      • Can I use your application on-premise?
    • Delete Account
      • How can I delete my account?
Powered by GitBook
On this page
  1. Engineering Metrics
  2. Sprint Metrics

Work Breakup

PreviousTeam VelocityNextWork Progress

Last updated 5 months ago

Work breakup represents the percentage breakdown of Issue tickets in the current sprint according to their Issue Type or Labels. This helps in understanding the kind of work being picked in the current sprint & plan accordingly.

Typo considers all the Issue tickets in the selected sprint & sums them up based on their Issue Type.

How does tracking work breakup help in sprint analysis?

Tracking work breakup provides valuable insights into the composition of tasks and issues within the current sprint. Here are a few points highlighting how monitoring work breakup helps in sprint analysis:

  1. Identifying Priority Areas: Work breakup allows teams to identify the distribution of different types of issues or tasks within the sprint. By analyzing the percentage breakdown of issue types or labels, teams can prioritize their efforts based on the most prevalent or critical categories, ensuring that important tasks receive appropriate attention and resources.

  2. Understanding Workload Distribution: Work breakup helps teams understand the distribution of workload across different issue types or labels. By examining the percentage distribution of tasks, teams can ensure a balanced allocation of resources and effort across various areas, avoiding overloading certain categories while neglecting others.

  3. Detecting Trends and Patterns: Monitoring work breakups over multiple sprints enables teams to detect trends and patterns in task distribution. By tracking changes in the distribution of issue types or labels over time, teams can identify recurring patterns, emerging trends, or areas of improvement, informing future sprint planning and resource allocation decisions.

  4. Improving Sprint Planning: Insights from work breakup analysis inform sprint planning activities. By understanding the composition of tasks and issues within the sprint, teams can better estimate the complexity, effort, and duration associated with different categories of work, leading to more accurate sprint planning and forecasting.

  5. Optimising Resource Allocation: Work breakup data guides resource allocation decisions during sprint execution. By identifying areas with a higher concentration of tasks or issues, teams can allocate resources, such as team members or specialized skills, more effectively to address critical areas and ensure balanced workload distribution across the sprint.

  6. Facilitating Retrospective Discussions: Work breakup analysis provides valuable data for retrospective discussions at the end of the sprint. Teams can use insights from task distribution to evaluate sprint performance, identify areas of improvement, and discuss strategies for optimizing future sprint execution based on the observed distribution patterns.