Hey there! So, a few months back, we kicked off On-call with some cool features, just scratching the surface of what we envision for the product. Like many other companies, we like to plan our product roadmaps on a quarterly basis. However, On-call being a new product, brings in a lot of uncertainties.
To tackle this, we recently had a dedicated week where our team paired up to scope out key upcoming projects in our roadmap. The main aim was to turn those big ideas into solid project plans that we could confidently commit to, ensuring a sensible delivery order.
But why did we do this? Well, our roadmap themes were initially quite vague, making it hard to estimate the effort needed or the value it would bring. We identified a few recurring issues like under-scoping work, inaccurate estimates, and poor project sequencing.
During the scoping week, we collaborated to create a roadmap that combined our product and customer knowledge, aligned with our long-term goals, and was technically feasible. This required focus, hence the dedicated scoping week for the whole team to look ahead.
Our main goal was to move from vague ideas to precise plans, defining both the product and technical aspects. We picked four themes to scope that we believed would boost the usage of our on-call product. Each pair was tasked with creating a proposal, estimating engineering days, and outlining clear next steps for immediate project kick-off.
The scoping week was a success, resulting in a detailed roadmap that got the team excited for the upcoming quarter’s work. The collaborative effort between product, design, and engineering functions led to better outcomes and a more integrated project delivery. This process has set a new standard for our project planning, and we can’t wait to see the impact it will have on our future work.
In three months, we’ll reflect on the success of this approach and see how well we executed our plans. Stay tuned for more updates! 🔥
