InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

A Disciplined Approach to Agile Adoption

Posted by Ben Hughes on May 10, 2007

Sections
Process & Practices,
Architecture & Design
Topics
Agile ,
Methodologies ,
Agile in the Enterprise ,
Change
Tags
Business Models ,
Adoption
Ahmed Sidky and James D. Arthur present the first part of their Agile Adoption Framework. providing a structured, repeatable framework for adopting Agile processes in a development organization.

The framework aims uses a four staged approach for assessing the organization's ability to adopt agile practices, cascading down through project suitability and aims to reconcile the findings in a set of agile processes to adopt:



The authors introduce the concept of the Sidky Agile Measurement Index (SAMI), which proposes the agile potential (i.e., the degree to which that entity can adopt agile practices). This consists of four components:

  1. Agile Levels - a set of agile practices that are related and, when adopted collectively, would make significant improvements in the software development process, thereby leading to the realization of a core value of agility.

  2. Agile Principles -  guidelines that need to be employed to ensure that the development process is agile.

  3. Agile Practices and Concepts - concrete activities and practical techniques used to develop and manage software projects in a manner consistent with the agile principles.

  4. Indicators - questions the assessor uses to assess certain characteristics of an organization or project, such as its people, culture, and environment, in order to determine assess the readiness of the organization or project to adopt an agile practice.

The authors go on to comment on the practical uses of of the SAMI beyond the framework, and illustrate thorough an example how the SAMI can be applied.

While this is only the first installment in a two part article, the authors provide a thought provoking method for measuring the distance an organization will have to travel, in order for it to reach its full agile potential.
  • This article is part of a featured topic series on Agile

Related Sponsor

In today’s hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now!

No comments

Watch Thread Reply

Educational Content

Jesper Boeg on Priming Kanban

In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.