Scrum or Scrumban?

Introduction

Choosing whether to create a “Scrum” based or a “Scrumban” based project is one of your first decisions points, when you create a project in ScrumDo.

If you are doing traditional Scrum then a “Scrum” project should be the right fit for you.

Generally speaking, Scrum projects work best when you want to have a fixed cadence of time in which you want to deliver work regularly. Work is more or less defined by a product owner and accepted & delivered by a mature team.

Scrumban project incorporate Kanban practices such as continuous flow.

Again generalizing, Scrumban projects work best when you have less defined pieces of work to be done.

This page aims to help you understand some of the differences between the two types of projects in ScrumDo.

Comparison Matrix

	Scrum Projects	Scrumban Projects
Iterations or Sprints	Yes	Optional
Cadence	Planning and release tend to be synchronized	Not necessary for planning and release synchronized
Reporting	Burndown / Burnup charts	Continuous flow diagrams & Lead time histograms
Emphasis On	Story Points & Velocity	Work in Progress & Lead Time
Planning	Velocity to predict future progress	Calculations based on observed lead time to predict future progress
Work flow	Single, customizable work flow per project	Multiple custom work flows per project.
Visual Board	Simple, easy to use, status board.	Fully configurable Kanban board.
Work Breakdown	Epics, Stories & Tasks	Epics, Stories & Tasks
Conversion	Can be converted to Scrumban Project	Can NOT be converted to Scrum Project

Help Topics

General

Account & Subscription

Scrum Projects

Scrumban Projects

Scrum or Scrumban?

Introduction

Comparison Matrix