From Epic to Release, In One Hierarchy
Product teams lose time translating between a strategy deck, a backlog, and a delivery board. Keep all three as views of the same work, and the translation stops being a job.
Free forever plan · No credit card required · Set up in minutes
What is product management software?
Product management software connects what you have decided to build with what the team is actually building. Orangescrum does that with a single hierarchy of epics, features, stories, and tasks, so a strategic item can be opened and drilled into until you reach a task somebody is working on today. Around it sit prioritised backlogs, sprints, epic approvals, task dependencies with a critical path, and reporting on what you actually shipped.
Why product plans lose touch with delivery
Structure that survives contact with delivery
Epic, feature, story, task
Four levels of the same hierarchy, so a strategic item opens all the way down to the work in progress.
Prioritised backlogs
Keep a product backlog and pull work into sprint backlogs at planning, with story points and a sprint goal.
Epic approvals
Assign an approver to an epic and track it through Pending, Reviewing, Approved, or Rejected, so nothing large starts unagreed.
Dependencies that mean something
Finish to start, start to start, finish to finish, and start to finish, with circular dependencies blocked before they are saved.
Timeline and critical path
Give stakeholders a Gantt view of the same work, with milestones and the critical path highlighted.
Delivery reporting
Burndown, velocity, average age, resolution time, and planned against actual, built from real sprint data.
How a release takes shape
Product teams of different shapes
Which edition includes what
| Capability | CloudManaged SaaS | Self-HostedOn-premise / private cloud | Open SourceCommunity Edition |
|---|---|---|---|
| Epic, feature, story, and task hierarchy | Pro | ✓ | ✗ |
| Epic approval with a named approver | ✓ | ✓ | ✗ |
| Product and sprint backlogs | Pro | ✓ | ✗ |
| Story points, burndown, and velocity | Pro | ✓ | ✗ |
| Task dependencies (FS, SS, FF, SF) | ✓ | ✓ | ✗ |
| Gantt timeline and critical path | ✓ | ✓ | ✗ |
| Custom statuses and workflows | Pro | ✓ | ✗ |
| Scaled Agile (Essential SAFe) | Premium | ✓ | ✗ |
| Release management | ✗ | ✓ | ✗ |
| Resource and capacity across products | Premium | ✓ | ✗ |
Product management FAQ
Does Orangescrum have a product roadmap view?
Not as a separate roadmap module, and it is worth being precise about that. What you get is an epic, feature, story, and task hierarchy plus milestones and a Gantt timeline, so the roadmap item is the epic and it opens straight into the work underneath it rather than being a slide that goes stale.
How is an epic different from a project?
A project is the container and the permission boundary. An epic is a large piece of work inside it that breaks down into features, stories, and tasks, with its own progress rolled up from what sits underneath.
Can we require sign off before a big item starts?
Yes. An epic can carry a named approver and moves through Pending, Reviewing, Approved, and Rejected, with the change recorded and the approver notified.
Does it support both Scrum and Kanban?
Yes, and the method is set per project, so one product team can run sprints while another runs a continuous board in the same workspace.
Can I model dependencies properly?
Yes. All four relationship types are supported: finish to start, start to start, finish to finish, and start to finish. Circular dependencies are detected and blocked rather than saved, and the Gantt view highlights the critical path.
Can we manage several products at once?
Yes. Each product runs as its own project with its own backlog and sprints, and programme level views show epics and capacity across all of them.
Is there release management?
Yes, in the Self-Hosted edition, which has a release management module covering versions and release tracking. Cloud teams usually run releases as milestones on the timeline instead.
Which tools does it connect to?
Git Sync links GitHub and GitLab so commits and pull requests appear against the work, in both editions. Cloud adds Azure DevOps, and the Self-Hosted edition adds Jenkins. Bitbucket is built but not yet enabled. There is no Zapier connector.
What does it cost for a product team?
Flat monthly plans with unlimited users: 29 dollars Basic, 69 dollars Pro, and 349 dollars Premium. Epics, backlogs, and sprints are on Pro and above, and all of it is included in the Self-Hosted edition.
Connect the plan to the work
Epics, backlogs, and sprints are on the Pro plan and above. 14 day free trial, unlimited users on every plan.