--- title: "Use Cases: How Teams Run Their Work in Orangescrum" description: "Ten operational workflows, from sprint planning and bug triage to client onboarding and quarterly planning, each with roles, steps, and features." canonical: https://www.orangescrum.com/use-cases --- # Use Cases: How Teams Run Their Work in Orangescrum > For the complete documentation index, see [llms.txt](https://www.orangescrum.com/llms.txt). 10 workflows # How Teams Actually Use Orangescrum Ten workflows, written as instructions rather than claims. Each one names the people involved, the steps in order, and the part of Orangescrum that carries every step. [Start Free Trial](/sign-up?utm_source=website&utm_medium=usecases&utm_content=index_hero) [Start from a template](/project-templates) Unlimited users Flat pricing Cloud or self-hosted ## Building and shipping software4 Engineering, QA, and product teams working in iterations against a backlog. [ ### Sprint planning Turn a messy backlog into a committed sprint your team can actually finish. Who Scrum masters, product owners, engineering leads When Every one to four weeks ](/use-cases/sprint-planning)[ ### Bug triage Decide what gets fixed, by whom, and by when, without a two hour meeting. Who QA leads, engineering managers, support engineers When Daily or twice a week ](/use-cases/bug-triage)[ ### Product launch Coordinate engineering, marketing, support, and sales towards one launch date. Who Product managers, launch leads, marketing managers When Per release ](/use-cases/product-launch)[ ### Incident management Take an incident from first report to resolved, with the follow up actions tracked. Who Support engineers, on call engineers, engineering managers When Whenever something breaks ](/use-cases/incident-management) ## Serving customers3 Work that starts when somebody outside the team asks for something. [ ### Client onboarding Give every new client the same first thirty days, instead of whatever the account manager remembers. Who Account managers, delivery leads, onboarding specialists When Per new client ](/use-cases/client-onboarding)[ ### Campaign launch Run a multi channel campaign from brief to live, with the review cycles built in. Who Campaign managers, designers, content writers, media buyers When Per campaign ](/use-cases/campaign-launch)[ ### Content production Keep an editorial calendar moving, with a review stage that has to be passed. Who Content leads, writers, editors, designers When Weekly, against a monthly calendar ](/use-cases/content-production) ## Running the business3 Recurring internal processes with owners, approvals, and a deadline. [ ### Employee onboarding Get a new starter productive in week one, with IT, HR, and the hiring manager in step. Who HR, IT, hiring managers, buddies When Per new starter ](/use-cases/employee-onboarding)[ ### Quarterly planning Agree what the next quarter contains, and check the team can actually staff it. Who Heads of department, PMO, resource managers When Every quarter ](/use-cases/quarterly-planning)[ ### Vendor procurement Move a purchase request from raised to ordered, with the approvals on the record. Who Procurement officers, budget holders, finance, legal When Per request ](/use-cases/vendor-procurement) ## Every Page Follows the Same Shape So you can skim to the part you need, and so nothing on the page is a claim we cannot show you in the product. ### The scenario What is happening, how often it happens, and who is waiting on the result. ### Who is involved Each role, what they own, and what they see when they open Orangescrum. ### The workflow The steps in order, with a link to the feature that carries each one. ### What good looks like The signals that tell you it is working, plus where it usually goes wrong. ## Use Case Questions What is the difference between a use case and a feature page?+− A feature page describes one capability, such as the Kanban board or time tracking. A use case page describes a job a team does from start to finish, such as running a sprint or onboarding a client, and names which features carry each step of it. Do I need a different plan for each use case?+− No. Every Orangescrum plan includes unlimited users, and pricing is flat rather than per seat. Individual capabilities sit at different tiers, and each use case page says which ones it leans on. Can I run these on the self-hosted edition?+− Yes. The self-hosted edition runs on your own servers and includes several modules the cloud edition does not, such as document management, risk management, release management, and attendance and leave. Each use case page marks which editions it applies to. Do I have to set all of this up before I start?+− No. Every use case here starts from a project template, which sets the status workflow and default view for you. You can add custom fields, checklists, and reports once the basic flow is running. How long does one of these take to set up?+− Most take under an hour for the first project. The step by step on each page is written so one person can build it in a single sitting and invite the team the same day. ## Pick One and Build It This Week Start from a project template, follow the steps, and invite the team. Unlimited users on every plan. [Start Free Trial](/sign-up?utm_source=website&utm_medium=usecases&utm_content=index_cta) [Self-Hosted edition](/self-hosted) 14 day free trial. No credit card. Cloud or self-hosted. Ready to transform your workflow? Start your free project workspace today