Each roadmap project in Korl has attributes that track key pieces of information about the project. These attributes focus on information that is important when communicating to internal or external stakeholders. They are organized into several categories:
| Project Overview | |
|---|---|
| Project name | The internally-facing name for the project |
| Internal summary | A 1-3 sentence internally-facing description of what the project delivers |
| Owner | The person most directly responsible for the project’s delivery (usually a PM) |
| Team | The development team building the item |
| Dev link | The URL for the epic, project, or issue where development status is tracked
Treated as a “Synced source” if other attributes are configured to sync from Jira or Linear |
| Project doc link | The URL for a document (e.g. PRD, product brief, 1-pager) describing the project
Treated as a “Synced source” if other attributes are configured to sync from the project doc |
| Design links | The URL(s) for files that detail project designs |
| Priority | How important the project is to deliver
Choose from: P0, P1, P2, Backlog |
| Themes | The strategic focus area(s) to which the project aligns
Values are configurable |
| Goals | The business objective(s) to which the project aligns
Values are configurable |
| Target personas | The user persona(s) or role(s) the project is intended to benefit most
Values are configurable |
| Project images | Visual assets that help explain the item
.jpg, .png, .jpeg, .webp, .gif |
| Critical user journey | The in-product steps a user takes to address the core need this project targets |
| Release Status | |
| Stage |
Choose from: Not Started, Defining, Developing, Validating, Released |
| Eng start | The date when the project’s development is expected to begin or began |
| Eng complete | The date when the project’s development is expected to complete or completed |
| Release | The quarter, month, or exact date when the project is expected to or did release to end users |
| Status | The confidence level that the project will release to end users on the Release date
Choose from: Released, On track, At risk, Off track, In backlog |
| Status update | Comments about how the project is progressing |
| External Positioning | |
| External visibility | Whether the project can be shared with external stakeholders, such as customers
Choose from: Okay to share, Requires NDA, Do not share |
| External name | The externally-facing name for the project |
| External description | A 1-3 sentence externally-facing description of what the project delivers |
| Customer impact | A 1-3 sentence externally-facing summary of how the project benefits end users |
| Shareable timeframe | Whether the Release date can be shared externally, and if so, at what granularity
Choose from: None, Release Quarter, Release Month |
| Shareable media | Visual assets added to Project images that are tagged as “Externally shareable” |
