Product Roadmap
This document outlines the guiding principles and structure of our product roadmap. Please read this document before requesting new features or enhancements. MikroCloud loosely follows the Scrum framework. Ideas from users are added to the product backlog.
Structure of the Roadmap
- The roadmap only contains epics.
- Each epic has its own dedicated storyboard. Storyboards are not open to the public.
- The storyboard delves into details like user stories, specific functionalities, and tasks for that particular epic.
- Epics should be laid out in a logical sequence based on their importance, dependencies, and strategic alignment.
Guidelines for Adding Epics
-
Clarity: Ensure that each epic clearly describes the objective and expected outcome. Avoid technical jargon unless necessary.
-
Brevity: Epics should be concise. Details, user stories, and specific functionalities will reside within the storyboard of that particular epic.
-
Value Proposition: Epics should be aligned with our product's mission. Always ask if the epic enhances our core value to the MikroTik community.
-
Security First: Given our product's emphasis on security, any epic involving data or MikroTik operations should prioritize security implications.
-
Stakeholder Involvement: Before finalizing an epic, ensure that relevant stakeholders, be it from the technical, marketing, or sales team, have had the opportunity to provide input.
-
Dependencies: Always consider dependencies. If an epic depends on another, this should be clearly indicated and planned for in the overall roadmap timeline.
Feedback and Collaboration
Your input is vital. If you have suggestions, ideas, or feedback on the roadmap or a particular epic, please share them with the product team. Collaboration is key to refining our path forward.