Scrum-Agile Vs. Kanban, Scrumban-1!

I will cover Scrum-Agile and Kanban methodology and discuss Scrumban with you in 3 articles in total. In this first post, we’ll cover methodologies used in project management in general and Scrum.

Agile process models in software development have prevailed in business since the turn of the millennium. Scrum is one of the most commonly used models here. However, due to its fixed set of rules, Scrum is not equally suitable for all software development tasks. Sometimes Scrum is also unsuitable, for example for support tasks or for very small teams. Some of these teams then use a more flexible and very non-specific Kanban.

However, a middle ground between Kanban and Scrum is also possible in order to combine the advantages of both process models and avoid or at least reduce the disadvantages. This is often called a Scrumban.

Software Development Lifecycle Models

A software development lifecycle model describes the types of activities performed in each phase of a software development project and how these activities are related logically and temporally. There are a number of different software development lifecycle models.

ISTQB (International Software Testing Qualifications Board) categorizes common software development life cycle models as follows: