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.
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
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
Product launch
Coordinate engineering, marketing, support, and sales towards one launch date.
- Who
- Product managers, launch leads, marketing managers
- When
- Per release
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
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
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
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
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
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
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
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?
Do I need a different plan for each use case?
Can I run these on the self-hosted edition?
Do I have to set all of this up before I start?
How long does one of these take to set up?
Pick One and Build It This Week
Start from a project template, follow the steps, and invite the team. Unlimited users on every plan.
14 day free trial. No credit card. Cloud or self-hosted.
Ready to transform your workflow?