Scrum and Kanban.
Built around the principles.

Purpose-built workspaces grounded in the Scrum Guide and Kanban University’s guide. Plan Sprints, manage flow and put the principles into practice.

Scrum / Sprint planning

A goal. A plan. A shared direction.

Paper folios connect a Sprint Goal with selected Product Backlog items.

Kanban / Workflow

See the work. Make room to finish.

Kanban paper board with Ready, In progress and Review columns and explicit WIP limits.

Spend less time piecing work together.

Keep the context your team needs close to the decisions it makes every day.

Know why the work matters.

See the shared goal behind selected work.

Know when to pull more.

See available capacity before starting another item.

Decide the next step together.

Use shared priorities and feedback to adapt the plan.

Scrum

Make room for the Sprint Goal.

Keep the Product Goal, ordered backlog and Sprint plan connected.

Wipkin Sprint Backlog preview showing a Sprint Goal, selected work and delivery steps.

01 / Product Backlog

Give priorities a shared home.

Keep the Product Goal and ordered backlog in view.

02 / Sprint

Plan and adapt together.

Bring the Sprint Goal and selected work into one plan.

03 / Inspect and adapt

Make progress meaningful.

Use events and Increments to inspect and adapt.

Kanban

Make room for the work to flow.

Make your workflow, policies and work-in-progress limits visible.

01 / Workflow

Show how work really moves.

Shape columns around the way your team works.

02 / Work in progress

Make capacity a shared decision.

Set WIP limits and keep blocked work visible.

03 / Flow report

Learn from the work.

Review flow measures using defined Start and End points.

Wipkin Kanban preview showing swimlanes, blocked work and shared capacity limits.

Your team defines the workflow; new Kanban projects have no preset columns or work items.

Built for organizations

Separate projects. One organization.

Bring Scrum and Kanban projects together while keeping project access separate.

Northstar Studio organization with separate Scrum Website launch and Kanban Customer Portal folders.

01 / Choose

One method per project.

Select Scrum or Kanban when you create the project. Each has its own workspace and practices.

02 / Invite

Bring the right people in.

Keep organization membership and access to private projects separate.

03 / Collaborate

Give teams a shared context.

Use one account across the organizations and projects you are authorized to access.

From principles to practice

See the principles in the workspace.

01

Sprint Goal → a shared purpose

Keep the Sprint Goal beside selected work so the team can inspect progress toward a shared outcome.

02

Definition of Done → shared quality

Keep the Definition of Done accessible when checking whether work forms part of a usable Increment.

03

WIP limits → visible capacity

Show work against the agreed limit, including waiting and blocked items, before pulling more.

04

Flow measures → evidence for improvement

Use recorded work events to review throughput, cycle time and work-item age.

Practical questions

Before you get started.

How large can a Scrum Team be?

Wipkin supports up to 10 people per Scrum Team. This is a Wipkin product limit.

What happens after beta?

Team will cost $14 per person per month with a 14-day trial. Organization has custom pricing. Self-hosted is planned. See Pricing for the options and current details.

Could our beta data be deleted?

Yes. Keep a separate copy of important work and do not use beta as your only record. Read the Beta page for details.

Give your team a home for its work.

Bring your goals, work and working agreements together in Wipkin.

Get started