Cook your product better - Story map and no estimate is the new recipe. This presentation is a case study of how we solved problems and made team think more about the product. Collaboratively, we looked at the roadmap and decided what to ship next to our beta customers and later to the market. We did not estimate but identified smaller goals and the team focussed on those goals and delivered.
did a lot of
Design studio is a team activity where a business scenario is shared and the team comes up with various ideas. They draw the user flow and then share it with the team. This helps the team understand what’s coming up and prioritized what’s MVP for that feature.
did story mapping
Feature / Story breakdown
For our velocitywe looked at number of cards which the team completed within a certain timeframe. That gave us “number of cards completed” per sprint.
we then summedthe number of cards per sprint on the story map wall and calculated projected velocity.
It was always better to start development than spend hours estimating. Velocity would anyways change
During our planning session we identified goals and focussed as a team to achieve those goals.
We identified two or three goals and prioritizedthem and we did a quick check every alternate dayon how are we doing on our goals.
all these helped us as it gave better clarity and control on what we want to deliver. This also helped as team was empowered and they started valuing product more than the numbers.