Agile in a Flash

Tim Ottinger & Jeff Langr present the blog behind the versatile
Pragmatic Programmers reference cards.

Top Ten Agile Dangers


No comments:
Email ThisBlogThis!Share to XShare to FacebookShare to Pinterest
Newer Posts Older Posts Home
Subscribe to: Posts (Atom)

Purchase A Deck!

You can buy your own copy (or copies) of Agile In A Flash at Pragmatic Programmers. Check for generous quantity discounts.

Popular Posts

  • FURPS+
    Source: http://en.wikipedia.org/wiki/Furps Nowhere does it say that you must dispense with all prior knowledge in order to be agile. The FUR...
  • F.I.R.S.T
    Source: Brett Schuchert, Tim Ottinger In my Object Mentor days Brett and I were looking at ways to improve some class materials on the ...
  • 12 Principles for Agile Software Development
    Font (once again): MechanicalPencil The canonical source for these principles is the agile manifesto website . These are the basic agil...
  • Test Abstraction Smells
    In our article Test Abstraction: Eight Techniques to Improve Your Tests (published by PragPub), we whittled down a convoluted, messy tes...
  • Simple Design
    Source: Jeffries, et. al. Extreme Programming Installed , Addison-Wesley, 2000. My understanding is that the concept of simple design is Ken...
  • SMART goals
    Font: Sterofidelic The best lists never die. The SMART mnemonic has been around for at least half a century, per Wikipedia . SMART is simila...
  • Seven Steps to Great Unit Test Names
    You can find many good blog posts on what to name your tests . We present instead an appropriate strategy for when and how to think ab...
  • Red-Green-Refactor
    Drawing: Tim Ottinger Photo: Libby Ottinger Cleanup: Jeff L. We show flash cards to students in order to help them completely ingrain a conc...
  • Planning Poker (R)
    Source: Wikipedia Font: AndrewScript 1.6 Planning poker, trademarked by Mike Cohn , is a modernizing of a 50+-year-old estimating process kn...
  • Premature Passes: Why You Might Be Getting Green on Red
    Red, green, refactor.  The first step in the test-driven development (TDD) cycle is to ensure that your newly-written test fails before ...

Search This Blog

Subscribe To

Posts
Atom
Posts
All Comments
Atom
All Comments

Links

  • Agile Otter (Tim's Blog)
  • All About Agile
  • Langr Software Solutions (Jeff's blog)

Followers

Everything So Far

  • ►  2020 (1)
    • ►  January (1)
  • ►  2016 (1)
    • ►  August (1)
  • ▼  2015 (1)
    • ▼  February (1)
      • Top Ten Agile Dangers
  • ►  2013 (2)
    • ►  January (2)
  • ►  2012 (5)
    • ►  July (1)
    • ►  June (2)
    • ►  May (1)
    • ►  April (1)
  • ►  2011 (41)
    • ►  November (2)
    • ►  October (2)
    • ►  September (1)
    • ►  June (1)
    • ►  May (3)
    • ►  March (11)
    • ►  February (17)
    • ►  January (4)
  • ►  2010 (23)
    • ►  December (1)
    • ►  November (2)
    • ►  October (2)
    • ►  September (1)
    • ►  August (1)
    • ►  July (4)
    • ►  June (3)
    • ►  May (1)
    • ►  April (4)
    • ►  March (2)
    • ►  February (1)
    • ►  January (1)
  • ►  2009 (74)
    • ►  September (2)
    • ►  August (2)
    • ►  July (6)
    • ►  June (6)
    • ►  May (2)
    • ►  April (10)
    • ►  March (11)
    • ►  February (35)

Need a Deck?

Get your copy of Agile In A Flash today!
Simple theme. Powered by Blogger.