Within our emerging Financials feature, we sought to introduce three blended-cost breakdowns: Build, Run and Maintain cost breakdowns. This is a calculation using dev work in each phase of development * blended hourly rate from the customer-uploaded spreadsheet introduced last release.
What’s New?
Bloomfilter now displays cost breakdown by project’s phase of development, with the phases adding up to the subtotal for the type of cost (Build, Run, Maintain)
Added a tool tip to summarize calculation in simple terms for user.
Cost breakdowns by phase of development and the new tool tip.
Enhancements
Removed inactive DORA metrics from view. Previously the app was displaying common DORA metric fields, but there were no corresponding values being displayed (thank you, Andrew!)
Cycle time chart now lists cycles in descending chronological order.
The header was updated to include a housekeeping area for settings, legal notices, and logging out.
XLS template is now pre-filled with projects for customer.
Removed Active Sprint from setup flow.
Fixes
Fixed a bug that made the Cycle Time chart disappear for users when the standard deviation for chart data was 0 (no chart was being returned).
“Add comment” now submits user-posted data to the back-end of Bloomfilter (NOTE: this does NOT add comments to Jira instance).
Limited look-back period for integration to the last twelve months. Was previously pulling from entire corpus of historical data.
We’ve previously talked about our Burn Confidence band, which measures team performance as compared to expectations in a static representation. However, the development lifecycle is constantly changing and requires teams to respond dynamically. We are excited to announce that our latest update to the Burn Confidence Band transforms the band into a dynamic forecasting tool based on a rolling sequence of burn data from past sprints.
We’ve previously talked about our Burn Confidence band, which measures team performance as compared to expectations in a static representation. However, the development lifecycle is constantly changing and requires teams to respond dynamically. We are excited to announce that our latest update to the Burn Confidence Band transforms the band into a dynamic forecasting tool based on a rolling sequence of burn data from past sprints.
In Sprint 22, two key features are in User Acceptance Testing (UAT): a new Summary page as the app home screen and an update to our frequently used feature, Sprint Performance.
.gif)
