📖
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

Issues At-Risk

PreviousIssue Cycle TimeNextScope creep

Last updated 9 months ago

Issues At-Risk highlights those Issue tickets in the ongoing sprint that are at a potential risk of not getting completed on time. This acts as a proactive measure to keep track of such Issues to ensure timely delivery of sprint.

Typo runs a predictive algorithm to highlight such Issues in the sprint that have a risk of delayed delivery. There are multiple factors taken into consideration while flagging such issues:

  • If the issue has been ‘In Progress’ state for 2 or more days with no activity

  • If the issue is still ‘In Progress’ state & the sprint closure is in the next 72 hours or more

  • If there hasn’t been any activity on an issue for long & more.

How does tracking issue at-risk help in sprint analysis?

Tracking issues labeled as "at-risk" is essential for sprint analysis as it helps teams anticipate and address potential challenges, maintain progress toward sprint goals, and drive continuous improvement in agile software development projects.

  1. Early Risk Identification: Tracking issues labeled as "at-risk" helps in identifying potential blockers or challenges early in the sprint. By flagging issues that are at risk of not being completed on time, teams can proactively address them before they escalate into larger problems.

  2. Resource Allocation: Monitoring at-risk issues allows teams to allocate resources more effectively. By identifying tasks that are in danger of falling behind schedule, teams can reallocate resources or prioritize work to ensure that critical tasks are completed on time.

  3. Sprint Progress Monitoring: Tracking at-risk issues provides visibility into the overall progress of the sprint. Teams can monitor the number of at-risk issues over time and assess whether the sprint is on track to meet its goals. This helps in making informed decisions about adjusting priorities or timelines as needed.

  4. Mitigating Risks: Identifying at-risk issues enables teams to take proactive measures to mitigate risks and prevent delays. Teams can collaborate to resolve blockers, re-evaluate priorities, or seek additional support to ensure that at-risk tasks are completed on schedule.

  5. Stakeholder Communication: Monitoring at-risk issues facilitates transparent communication with stakeholders. Teams can provide timely updates on the status of at-risk tasks, discuss potential impacts on project timelines, and work together to address any concerns or challenges.

  6. Continuous Improvement: Tracking at-risk issues provides valuable data for retrospective analysis. Teams can review the root causes of at-risk issues, identify patterns or trends, and implement process improvements to prevent similar issues from occurring in future sprints.