Sprint 21 focused on two exciting features: a new Summary page that will serve as the app home screen, and an update on Sprint Performance, our most frequently used feature. Building on the logic and data from the previous sprint, we populated these pages with valuable, data-driven content.
Sprint goal
We set a goal to populate the home page with our first iteration of the ‘Big Three Questions’ on the new Summary page (what are we building, how much will it cost and when will it be ready). We also wanted to be ready with a ‘Sprint Performance’ page concept that enhances the current sprint level view while also tackling navigation quirks for sprint history. We aimed to be more than halfway complete with renders of all planned content for each of these features.
What’s new?
The team progressed on the “Summary” home page. In this sprint we populated content for two of the big three questions (shown below):
What are we building?
How much will it cost?
One more question to go: When will it be ready?
Getting close to a completed Summary screen!
The team improved data retrieval and subsequent calculations of process metrics, including resolution of the system.
Updates
We’re making progress on an exciting update to the Sprint view! We will soon share our Pillars of Process (concept below): a sprint-level view to demonstrate the extent to which an individual sprint contributes to the key measures of a successful SDLC. Currently, we have completed about half the business logic for the page.
The Pillars of Process will be debuting with our updated Sprint Performance screen very soon!
We also updated our ‘first impression’ visuals. Both the sign in screen and our signature Performance Odometer (shown below) have new visuals. Users will recognize the odometer as the indicator that visualizes the SDLC performance at the portfolio, project/product, and sprint levels. The updated look helps the user focus on where their project stands.
We help the user focus on important elements by deemphasizing the color bands of the odometer that are not relevant to the outcome for the project!
What we fixed
We improved the handling of historical sprint snapshots so that users do not hit a dead-end when they click to view an issue in Jira that has been deleted.
We found and squashed a bug where jobs running behind the scenes would stop if they encountered a project or board that was previously used but had been deleted.
We added handling for cases when Jira Software returns null responses through our integration.
We also found and squashed a bug related to blocked tasks. In specific use cases, blocked tasks were still blocked after the sprint closed even if the issue was unblocked.
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.
