1. The Problem
In the course of every sprint, a Product Manager is required to hold several concerns simultaneously: what must be ideated, what requires engineering alignment, what needs testing, and what demands release notes once a feature has shipped. These responsibilities seldom reside in a single place. Under pressure, they are often neglected, addressed belatedly, or handled inconsistently. The resulting cognitive burden, though not acute, remains persistent.
<aside> 💡
Check the project here: https://rchin6454.github.io/PM-Sprint-Board/
See the video here: https://drive.google.com/file/d/1fNeLEwK1NASEKreMdIMBN9D1wH73FPQX/view?usp=drive_link
</aside>
2. What Was Built
A lifecycle planning tool that accepts sprint data as input and presents a daily view of the actions a Product Manager must take across seven distinct phases:
The tool calculates each story's active phase window by working backwards from the sprint's start date. On any given day, the Product Manager may open the tool and see precisely which stories require attention, and at what stage. It functions not as a task list, but as a day-specific map of where attention is due.
Each story progresses through the phases as a card upon a board, and may be advanced or reverted manually. Upon a story's arrival at the Release phase, the tool prompts the user to draft release notes and record a demonstration video.
3. Approach
The sprint lifecycle was mapped from the Product Manager's vantage point, rather than the engineer's. This revealed seven recurring junctures at which tasks are most commonly overlooked, and the tool was built specifically around them.
4. Technical Notes