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.

Agile In a Flash

Posted by Mike Bria on Jul 01, 2009

Sections
Process & Practices,
Architecture & Design
Topics
learning ,
Agile ,
Adopting Agile
Tags
Coaching and Mentoring ,
Index Cards ,
Principles ,
TDD

Many people playfully credit the 3x5 index card as the "agilist's badge". In many ways though this is not an inaccurate or inappropriate; going through a stack of index cards is a often real hallmark of many agile activities. But what about using index cards to learn and remember agile? With their Agile In a Flash project, Tim Ottinger and Jeff Langr want to help people do just that.

In the introductory post to their Agile In a Flash blog, which now catalogs over 60 agile "flash cards", Tim Ottinger and Jeff Langr explain Agile In a Flash like this:

There are lots of elements in agile to learn and remember. Uncle Bob defines three laws for TDD. Kent Beck devised the four rules of simple design. The agile manifesto defines four values. And so on. We found at least a full deck's worth of such lists, and have started capturing and using these lists to prod ourselves when our memories fail. The goal of our Agile In a Flash project is to produce a web resource, a book, and a replenish-able index card deck, all to use as tools in your day-to-day application of agile.

For background, early posts recount Tim then Jeff's experiences with and reasons for affinity for using index cards to capture information in their day-to-day activities, and how they've used cards to learn and teach over the years. Another early post describes the Oblique Strategies card decks from the late 1970's, mentioned as another source of inspiration for the Agile In a Flash project.

From there Jeff and Tim rip into a still-ongoing series of posts presenting the cards, one post per card, one card per post. Each post contains an image of the card, a reference to the idea's origin, and an expanded (but still concise) explanation of the cards bullet points. Many posts include not just "the book info", but also helpful commentary from Jeff and Tim's about their experience with the concept.

As of this writing, the series has provided over 60 cards covering topics from all over the agile landscape. In these 60, there are ideas coming from agile in the general sense, from XP, from Lean, from ideas on team dynamics, programming in general, and more.

Whether you're learning about agile, teaching others about it, or even just curious you should set aside some time to check out the Tim and Jeff's Agile In a Flash.

  • This article is part of a featured topic series on Agile

No comments

Watch Thread Reply

Educational Content

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.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.