The Rollercoaster of Required Agile Transition
AGILE '07 Proceedings of the AGILE 2007
Does the XP environment meet the motivational needs of the software developer? An empirical study
AGILE '07 Proceedings of the AGILE 2007
Empirical studies of agile software development: A systematic review
Information and Software Technology
An initial investigation of software practitioners' motivation
CHASE '09 Proceedings of the 2009 ICSE Workshop on Cooperative and Human Aspects on Software Engineering
The Amazing Team Race A Team Based Agile Adoption
AGILE '09 Proceedings of the 2009 Agile Conference
From CMMI and Isolation to Scrum, Agile, Lean and Collaboration
AGILE '09 Proceedings of the 2009 Agile Conference
Historical Perspective of Two Process Transitions
ICSEA '09 Proceedings of the 2009 Fourth International Conference on Software Engineering Advances
Kanban and Scrum - making the most of both
Kanban and Scrum - making the most of both
Transition from a plan-driven process to Scrum: a longitudinal case study on software quality
Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement
| Hi-index | 0.00 |
Even if most of the software process transitions have been made with the goal of improving software processes, only few experience reports recognize process transition as an important element of software process improvement. This paper reports on a developer-driven Big-Bang process transition from Scrum to Kanban, and recognizes it as part of process improvement effort in one software development company. The paper reports on the transition process, changes done to the process and results achieved. It rounds up with an initial model of a process transition, lessons learned from the process transition effort and suggestions for future work.