• Corpus ID: 14964165

Quantifying the Effect of U sing Kanban vs . Scrum : A Case Study

@inproceedings{Sjberg2012QuantifyingTE,
  title={Quantifying the Effect of U sing Kanban vs . Scrum : A Case Study},
  author={Dag I.K. Sj{\o}berg and Anders Johnsen and J{\o}rgen Solberg},
  year={2012}
}
Many claims about the usefulness of various processes or methods, such as Scrum and Kanban, have been stated in agile and lean software communities. However, these claims are rarely supported by objective data or empirical investigations. In contrast, this article aims to demonstrate that the effect of processes or methods (here: Scrum versus Kanban) can be evaluated and compared on the basis of objective data. We analyzed data of more than 12,000 work items collected over the years 2009-2011… 
1 Citations

Figures and Tables from this paper

Requirements Formulation Neglect as a Major Cause of Poor Data Quality in Information System Systems

TLDR
There are over 30 percent (near 40 percent) of unnecessary data replication or redundancy when elicitation of requirements is poor, which is serious enough to impel the success or failure of information systems.

References

SHOWING 1-9 OF 9 REFERENCES

Kanban and Scrum - Making the Most of Both

Scrum and Kanban are two flavours of Agile software development - two deceptively simple but surprisingly powerful approaches to software development. So how do they relate to each other? The purpose

Quantifying the Effect of Code Smells on Maintenance Effort

TLDR
To reduce maintenance effort, a focus on reducing code size and the work practices that limit the number of changes may be more beneficial than refactoring code smells.

Empirical studies of agile software development: A systematic review

The effectiveness of pair programming: A meta-analysis

Orthogonal Defect Classification - A Concept for In-Process Measurements

TLDR
The authors define ODC and discuss the necessary and sufficient conditions required to provide feedback to a developer; illustrate the use of the defect type distribution to measure the progress of a product through a process; and open the doors to a wide variety of analysis techniques for providing effective and fast feedback based on the concepts of ODC.

Software measurement - establish, extract, evaluate, execute

TLDR
This book describes software measurement in theory and practice as well as provides guidance to all relevant measurement tools and online references and provides many examples and case studies from Global 100 companies.

Software Project Dynamics: An Integrated Approach

Presents a scientific model of the software project management process based on focused field interviews and includes a detailed case study that was conducted to test the model. Covers human resource

Dybå and T . Dingsøyr . Empirical studies of agile software development : A systematic review

  • Information & Software Technology
  • 2008

Kanban: Successful Evolutionary Change for Your Technology Business

  • 2010