<aside> đź’ˇ This kit is a directory of resources to help you understand and execute product planning. Template directory is organised in several abstraction layers. Starting from high-level business perspective, and then gradually drilling down to technical details. Final result is a shared vision, development plan, roadmap, based on the knowledge from all the documents included.
</aside>
<aside> ℹ️ Why is this document important: clear scope is crucial factor for project success, and it is extremely important to have all team members and stakeholders aligned and aware of your goals and initiatives. Having your scope of work clear will provide a software that stakeholders and users need.
</aside>
This set of pages is a collection of information that will provide essential information for understanding what is the product that you are building and how to build it. Each section addresses one layer of abstraction, starting from high-level vision, all the way to detailed technical breakdown.
Product Vision Board is a high-level overview of the product (business layer). It provides product vision, description of the users, their needs and required features to fulfill those needs. This is a strategic document, that should be used as a guidance for setting goals and initiatives.
Platform Overview provides a description of business logic for each end to end scenario, or users’ journey for each role (information layer). This part should cover all starting and finishing point for each path that users needs to take, with all the steps in between (optimistic path and edge cases). This will help us to identify and cover as many cases as possible.
Functional Specification is a document that describes the application and all its features (application layer). These features should map exactly to the needs described in the platform overview document. Functional Specification contains feature description as well as high fidelity mockups and UX flows.
System Design is a set of tasks (tactics) to achieve the goals described in previous documents (technology layer). This part contains a list of all technical tasks, user stories and C-diagrams with architecture overview.
Roadmap is your timeline layer. The timeline will help us in setting milestones and measuring progress. This part is essentially a user story map, where we have each task associated to a sprint. This will provide a better insight into the project timeline, when and what will be delivered after each sprint.
Table Of Contents: