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.

What Practices Make Up YOUR Agile Development?

Posted by Amr Elssamadisy on Apr 17, 2009

Sections
Process & Practices,
Architecture & Design
Topics
Agile Techniques ,
Survey ,
Agile
Tags
Surveys

In the world of agile software development there is little agreement on which practices are "really" agile, and which ones are not. Likewise, people don't agree on which agile practices are most important, and nobody knows which practices are actually applied in how many projects.

In an attempt to gain insight into the current state of the community, Jurgen Appelo is running a survey that could give us answers to these questions if a sufficient number of people participate.

Even though a number of other surveys have already been published before, most notably those of VersionOne and Scott Ambler, Jurgen's survey is the first that does not focus on coarse-grained methods (like Scrum or XP), but on 66 fine-grained individual agile practices. The results are going to be interesting if enough of the community participate.
 

Absurd idea by Steven Mak Posted
  1. Back to top

    Absurd idea

    by Steven Mak

    The idea to isolate the practice and ask people whether certain practice is "Agile" or not is simply absurd.

    Take an example, asking whether "Product Vision / Vision Statement" is an Agile practice or not makes no sense at all.

    One can have product vision regardless of what methodology he/she uses. It has nothing to do with Agile or not, while having "Product vision" (or any other SINGLE practice) won't guarantee agility (even employing all practices without sharing Agile values won't).

    I doubted what "Agile" means here, and what "Agile" means to the owner of the survey.

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.