Agile Software Development with Scrum
Agile Software Development with Scrum
The effects of pair-programming on performance in an introductory programming course
SIGCSE '02 Proceedings of the 33rd SIGCSE technical symposium on Computer science education
Pair programming and pair trading: effects on learning and motivation in a CS2 course
Journal of Computing Sciences in Colleges
Lean Software Development: An Agile Toolkit
Lean Software Development: An Agile Toolkit
Analyses of an Agile Methodology Implementation
EUROMICRO '04 Proceedings of the 30th EUROMICRO Conference
Project Management in Plan-Based and Agile Companies
IEEE Software
Managing Uncertainty in Requirements: A Survey in Documentation-Driven and Agile Companies
METRICS '05 Proceedings of the 11th IEEE International Software Metrics Symposium
Appropriate Agile Measurement: Using Metrics and Diagnostics to Deliver Business Value
AGILE '06 Proceedings of the conference on AGILE 2006
Rolling Out Agile in a Large Enterprise
HICSS '08 Proceedings of the Proceedings of the 41st Annual Hawaii International Conference on System Sciences
Empirical Software Engineering
Pair programming: what's in it for me?
Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement
ISSRE '08 Proceedings of the 2008 19th International Symposium on Software Reliability Engineering
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
Empirical Software Engineering
When agile meets OO testing: a case study
Proceedings of the 1st Workshop on Testing Object-Oriented Systems
Empirical Studies on Quality in Agile Practices: A Systematic Literature Review
QUATIC '10 Proceedings of the 2010 Seventh International Conference on the Quality of Information and Communications Technology
Information and Software Technology
Hi-index | 0.00 |
Many software-development organizations have recently started to adopt agile practices in order to benefit from the improvements they clearly bring, in terms of production speed and software quality, for example. However, in a large, distributed organization, such as Nokia Siemens Networks, an agile transformation may be a long-term, complex process, and therefore, evaluating the benefits achieved, and measuring the success of the change, can be difficult, especially in the early phases of the transformation. This paper is based on the results of a case study on the impact introducing agile practices actually had in a large, software-development organization, part of Nokia Siemens Networks. The impact of this agile transformation was evaluated in terms of how well it succeeded in achieving the goals set by the management before the transformation started. This longitudinal study included two separate analyses, made at 6 monthly intervals, which measured what agile practices were really in use in the organization, and what effects, if any, were visible in terms of the goals which had been set by the management The 6 monthly analyses included defect data metrics and opinion surveys of the personnel directly involved in the transformation. The study showed two things: firstly, that the introduction of agile practices does have the beneficial effects that one would expect, and secondly, that, using this kind of study, it is not only possible to evaluate the impact that the adoption of agile practices has in a large, established software-development company, but also that the effects are visible at a surprisingly early stage.