<aside> 💡 This document contains a high level delivery plan with proposed delivery milestones - versions. Each version has a “What’s on the box” section which describes what will be delivered to end-users, with emphasis on outcomes rather than outputs. Also, there’s a list of objectives and tasks required to achieve the goal for each version.
</aside>
<aside> ℹ️ Why is this document important: The document will be used as a development guide, ensuring the team is always working on high-value - high-priority tasks. Also, this will help us keep track of the progress and measure success.
</aside>
<aside> 💡 An outcome-driven roadmap provides context for specific items on the roadmap and their prioritisation while simultaneously ensuring that the product strategy is both communicated and consistently pursued. Everything is there for a reason, the reason is well understood, and the goal is measurable.
</aside>
The first step in creating outcome-driven roadmaps is to pile up all the features, which you already did in your System Design, writing down and . Then, organise the pile into topics and themes. After you have a collection of themes, try to formulate an expression that will reflect the outcome for the users, as if the feature has been implemented.
<aside> ➡️ Outcome oriented planning will give you flexibility to solve problems rather than to build specific feature without the end goal in mind.
</aside>
When formulating the outcome, put yourself in user’s shoes and ask “what can I do with this set of features once it is completed?”. The answer to that will give you the outcome statement. Also, these outcomes should map to the needs and business process defined in the Platform Overview doc. Furthermore, that you previously defined will have detailed description what needs to be created, so include them in outcomes for reference.
The next step is to prioritise these outcomes. There are numerous ways to prioritise, and the criteria will heavily depend on the business goals defined in the Product Vision Board document.
One of the dimensions you can use is Impact vs. Effort matrix. Distribute your user stories and outcomes in these four dimensions. Tackle major projects first since they have the highest value for your users. Focus on quick wins as well, to easily show progress. Use fill ins when you have extra time in your schedule and avoid "not worth it" category.
<aside> 🍒 Cherry on the top. You did an amazing job gathering all the information, understanding your users, aligning with your team and stakeholders, creating a bullet proof architecture. Finish it up with a great delivery plan.
</aside>
<aside> ➡️ Delivery plan will help you, your team and your stakeholders to understand what is the plan and what's the progress. Based on your prioritisation, organise your roadmap into versions. Try to give an inspiring version name, so that everybody gets hyped about it. Also, version names will help you communicate your milestones. Each version should have a living list of work items planned for each iteration. Milestones will include the dimension of time. Finally, one important thing is to describe the goal for each version. That statement will improve the focus of the team, where everyone included should contribute to the shared goal.
</aside>
<aside> 💡 Delivery plan is a living thing. You will update it as you go. But it's important piece of this kit, since it will be used as a tool to align and inform all parties involved. This will help the development team to understand what needs to be built and when. Also, stakeholders will have a preview of the progress. And ultimately, this will help you be more organised and in control.
</aside>