Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
From scrum to scrumban: A case study of a process transition
KTH, School of Information and Communication Technology (ICT), Software and Computer systems, SCS.
KTH, School of Information and Communication Technology (ICT), Software and Computer systems, SCS.ORCID iD: 0000-0002-1780-0683
2012 (English)In: 2012 International Conference on Software and System Process, ICSSP 2012 - Proceedings, IEEE , 2012, 140-149 p.Conference paper, Published paper (Refereed)
Abstract [en]

Transitioning from one development method to another has become a common routine for many companies. Despite this, very few reports describe how the process transition has been carried out, and provide suggestions for how to define a process transition model. This paper reports on a process transition from Scrum to Scrumban in one software development company. The paper gives an account on the process transition process, changes done to the development process undergoing the transition and the improvements achieved. It rounds up with lessons learned.

Place, publisher, year, edition, pages
IEEE , 2012. 140-149 p.
Keyword [en]
Kanban, method adoption, Process improvement, process introduction, Development method, Development process, Transition model, Transition process, Industry
National Category
Engineering and Technology
Identifiers
URN: urn:nbn:se:kth:diva-101539DOI: 10.1109/ICSSP.2012.6225959Scopus ID: 2-s2.0-84864344008ISBN: 978-146732352-9 (print)OAI: oai:DiVA.org:kth-101539DiVA: diva2:549317
Conference
2012 International Conference on Software and System Process, ICSSP 2012; Zurich; 2 June 2012 through 3 June 2012
Note

QC 20120904

Available from: 2012-09-04 Created: 2012-08-30 Last updated: 2014-02-13Bibliographically approved
In thesis
1. Software Process Improvement Framework
Open this publication in new window or tab >>Software Process Improvement Framework
2014 (English)Doctoral thesis, comprehensive summary (Other academic)
Abstract [en]

Many software development organizations today are keen on improving their software development processes in order to develop software products faster, cheaper or better. For that reason, Software Process Improvement (SPI) has received significant attention from the research community over the last few decades. Process maturity models have become widely known for benchmarking software processes against predefined practices and for identifying processes to be improved or implemented, whereas process improvement approaches were developed for guiding the actual process improvement process. However, despite a wide number of provided guidelines on how to standardize the processes and how to run process improvement efforts, only a few SPI initiatives have succeeded. About 70% of the SPI initiatives fail and a significant number do not even get started. Many studies argue that the success of the SPI initiatives is dependent on the organizational, social and managerial aspects of process improvement. Those aspects however are not sufficiently covered by the existing SPI approaches and models. The little knowledge on organizational, social and managerial aspects of SPI that is available is mostly scattered across the domain. Hence, there is lack of a holistic overview of the current SPI domain that provides sufficient coverage of organizational, social and managerial aspects of SPI.

This thesis has explored the organizational, social and managerial aspects of SPI and placed them into the context of the SPI domain. Its main research result is Software Process Improvement Framework (SPIF). The framework provides an overview of the SPI domain and positions theories representing organizational, social and managerial aspects of SPI in the context of existing SPI approaches, models, methods and practices. SPIF is based on the existing theoretical framework for SPI environment proposed by Sami Zahran. The SPIF framework has been additionally complimented with four additional outcomes of this study. Those are: 1) a list of organizational, social and managerial factors facilitating SPI effort, 2) a list of contextual factors impacting process change, 3) a process model for guiding software method adoption, and 4) a checklist representing the properties of successful and sustainable SPI projects.

The research was based on a strong industrial cooperation. As many as thirty software development organizations were involved in this research. Methodologically, the research was conducted in line with the inductive reasoning, which guided the research into building the knowledge from empirical studies. However, at some stages of this research, literature studies were incorporated. The main research methods of this study are action research and case studies, whereas data collection methods are primarily structured interviews, participatory observations and surveys.

The thesis concludes that implementing a recommended software development processes or practices using well defined SPI approaches is not enough. In order to implement successful and lasting process improvement, organizations also need to consider organizational, social and managerial aspects of SPI. The SPIF framework and other results of this thesis may significantly benefit software development organizations that plan to conduct software process change, or have already done it. These organizations may use SPIF for getting an overview of the process improvement process and the theories, methods and tools that should support it. The other results of this thesis can be used for: 1) incorporating organizational, social and managerial aspects in process changes, 2) for adapting process improvements in various organizational contexts, 3) for guiding adoptions of new software development methods, and finally 4) for evaluating and improving process improvement efforts.

Place, publisher, year, edition, pages
Stockholm: KTH Royal Institute of Technology, 2014. 129 p.
Keyword
software process, process improvement, SPI, software method adoption, organizational change, change management, organizational aspects, social aspects, managerial aspects, SPI success factors, SPI checklist
National Category
Engineering and Technology
Research subject
Information and Communication Technology
Identifiers
urn:nbn:se:kth:diva-141272 (URN)978-91-7595-002-0 (ISBN)
Public defence
2014-03-11, Sal D, Forum 100, Isafjordsgatan 39, Kista, Stockholm, 13:00 (English)
Opponent
Supervisors
Note

QC 20140213

Available from: 2014-02-13 Created: 2014-02-12 Last updated: 2014-02-13Bibliographically approved

Open Access in DiVA

No full text

Other links

Publisher's full textScopus

Authority records BETA

Kajko-Mattsson, Mira

Search in DiVA

By author/editor
Nikitina, NataljaKajko-Mattsson, Mira
By organisation
Software and Computer systems, SCS
Engineering and Technology

Search outside of DiVA

GoogleGoogle Scholar

doi
isbn
urn-nbn

Altmetric score

doi
isbn
urn-nbn
Total: 1102 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf