---
title: "Product Management Software | Orangescrum"
description: "Run a product from idea to release. Epics, features, stories, and tasks in one hierarchy, sprint backlogs, epic approvals, dependencies, and release tracking."
canonical: https://www.orangescrum.com/product-management-software
---

# Product Management Software | Orangescrum

> For the complete documentation index, see [llms.txt](https://www.orangescrum.com/llms.txt).

[Home](/) / [Features](/features) / Product Management

Product management software

# 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.

Available in[Cloud](/pricing "Cloud - included")[Self-Hosted](/self-hosted "Self-Hosted - included")Open Source

[Start Free Trial →](/sign-up?utm_source=website&utm_medium=feature&utm_content=product-management-software)[Book a Demo](https://calendly.com/orangescrum)

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.

The problem

## Why product plans _lose touch with delivery_

The roadmap and the backlog disagree

The roadmap is a slide, the backlog is a tool, and by the second month they describe different things.

✓ One hierarchy, so the roadmap item is the epic.

Nobody can answer how far along an epic is

Progress on a large initiative is estimated by asking three people and averaging.

✓ Epic progress rolled up from the stories and tasks underneath it.

Big items start before they are agreed

Work begins on a major initiative that stakeholders had not actually signed off.

✓ An epic approval step with a named approver.

What you get

## 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 it works

## How a release _takes shape_

1

Shape the epic

Write the initiative as an epic, assign an approver, and get it agreed before work starts.

2

Break it down

Features and stories underneath, estimated and prioritised in the backlog.

3

Plan and build

Pull stories into sprints, work the board, and let epic progress roll up on its own.

4

Track the release

Milestones and the Gantt view for stakeholders, and reporting on what really shipped.

Who it's for

## Product teams _of different shapes_

Software product teams

Backlog, sprints, defects, and releases without three separate tools.

[Learn more →](/agile-project-management)

Several products at once

Portfolio level view of epics and capacity across products.

[Learn more →](/program-management-software)

Scaling past one team

Essential SAFe with release trains and Program Increments.

[Learn more →](/scale-agile-project-management)

Availability

## Which edition includes _what_

Orangescrum runs as managed cloud, self-hosted on your own servers, or as the open-source Community Edition. Here is exactly what each one includes.

Backlogs and the agile framework are on Cloud Pro and above. Release management is Self-Hosted only.

| 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 | ✓ | ✗ |

Frequently asked questions

## 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.

[Start Free Trial →](/sign-up?utm_source=website&utm_medium=feature&utm_content=product-management-software_cta)[Book a Demo](https://calendly.com/orangescrum)

## Related capabilities

[Agile project managementSprints, backlogs, burndown](/agile-project-management)[Scaled AgileEssential SAFe for many teams](/scale-agile-project-management)[Gantt chartTimeline and critical path](/gantt-chart)[Release managementVersions and releases, Self-Hosted](/release-management)