📖
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 I connect multiple Git organizations to get a consolidated view on Typo?
      • Can Typo application work with on-prem Gitlab?
      • How do I unlink the JIRA tracker & integrate Linear?
      • How do I change a CI/CD integration?
      • How do I export my Git data?
      • Can I integrate with Azure Repos?
    • Pricing
      • How does the free plan work and how can I switch to it?
      • How does the pricing work?
      • How do I upgrade my plan?
      • How are active users Counted for billing?
    • 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 put checks before merging a PR in BitBucket
      • 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 to exclude a PR from any metric calculation?
      • My data is not visible, I have synced the repo
      • How do I create and download a custom report?
    • Platform
      • Which programming languages are supported for code coverage feature?
      • How do I manage notifications?
      • 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 Progress

PreviousWork BreakupNextCode Quality Metrics

Last updated 6 months ago

Work progress represents the percentage breakdown of Issue tickets or Story points in the selected sprint according to their current workflow status.

Typo considers all the issues in the sprint and categorizes them based on their current status category, using your JIRA status category mapping. It shows three major categories by default: Open, In Progress, and Done. These can be configured as per your custom processes. In the case of a closed sprint, Typo only shows the breakup of work on a ‘Completed’ & ‘Not Completed’ basis. If a task is ‘Not Completed’ in the selected sprint but is ‘Completed’ in the future sprint, it will still be shown as ‘Not Completed’.

How does tracking work breakup help in sprint analysis?

Tracking work progress provides valuable insights into engineering teams' work status and efficiency during a sprint. Here are a few points highlighting how monitoring work progress contributes to improving the efficiency of engineering teams:

  1. Visibility and Transparency: By tracking work progress, teams gain visibility into the status of individual tasks or stories within the sprint. This promotes transparency across the team, allowing members to understand what work is in progress, completed, or blocked, facilitating better collaboration and coordination.

  2. Identifying Bottlenecks: Work progress metrics help identify bottlenecks or blockers in the workflow. Teams can quickly identify tasks that are stalled or facing delays, allowing them to address issues and keep the work flowing smoothly and proactively. This prevents work from piling up and ensures the team stays on track to meet sprint goals.

  3. Optimizing Workflows: Insights from work progress data enable teams to optimize their workflows and processes. By analyzing the distribution of tasks across different workflow statuses, teams can identify areas where work tends to get stuck or delayed. This allows them to streamline workflows, eliminate unnecessary handoffs, and implement process improvements to accelerate work progress.