This is the second of two concurrent releases aimed at shipping a new architecture in order to support assigning multiple boards to a single project.
Our product leader, Bill, compared this sprint to "expanding the bellows" of an accordion. It's a (strange) but accurate metaphor that captures how we paid off some technical debt and shipped customer feedback-driven items over these last few releases, giving us a bit of slack to shift away from a "run" or "maintain" cycle and back to a "build" cycle.
What's New?
Multi-board architecture. Users now have the ability to associate more than one active board per project in configuration. Now, users can see key stats like throughput, lead time, and velocity at the project level and at the board level. Customers who run their dev, design and QA on different boards may now rejoice!
Users can now use the Board dropdown selection to view statistics by board instead of only at the project level.
Chart Export. We now support chart export to PNG for Sprint Analysis charts (burnup, burndown, cumulative flow). This was in response to multiple customers wanting an easy way to get a clean chart image to include in presentations outside of Bloomfilter.
The icon in the upper right corner of Sprint charts initiates a PNG export.
Enhancements
Added hover-state text to navigation elements. We received feedback that users had trouble understanding what icons represented when using the navigation menu in collapsed mode. We added hover state text to make it easier for the user to discern.
Sprint Day 0 is now plotted on charts to represent sprint starting point. Previously our sprint charts did not plot a point on the charts at the start of the sprint. It made it look like nothing was happening on the chart. Now users can see where they are starting from when the sprint begins.
Renamed “Available Work Days” metric to “Work Days Planned” for clarity. The label on this metric caused universal confusion. It is now labeled “Work Days Planned” and includes sub-text that further describes what it means to plan work (backlog items are ready for development).\
“Available Work Days” has been changed to “Work Days Planned”.
Trimmed project name labels on the History screen. Without wrapping, some users experienced overlapping text horizontally when scrolling through their sprint history. The screen now wraps at a defined character limit to address this.
Added a spinning indicator for loading interactions. The user did not see any instant feedback in instances where, after making a selection, a short delay would occur while the system was processing the user’s request. We added a spinning animation to indicate “loading” is taking place.
Division of Cost chart heading now reflects the selected project. Users now see the title of their selected project instead of a generic “Division of Cost” title for the table.
Title of the table now indicates the selected project “Sunset Aurora v22” for clarity.
Fixes
Fixed an issue where the Performance Score calculation load flickered an “F” grade before loading the calculated score. This was due to the calculation beginning at a 0 value on initial load.
Fixed an issue where the Work Days Planned calculation was reporting deeper backlogs than it should have.
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.
