Team growth, an NYC conference, and product enhancements — this sprint had it all
TL;DR
Sprint 18 was a whirlwind of team growth and product enhancements. We onboarded new team members, held a successful All-Hands in Akron, and exhibited at the New York Product Conference. On the product side, we introduced user-friendly features, improved visual representation, and enhanced security measures.
Sprint goal
Sprint 18 was unique in that most of our focus was outside the product. We welcomed two new developers, a customer success leader, a design leader, and our very first company intern. The team also met for a three-day All-Hands in Akron and showcased Bloomfilter at the New York Product Conference (Product Collective).
What’s new
Customer facing
We implemented failure screens for 500 (server error) and 404 (file not found) errors, and provided self-service assistance to users encountering these common web application issues.
Non-working days now have visual representation on charts. Previously, all days on Bloomfilter looked the same, which were misleading and made progress appear flat. We added a light gray shade (see 04/01 through 04/03) to make users aware of non-working and closed-office days.
Light grey shading was added to indicate non-working days.
Non-customer facing
We upgraded Bloomfilter to Mantine 6.0, a key tool we use to manage our React library. This upgrade gives us more design flexibility as we gear up for our next series of data visualizations and user interactions.
Updates
Customer facing
We added labels to the axes and legends to our Burn charts (for current and historical sprints). Now, users have more control over which elements appear in the charts.
Legends now appear at right and axes are labeled.
Non-customer facing
We tightened our security defenses to further protect against attacks via the “Forgot Password?” experiences.
What we fixed
We improved the user experience when navigating between Jira boards for projects on Bloomfilter. Users are now presented with an alphabetical listing of all project boards integrated with Bloomfilter, removing the previous dead-end experience.
Log-in functionality is now working for Safari browsers.
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.
