Contents I. Introduction
IN February 2001 seventeen software developers met in the need of an alternative to documentation driven, heavyweight software development processes. The outcome of this meeting was the formulation and signing of the Manifesto for Agile Software Development [1]. This manifesto led the way to a transformation of engineering processes in the software industry. From traditional development approaches, like waterfall, the classic V, or the spiral model, towards agile methods like Scrum, Kanban, lean software development, extreme programming, or feature driven development [2]. All these agile process models have in common that they focus on customer involvement, team work, easy adaption to changes, flexibility and fast delivery of working products, not following a fixed sequential plan as in traditional methods. Especially Scrum [3] has become very popular in the software industry [4]. A survey released in May 2019 shows that Scrum is the most commonly used agile methodology, with 54% [5].
