WHAT IS SCRUM?
Scrum is an agile, incremental development method. With each increment, the team delivers a potentially usable product. Changes in requirements can be incorporated into the project in a controlled manner.
The focus is on the self-organisation of the team. The Scrum Master supports this to enable trouble-free work.
The development team does not need a project manager. The product owner, as the product manager, takes over the technical requirements and defines, prioritizes and adapts them if necessary. Scrum's rules contribute to transparency and trouble-free development cycles (sprints).
WHAT IS KANBAN?
STOP START - START FINISHING
Kanban is a procedure that reduces the number of parallel tasks, the Work in Progress (WIP), when processing a value chain, and thus achieves faster processing times.
Problems, in particular bottlenecks, are quickly made visible.
Kanban comes from lean production and became known through its use at Toyota. The procedure has since been adapted to software development and organizational processes.
Kanban is a wonderful tool to visualize personal tasks and to work through your own tasks in a structured and focused way.
COMPARISON OF SCRUM & KANBAN
- Iterations of the same length are prescribed.
- Team agrees on a certain amount of work to be done in the next sprint.
- Velocity = basic metric.
- Teams should be put together cross-functionally.
- Requirements must be met within a sprint.
- Burndown charts are used as metrics.
- Indirect WIP limitation by the limited amount in the sprint. Optional WIP limitation within a sprint.
- Estimates are mandatory.
- No new requirements in running sprint.
- Three mandatory roles (Product Owner, Scrum Master, Development Team)
- Scrum-Board belongs to the team and is emptied after every sprint.
- Iterations are optional. Different cadences for planning, relese and process improvement.
- Commitments are optional.
- Cycle-Time = basis metric for planning and process improvement.
- Expert teams are allowed.
- The completion of the requirements takes as long as it takes. There is no requirement for the size of a requirement.
- No specific diagram type is prescribed. Proven diagrams are CFD (Cumulative Flow Diagram) and Chart Control.
- Work-In-Progress (WIP) is directly limited.
- Estimates are optional.
- New requirements within WIP limits are possible at any time.
- No prescribed roles
- Board can be shared by 1-n persons and is continuously maintained.
USE OF SCRUM & KANBAN
Scrum and Kanban can be used in many places and offer different focal points.
Over time, the construct ScrumBan has also established itself, which wants to combine the strengths of the different frameworks in order to increase efficiency even more.
Nevertheless, we would like to advise you to test each framework for itself in order to identify its strengths and problems. It is rather counter-productive to pick the "raisins" from the respective framework, because problems arise during implementation.
What all frameworks have in common: they should uncover problems - so that we can solve them faster. For this reason it is desirable that the underlying problems become visible with the use of a framework.