Assessing Agility

@inproceedings{Lappo2004AssessingA,
  title={Assessing Agility},
  author={Peter Lappo and Henry C. T. Andrew},
  booktitle={XP},
  year={2004}
}
A technique is described that uses goals to assess the agility of software development teams and shows how it can be used with some examples. The agile assessment can be used to make investment decisions and process alterations. Value stream mapping is seen as an important technique in analysing processes. 

Organizing for agility: A complex adaptive systems perspective on agile software development process

TLDR
A conceptual framework to study agile software development based on the theory of complex adaptive systems is proposed and several agile practices are identified and reflected on from the perspective ofcomplex adaptive systems.

Title Organizing for Agility : a Complex Adaptive Systemsperspective on Agile Software Development Process

TLDR
A conceptual framework to study agile software development based on the theory of complex adaptive systems is proposed and several agile practices are identified and reflected on from the perspective ofcomplex adaptive systems.

Systems, Software and Services Process Improvement

TLDR
Here is a tentative set of process quality attributes that support achievement of safety requirements of a software product that can be analysed like any physical item.

An Approach for Assessing Suitability of Agile Solutions: A Case Study

TLDR
The purpose of this paper is to describe, how Agile Assessment was conducted in a case company in order to support product development and customer support improvement and it was found that Agile assessment is an efficient method to clarify what agile practices are suitable for the organization's productDevelopment and customer co-operation.

Agility beyond software development

TLDR
A set of agile characteristics is derived and two benefits of accepting such a set of characteristics for application of agile to other fields beyond software development and for measurement of agility are discussed.

AM-QuICk: A Measurement-Based Framework for Agile Methods Customisation

  • Hajer AyedN. HabraB. Vanderose
  • Business
    2013 Joint Conference of the 23rd International Workshop on Software Measurement and the 8th International Conference on Software Process and Product Measurement
  • 2013
TLDR
The Agile Methods Quality-Integrated Customisation framework (AM-QuICk) that relies on measurements and aims to continuously assist agile methodologists throughout the agile adoption and customisation process, i.e., during the initial organisation adoption, the method design and throughout the working development process is described.

Integrating PMBOX Standards, Lean and Agile Methods in Project Management Activities

TLDR
The results of this presentation show that PMBOK, Lean and Agile strategies are complimentary and can improve the visibility when performing complex projects.

CEFAM: Comprehensive Evaluation Framework for Agile Methodologies

TLDR
This work introduces the comprehensive evaluation framework for agile methodologies (CEFAM) as an evaluation tool for project managers and method engineers and provides results that are precise enough to be useful for the selection, adaptation and construction of agile methodology.

Agile software development in large-scale new product development organization: team level perspective

OF DOCTORAL DISSERTATION HELSINKI UNIVERSITY OF TECHNOLOGY P.O. BOX 1000, FI-02015 TKK http://www.tkk.fi Author Petri Kettunen Name of the dissertation Agile Software Development in Large-Scale New

References

SHOWING 1-10 OF 10 REFERENCES

SCRUM Development Process

TLDR
SCRUM is an enhancement of the commonly used iterative/incremental object-oriented development cycle that defines the systems development process as a loose set of activities that combines known, workable tools and techniques with the best that a development team can devise to build systems.

Comparing Extreme Programming to Traditional Development for Student Projects: A Case Study

TLDR
Little actual difference is observed between the products delivered by either process, but in this instance this is due to certain deficiencies in the way XP was realized, rather than fundamental flaws in the process itself.

Extreme programming explained - embrace change

TLDR
You may love XP, or you may hate it, but Extreme Programming Explained will force you to take a fresh look at how you develop software.

Lean Thinking—Banish Waste and Create Wealth in your Corporation

TLDR
The authors describe in detail how managers in a wide range of companies and industries - small, medium and large, North American, European and Japanese - transformed their business by applying the principles of lean thinking.

Principles of software engineering management

TLDR
This most recent book of Mr. Gilb's may be destined to become part of APL's folklore; if it were to adopt these methods in a similarly serious-minded vein the authors might easily discover a lot about ourselves and just possibly find a new way of getting their message into wider environments.

A formal experiment comparing extreme programming with traditional software construction

TLDR
An experiment to assess extreme programming and compare it with a traditional approach found that in spite of the absence of design and the presence of testing before coding the product obtained still has similar quality and size.

Learning to see.

  • A. Posner
  • Education
    Eye, ear, nose & throat monthly
  • 1955

Workshop submission to XP Agile Universe, http://sern.ucalgary.ca/eeap/wp/bk- position-2003.html (2003) Bacon, Steering With Numbers

  • Workshop submission to XP Agile Universe, http://sern.ucalgary.ca/eeap/wp/bk- position-2003.html (2003) Bacon, Steering With Numbers
  • 2003

IBM / NC State University XP Study Metrics

  • Workshop submission to XP Agile Universe,
  • 2003