Agile in a Flash Card Index

In order to keep Agile in a Flash very low cost and actually make a buck or two, Tim and I were pressured to keep the number of cards to a very minimum. That's why you'll see no author bios, for example, and no index / table of contents. (Of course, if the book takes off and you buy bajillions of copies, we can likely justify an index.)

Without further ado, here's the index of cards (which also tells you, by omission, which blog entries here are not in this deck--if, uh, all goes well with sales, we'll be doing a second deck):

The Idea:
  1. Why Agile?
  2. The Agile Values, aka the Agile Manifesto
  3. Principles Behind the Agile Manifesto
  4. Role-Playing in Agile
  5. Agile Success Factors
  6. Courage
  7. Redefining Discipline
  8. Pillars of Software Craftmanship
  9. Toyota Production System (TPS) Principles
  10. The Right Process
  11. Got Organizational Obstinance?
  12. Got Individual Obstinance
  13. Don't Get Too Deep in Technical Debt
The Plan:
  1. Incremental Everything
  2. Embrace Change
  3. Reach Consensus on Story Priority
  4. INVEST in Your Stories
  5. Categorize Requirements with FURPS
  6. Sail on the Three C's
  7. Shrink XL Stories to Fit
  8. Acceptable Acceptance Tests
  9. Acceptance Test Design Principles
  10. Story Estimation Fundamentals
  11. A Winning Hand for Planning Poker
  12. Iterate with Principle
  13. Communication-SMITH with Information Radiators
The Team:
  1. Shu-Ha-Ri
  2. The Only Agile Tools You'll Ever Need
  3. Successful Stand-up Meetings
  4. ABCs of Pair Programming
  5. Retrospectives
  6. When Not Pairing
  7. How to Be a Team Player
  8. Collective Code Ownership
  9. Coding Standards
  10. Is Your Team Circling the Drain?
  11. Pair Programming Smells
  12. Stop the Bad Test Death Spiral
  13. How to Stay Valuable
The Code:
  1. Eight Crucial Practices of Agile Programmers
  2. Build Superior Systems with Simple Design
  3. The Seven Code Virtues
  4. ReallyMeaningful Names
  5. The TDD Cycle
  6. FIRST Properties of Unit Tests
  7. Triple A for Tight Tests
  8. Prevent Code Rot Through Refactoring
  9. Refactoring Inhibitors
  10. Field Guide to Mocks
  11. Break Unit Test Writer's Block
  12. Test Double Troubles
  13. TDD Process Smells

2 comments:

  1. Is it true that "further adieu" is just a pun to play a trick on me and the other would-be typo police? (That's what some random commenter on the first Google hit for further adieu thinks: http://bit.ly/i6oYlc ) If that's the case, rejoice that I fell in your trap!

    ReplyDelete
  2. @philip: fixed. Sorry it was left in place so long. What would we do without the typo police?

    ReplyDelete

Note: Only a member of this blog may post a comment.