framework

InspectAdapt

WHAT'S SCRUM ABOUT?

Scrum is an agile, incremental development method. With each increment the team delivers a potentially usable product. Changes in requirements can flow into the project in a controlled manner.

The focus is on the self-organisation of the team. The Scrum Master provides support to enable trouble-free work.

The development team does not need a project manager. The Product Owner, as the person responsible for the product, takes over the technical requirements and defines, prioritizes and adjusts them if necessary. The rules of Scrum contribute to transparency and trouble-free development cycles (sprints).

WHAT'S KANBAN ABOUT?

STOP START - START FINISHING

KANBAN is a procedure that reduces the number of parallel operations, the Work in Progress (WIP), during the flow of a value-added chain and thus achieves faster throughput times.

This quickly makes problems, especially bottlenecks, visible.

Kanban comes from lean production and became known through its use at Toyota. In the meantime, the procedure has been adapted to software development and organizational processes.

Kanban is a wonderful tool for visualizing personal tasks as well as for structured and focused processing of one's own tasks.

COMPARISON OF SCRUM & KANBAN

SCRUM

  • Iterations of equal length are mandatory.
  • Team agrees on a certain amount of work to be done in the next sprint.
  • Velocity (team speed) = base metric.
  • Teams are to be put together cross-functionally.
  • Requirements must be met within a sprint.
  • Burndown charts are used as metrics.
  • Indirect WIP limitation due to the limited amount in the sprint. Optional WIP limitation within a sprint.
  • Estimates are mandatory.
  • No new requirements in the current sprint.
  • Three prescribed roles (Product Owner, Scrum Master, Development Team)
  • Scrum board belongs to the team and is emptied after each sprint.

KANBAN

  • Iterations are optional. Different cadence for planning, read and process improvement.
  • Commitments are optional.
  • Cycle-Time = basic metric for planning and process improvement.
  • Teams of experts are allowed.
  • Completion of requirements takes as long as it takes. There is no requirement for the size of a request.
  • No specific diagram type is prescribed. Proven charts are CFD (cumulative flow chart) and chart control.
  • Work-In-Progress (WIP) is directly limited.
  • Estimates are optional.
  • New requirements within the WIP limitation are possible at any time.
  • No prescribed roles
  • Board can be shared by 1-n people and is continuously maintained.

USE OF SCRUM & KANBAN

Scrum and Kanban can be used in many places and offer different focuses.

Over time, the construct ScrumBan has also established itself, which aims to combine the strengths of the different frameworks to increase efficiency even more.

Nevertheless, we would like to advise you to test each framework on its own in order to recognize the strengths and problems. It is rather counter-productive to pick the "raisins" out of the respective framework because problems will occur during implementation.

What all frameworks have in common is that they are designed to uncover problems - so that we can solve them faster. For this reason, it is desirable that with the use of a framework, the underlying problems become visible.

EXTERME PROGRAMMING

FEATURE DRIVEN DEVELOPMENT