Work Periods
Work Periods Overview
Welcome to the Work Periods tab in Bloomfilter.ai! This module provides a sprint-level and multi-sprint view of delivery performance. It combines adherence metrics, throughput data, and workflow trends to assess how effectively teams plan, execute, and deliver work over defined work periods (such as sprints).
Use Cases:
Sprint reviews and retrospectives to evaluate execution health
Program-level insights into delivery consistency
Identifying systemic inefficiencies across teams or boards
Work Periods gives teams objective visibility into delivery behavior, not just outcomes. By grounding discussions in execution data, it enables better planning, more predictable delivery, and continuous improvement over time.
This field guide breaks down each key component of the Work Periods page. For each, you'll find:
What it is: A clear description of the feature.
Use Cases: Practical scenarios where it's most helpful.
Why it's Valuable: The business impact and benefits.
Business Value:
Work Periods gives engineering and delivery teams objective, sprint-level visibility into how effectively they plan, execute, and deliver; combining health scoring, flow analysis, and multi-sprint comparison to drive better retrospectives, more predictable commitments, and continuous improvement across the delivery lifecycle.
Use this guide to navigate the tab confidently and unlock insights that drive better decision-making.
How to Navigate Work Periods Module:
Navigation Steps
Select Assessment View (for Individual Sprint Review) or Comparison (to analyze multiple sprints at the same time)
Filter by Board
Select Date Filter
Pre-Defined: Select Predefined start and end dates based on sprints.
Ad-Hoc: Select specific date ranges
Select Work Period(s) and review insights
Located at the top of the Work Periods page, this panelExport Button: In the top right of your screen, allows users to download the current graph as an image, complete with all selected variables.
How to Compare Sprints & Metrics:
What it is: Sprint Comparison allows users to analyze up to six sprints simultaneously using multiple analysis views: Table View, Measure Comparison, and Measures Over Time.
Use Cases:
Comparing recent sprints to identify improvement or regression
Validating whether process changes had the intended impact
Identifying consistency (or volatility) in key delivery metrics
Why it’s Valuable: By enabling side-by-side sprint analysis, this feature helps teams move beyond anecdotal feedback and base decisions on trends and evidence, improving forecasting accuracy and delivery reliability.
Navigation Steps:
Select Comparison at top of page
Select Board
Select up to 6 Sprints on left filter panel
Select Analysis View:
Table View:
Measure Comparison:
Key Measures Over Time:
Work Periods: Assessment
Assessment
What it is: The Assessment view evaluates the efficiency of a single team during a selected sprint. Each sprint receives a health grade based on eight key process measures, with AI-generated insights highlighting notable patterns or risks.
Use Cases:
Sprint retrospectives focused on execution quality
Coaching teams on planning, readiness, and scope management
Identifying root causes behind missed commitments
Why it’s Valuable: Sprint health scoring provides a structured, repeatable way to assess execution beyond velocity alone. It encourages better sprint hygiene and helps teams improve predictability without increasing pressure.
How Sprint Grade is Calculated: https://www.bloomfilter.ai/resources/introducing-new-product-metrics-to-better-understand-your-sdlc-health
Key Process measures: If you're unsure about what a specific measure entails or how it is calculated, you can simply click on it. This will redirect you to a detailed page
Strategy: Percentage of tasks associated with an epic within the selected date range
Complexity:The average number of points for tasks that are not yet done, are were done after the start of the work period.
Quality: The number of tech debt and bug share to the total number of tasks within the selected date range
Scope: What percentage increase/decrease in scope was committed to this sprint after it started
Readiness: A percentage of how many tasks in the sprint are "ready" Ready is defined as having a name, description, and points. However, only bugs need a name and description if the associated board setting indicates bugs should not be pointed out.
Independence: Percentage of tasks not blocked by another task.
Work Phase Distribution
What it is: Work Phase Distribution visualizes how tasks move through workflow stages (e.g., Ready, Blocked, WIP, Review, Test, Deploy, Done) during a sprint. Users can view this by task count or points and switch between chart and task-flow views.
Use Cases:
Identifying workflow bottlenecks (e.g., review or testing delays)
Understanding where work spends most of its time
Analyzing flow efficiency during retrospectives
Why it’s Valuable: This view makes invisible workflow friction visible. By highlighting delays and imbalances across phases, teams can optimize flow, reduce cycle time, and improve overall throughput.
Users can switch between # of tasks or points view in the top right and also switch between a chart view and a task flow view which allows teams to see where each task was on a given day
Work Pace
What it is: Work Pace shows completed work relative to originally planned work over time, offering a view into long-term delivery consistency and planning accuracy.
Use Cases:
Evaluating whether teams consistently over- or under-commit
Assessing stability across multiple sprints
Supporting long-term capacity and roadmap planning
Why it’s Valuable: Work Pace shifts the focus from isolated sprint outcomes to sustained performance. It helps organizations balance ambition with realism, leading to healthier teams and more reliable delivery forecasts.
Delivery Confidence
What it is: Delivery Confidence compares completed work against committed scope while tracking scope changes throughout the sprint. Confidence bands reflect historical delivery ranges based on prior sprints.
Use Cases:
Forecasting sprint outcomes mid-sprint
Identifying risk introduced by scope creep
Improving trust in delivery commitments
Why it’s Valuable: This feature connects planning discipline with execution outcomes. By visualizing confidence ranges and scope changes, teams can proactively manage risk and improve predictability over time.
Legend:
Green line is completed work items on a given day
Purple band shows to scope increase from beginning of sprint to end Confidence band which shows your upper and lower deliver over the past 16 sprints
Work Periods: Comparison
Table View
What it is: The Table View presents key metrics and trends across selected sprints in a structured, side-by-side format.
Use Cases:
Comparing performance metrics across sprints quickly
Identifying trends in readiness, scope, or complexity
Supporting leadership or delivery health reviews
Why it’s Valuable: The table provides a concise, factual baseline for sprint comparison, enabling fast analysis without needing to interpret multiple charts.
Measure Comparison
What it is: Measure Comparison allows users to visualize up to four metrics across selected sprints using line or bar charts. Metrics include scope creep, readiness, acceptance rates, velocity, and complexity.
Use Cases:
Evaluating tradeoffs between quality, speed, and scope
Tracking the impact of process changes
Identifying correlations between different delivery metrics
Why it’s Valuable: This view helps teams understand how metrics interact over time, encouraging balanced decision-making instead of optimizing for a single outcome like velocity.
Measures Over Time
What it is: Measures Over Time enables users to track a single metric day-by-day within each sprint, highlighting how it evolves throughout the work period.
Use Cases:
Monitoring scope changes during a sprint
Identifying late-stage instability or churn
Analyzing execution patterns within the sprint lifecycle
Why it’s Valuable: Day-level visibility helps teams detect issues early rather than after the sprint ends. This supports proactive intervention and continuous improvement within active work periods.
Last updated