--- title: "Agile Project Management Software | Orangescrum" description: "Run Scrum, Kanban, or both. Product and sprint backlogs, sprint planning, story points, epics, burndown and velocity charts, with a Gantt view for stakeholders." canonical: https://www.orangescrum.com/agile-project-management --- # Agile Project Management Software | Orangescrum > For the complete documentation index, see [llms.txt](https://www.orangescrum.com/llms.txt). [Home](/) / [Features](/features) / Agile Agile project management # Agile Project Management with _Scrum and Kanban_ Run the framework your team actually uses. Sprints and backlogs for Scrum teams, boards for Kanban teams, and a timeline for the stakeholders who need dates. 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=agile-project-management)[Book a Demo](https://calendly.com/orangescrum) Free forever plan · No credit card required · Set up in minutes ## What is agile project management? Agile project management delivers work in small, frequent increments instead of one large release, so teams can adapt as they learn. Orangescrum supports it end to end with product and sprint backlogs, sprint planning with story points, epics, Kanban boards, and burndown and velocity charts, while still giving stakeholders a Gantt view of the overall plan. The problem ## Why agile _gets messy in tools_ The tool forces one method The team runs Kanban but the tool insists on sprints, or the reverse. ✓ Scrum, Kanban, or both, per project. Stakeholders want dates Leadership asks for a timeline the board cannot give them. ✓ A Gantt view over the same work, without extra admin. Velocity is anecdotal Nobody really knows how much the team delivers per sprint. ✓ Burndown and velocity built from actual sprint data. What you get ## Everything a _Scrum or Kanban team_ needs The full agile surface, grouped the way the product is: backlog, sprint, board, estimation, work items, and reports. 01Backlog - ### One list, every sprint The unscheduled backlog and each planned sprint sit in the same list, so planning is drag and drop rather than screen hopping. - ### Six ways to group Group the backlog by sprint, status, workflow status, epic, assignee, or priority. - ### List view and tree view Read it as a flat list, or as a tree from epic down through feature and story to subtask. - ### Nine filters Filter by epic, quick filter, assignee, type, status, priority, due date, start date, and last update. - ### Cascading filter options Option lists narrow to what the other filters already match, so you never pick a value that returns nothing. - ### Saved views and search Save a named set of filters for the team, and search the backlog by free text at any time. - ### Sort or rank by hand Sort by nine fields, or switch to manual and drag items, epics, features, and whole sprints into order. - ### Edit in the row Change title, points, estimate, priority, due date, type, assignee, and status without opening the item. - ### Act on many at once Select rows and set a status, move them to a sprint, or archive them in one action. - ### Import epics from CSV Upload a file, preview exactly what will be created, then confirm, with a sample file to start from. 02Sprint - ### Plan, start, and close Create a sprint with a goal and dates, start it when the team commits, and close it when it ends. - ### Durations and working days Pick one, two, three, or four weeks or set your own, and see the working days left after weekends and company holidays. - ### Decide where leftovers go On close, send unfinished work to the backlog, to the next sprint, or to a new sprint created for it. - ### Reopen a closed sprint If a sprint was closed too early you can reopen it rather than rebuilding it by hand. - ### Run more than one at a time A company setting allows parallel sprints, or keeps teams to one active sprint per project. 03Board - ### The active sprint board To Do, In Progress, In Review, and Done, with In Review appearing when your workflow has a second in progress status. - ### Swimlanes Turn the board into lanes by epic, assignee, or sprint, and collapse the lanes you are not working in. - ### Board, list, or timeline The same sprint reads as a board, a sortable list, or a timeline, without moving the work. - ### Filter by person A row of team cards shows each person's To Do, In Progress, and Done counts, and clicking one filters the board. - ### Epic, feature, and Scrumban boards Separate boards for epics and features, plus a backlog board with swimlanes, on the Premium plan and in Self-Hosted. 04Estimation - ### Story points Type any number or tap the Fibonacci presets 1, 2, 3, 5, 8, and 13. - ### Hour estimates Enter time as HH:MM, as 2.5, or as 2h 30m, with presets from fifteen minutes to a full day. - ### Pick the unit that counts Roll sprints up by story points, by estimated time, or by task count, and every total follows your choice. 05Work items - ### Epic, feature, story, subtask A real hierarchy with typing rules, and subtasks nested up to three levels deep. - ### Defects in the plan Turn on defect planning and defects from test management appear in the backlog and can be ranked with everything else. - ### A method per project Set Scrum, Kanban, or simple per project, and the labels, boards, and reports change to match. 06Reports - ### Sprint report Planned against completed for tasks, points, and hours, plus a per person breakdown of what each member finished. - ### Velocity Committed against completed for every closed sprint, with an average, shown in points, tasks, or hours. - ### Burndown Planned, completed, and remaining work for a sprint, against the ideal line. - ### Export the sprint Download the sprint report as a PDF for anyone who needs it outside the tool. - ### The wider project set Planned versus actual, average age, resolution time, created versus resolved, time since, pie chart, and due date changes. - ### Probabilistic forecast A Monte Carlo forecast of when the remaining work will finish, based on your own recent throughput. Self-Hosted only. How it works ## How a _sprint runs_ 1 Groom the backlog Keep the product backlog prioritised and estimated. 2 Plan the sprint Pull work into the sprint, agree the goal, and commit. 3 Run the board The team works the sprint board and burndown tracks progress. 4 Review and improve Close the sprint, capture velocity, and feed it into the next plan. Who it's for ## Agile for _different teams_ Software teams Full Scrum with backlogs, sprints, story points, and burndown. [Learn more →](/solutions/it-project-management-software) Marketing teams Kanban for continuous delivery of campaigns and content. [Learn more →](/solutions/marketing-project-management-software) Scaling organisations Several teams delivering together with Essential SAFe. [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. Agile framework and sprints are on Pro and above, and in Self-Hosted. The Community Edition has no Scrum module. | Capability | CloudManaged SaaS | Self-HostedOn-premise / private cloud | Open SourceCommunity Edition | | Kanban boards | ✓ | ✓ | ✓ | | Agile framework and sprints | Pro | ✓ | ✗ | | Backlog with group by, filters, and saved views | Pro | ✓ | ✗ | | Epics, features, and stories | Pro | ✓ | ✗ | | Sprint board with swimlanes and timeline | Pro | ✓ | ✗ | | Story points and estimation rollups | Pro | ✓ | ✗ | | Parallel sprints and carry over rules | Pro | ✓ | ✗ | | Epic import from CSV | Pro | ✓ | ✗ | | Sprint, velocity, and burndown reports | Pro | ✓ | ✗ | | Planned versus actual, average age, resolution time | Pro | ✓ | ✗ | | Epic, feature, and Scrumban boards | Premium | ✓ | ✗ | | Monte Carlo completion forecast | ✗ | ✓ | ✗ | | Scaled Agile (SAFe) | Premium | ✓ | ✗ | Frequently asked questions ## Agile project management _FAQ_ ### Does Orangescrum support Scrum? Yes. Orangescrum has full Scrum support with product and sprint backlogs, sprint planning, story points, sprint boards, and burndown and velocity charts, so a team can run every ceremony in one tool. ### Does it support Kanban as well? Yes. You can run Kanban on its own with custom workflow columns, or alongside Scrum. Kanban boards are available in every edition including the free Community Edition. ### Which plan includes sprints? The agile framework, sprints, epics, and backlog management are on the Cloud Pro plan and above, and are included in the Self-Hosted edition. ### What can I group and filter the backlog by? You can group by sprint, status, workflow status, epic, assignee, or priority, and filter by epic, assignee, type, status, priority, due date, start date, last update, and a quick filter for starred, assigned to me, or unassigned work. Filter options cascade, so you only ever see values that will return results, and a filter set can be saved as a named view for the team. ### What is the Scrumban board? It is the epic and feature board set. Epics and features get their own boards, and there is a backlog board that shows the whole backlog as status columns with swimlanes. It is available on the Premium plan and in the Self-Hosted edition. ### Can I use agile and Gantt together? Yes. The Gantt chart is a different view of the same work, so the team can run sprints while stakeholders see a timeline, with no duplicate admin. ### What agile reports are included? Three sprint reports come with the agile module: a sprint report with a per person breakdown and a PDF export, a velocity report showing committed against completed, and a burndown. Alongside them the project reports cover planned versus actual, average age, resolution time, created versus resolved, time since, a pie chart breakdown, and due date changes. The Self-Hosted edition adds a Monte Carlo forecast that predicts a finish date from your own recent throughput. ### How do you estimate work? In story points, in hours, or by task count. Story points take any number or the Fibonacci presets, hours accept HH:MM, decimals, or shorthand such as 2h 30m, and you choose which of the three every sprint total rolls up in. ### Can different teams use different methods? Yes. One project can run Scrum while another runs Kanban, in the same workspace, because the method is set per project, and the labels, boards, and reports follow that choice. ### Can we run two sprints at the same time? Yes. A company setting turns on parallel sprints. Leave it off and each project keeps a single active sprint, which is the usual Scrum rule. ### What happens to work that does not finish? When you close a sprint you decide where it goes: back to the backlog, into the next sprint, or into a new sprint created for it. The choice can be saved as the team default. ### Does it scale beyond one team? Yes. Scaled Agile with Essential SAFe support is available on the Premium plan and in Self-Hosted, adding release trains and Program Increments. ### How many users can I add? Unlimited, on every plan. Adding the whole team, plus clients or stakeholders, does not change the price. ## Run agile the way your team works Sprints and the agile framework are on the Pro plan and above. Kanban is in every edition, and every plan includes unlimited users. [Start Free Trial →](/sign-up?utm_source=website&utm_medium=feature&utm_content=agile-project-management_cta)[Book a Demo](https://calendly.com/orangescrum) ## Related capabilities [Kanban boardsVisual boards for daily work](/kanban-board)[Scaled AgileEssential SAFe for many teams](/scale-agile-project-management)[Gantt chartTimeline for stakeholders](/gantt-chart)[Test Case ManagementQuality inside the sprint](/test-case-management)[Agile explainedScrum, Kanban, and how to choose](/agile)