Hackathon 2025 — Quarterly Reports
This project emerged unexpectedly, we hadn’t planned it as a hackathon, but once we dove in, the momentum carried us forward. After three days, we had a complete working version ready to go.
Backstory
As part of our commitment to transparency at Juice Box Monkey Designs, we began sharing our scrum reports last year to showcase our work. We want to demonstrate our workload and processes so others who are just starting out can learn from how we track and grow our business.
Rather than posting quarterly metric articles, this hack aimed to build Quarterly Reporting directly into our website.
Hackathon
This hack emerged organically without formal planning, unlike our usual approach. Since we already had most of the design completed, we divided the implementation into manageable pieces and started coding right away.
The phases
The designs
Having used scrum at JBMD for many years, we’ve accumulated extensive historical data to display. This system allows us to showcase both existing and upcoming reports, with tracking throughout the year and easy access to reports across different years.
The hack
Day 1 — 12 hours
Before starting, we reviewed the design and began working on individual components of the Report Quarter Page.
Outcome:
- Finished off the Sprint metrics component
- Finished off the Epic metrics
- Built out the articles link section of the page
- Built out the dynamic display of other quarters at the bottom of the Quarter page. The system checks the current quarter and displays only completed quarters from the same year.
Day 2 — 10 hours
We completed the final components of the Report Quarter page and began work on the Year report page. This phase involved experimenting with several new libraries.
Outcome:
- We reused the component used inside the Quarter report like epic and sprints
- Built out chartJS support for ticket types using a donut graph 🍩
- Created a new in progress view for when you hit a year report that isn’t quite done yet
- Built out new modal popups for explaining scrum terms like what epics are, sprints and ticket breakdowns.
- Built out new modals popups for explaining epics and what we did during that quarter or year (depending on where you are opening them)
Day 3 — 6 hours
On Day 3, we simplified the yearly list design to reduce crowding and better align with our Quarterly Reports views. We also enhanced the reporting functionality with additional features.
Outcome:
- Year List Progress Page build out
- Banners with content links to other places on site
- Quick buttons to go back quickly throughout reporting
- Starting some of the stretch goals but not finishing any of them within the third day
Stretch Goals + Content — 8 hours
Over the following days, we completed the remaining tasks. We finished all stretch goals while gathering the necessary data to populate the reports, which involved collecting years of historical reports and epics.
Outcome:
- Built out dynamic loading years of data (using a combination of local and s3 loading)
- Built out Goals inside Year Report page
- Added a quarter breakdown inside Ticket Breakdown section
- Collected 5 years of epics, goals and ticket information for JBMD
Summary Wrap Up
We are really excited to be more transparent for our business and this hackathon built out all the things required to tackle this. And we look forward to updating the report with Quarter 2 as we are able to wrap it up this sprint!
Check it out here
Want to see individual years, check it out here: 2024 ,2023, 2022, 2021.
If you liked this or want to know anything more about this, please reply and like this post. It means we are doing something right!
