Published: January 2011
The best agile book isn’t a book: Agile in a Flash is a unique deck of index cards that fit neatly in your pocket. You can tape them to the wall. Spread them out on your project table. Get stains on them over lunch. These cards are meant to be used, not just read.
Agile in a Flash is no longer sold as a printed deck of cards. The PDF version is available, and you can use the PDF to print your own card deck.
Agile in a Flash cards teach leadership, teamwork, clean programming, agile approaches to problem solving, and tips for coaching agile teams. Use the cards for learning, as ice breakers for conversations, as constant reminders, and as a potent source of useful tips and hard-won wisdom. Agile in a Flash cards are:
The Agile in a Flash deck is broken into four sections: agile concepts, planning, teamwork, and coding. The front of each card features a concise list of the concepts you need to know and remember. The back provides further detail, with sage nuggets of knowledge based on the authors’ two decades of experience coaching and doing agile-style projects.
These cards are an indispensable tool for any agile team, and a must-have for every agile coach or Scrum Master.
Don’t be afraid to wear them out—they’re priced so you can get a set for everyone and replace them if you need to. Tape the cards to your wall, stick them on your monitor, quiz your peers, and get agile fast.
“I have only one major issue with your cards, which is that I didn’t
think of them
and do them first. That wouldn’t be so bad if you were screwing them up, but
unfortunately they’re great.”
“Agile in a Flash is the only place to find a concise summary of all
things agile. I
recommend my customers buy it for all their programmers.”
Actual picture of Agile in a Flash cards in use!
Jeff Langr has been building software for more than a quarter century. He is the author of Agile Java and Essential Java Style, plus more than 80 articles on software development and a couple chapters in Uncle Bob’s Clean Code. Jeff enjoys helping others learn how to build software well, but is happiest when he gets to code.
Tim Ottinger has more than 30 years of software development experience, including time as an agile coach, OO trainer, contractor, in-house developer, and even a little team leadership and management. He is also a contributing author to Clean Code. He writes code. He likes it.
Published: January 2011