Using and Configuring Top Triggered Alerts for Workflow Improvement

devActivity's 'Top Triggered Alerts' feature provides critical insights into your team's development performance. This guide will walk you through how to effectively use and configure these alerts to identify bottlenecks and drive continuous improvement in your workflow.

1. Accessing Top Triggered Alerts

1. Navigate to Retrospective Insights: Log in to devActivity.com and proceed to the Retrospective Insights Details page.
2. Locate the Widget: On this page, find the 'Top Triggered Alerts' widget, which presents a table of alerts that have activated during the selected retrospective period.

2. Understanding Alert Details

Each row in the 'Top Triggered Alerts' table offers detailed information about a specific alert:

• Alert Description: For example, 'More than 10 hours for PR's Pickup Time'.
• Contextual Details: Beneath the main alert, you'll find the relevant repository (e.g., 'web-framework'), the specific pull request that triggered the alert ('feature: robust JSX whitespace handling by [user avatar]'), time metrics ('1d 2h'), and related comments ('3').
• Trigger Count: The 'TRIGGER COUNT' column indicates how many times this specific alert condition was met during the retrospective period. This helps you prioritize issues based on their frequency.

3. Configuring Alert Thresholds

A key strength of devActivity's alerts is their configurability. Alerts can be individually configured with various triggering thresholds to align with the specific development process of your team or organization. This ensures that the alerts are truly relevant to your unique environment.

• Customizing Thresholds: Access the alert settings (specific navigation to be added in future updates) to adjust parameters like maximum PR pickup time, acceptable cycle time, or task completion deadlines.
• Adapting to Your Process: Tailor alerts to reflect your team's specific practices, ensuring that only truly important deviations are flagged for attention.

4. Leveraging Alerts for Retrospectives

Once you've identified triggered alerts, use these insights to delve deeper into the causes of these triggers and address them proactively:

• Data-Driven Discussions: Use the 'Top Triggered Alerts' as a starting point for retrospective meetings, focusing discussions on actual, quantifiable issues.
• Root Cause Analysis: Investigate why certain alerts (e.g., increased cycle time, unclosed tasks) were triggered, identifying underlying process inefficiencies or blockers.
• Continuous Improvement: Adapt your development processes and alert configurations based on your findings, driving ongoing improvements in team productivity and workflow efficiency.