Korieo Community Docs
Roadmaps
Use roadmap structure to connect objectives, themes, epics, features, and delivery evidence.
Roadmap concepts
A Korieo roadmap should show the relationship between product intent and planned work. It is most useful when each item can be traced back to Product Truth and reviewed as product context changes.
Themes, objectives, epics, and features
- Themes group related product investments.
- Objectives explain the outcome the team is pursuing.
- Epics organize larger bodies of work.
- Features describe customer-facing or workflow-facing capabilities.
Connect roadmap items to Product Truth
Every roadmap item should point to the objective, problem, decision, or constraint that justifies it. This creates a practical review path when priorities shift.
Avoid roadmap drift
- Review roadmap items when product objectives change.
- Remove or revise items that no longer support current Product Truth.
- Use repository signals as evidence of movement, not as the complete product narrative.
Review and maintenance cadence
Review roadmap structure at a regular cadence such as weekly during active planning and monthly for broader alignment. Update Product Truth first when the underlying strategy changes.