Databases
StackOverflow2013
Postsdbo
POBest concrete "How-To Manual" on *Managing* Test Driven and/or Agile development?
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBest concrete "How-To Manual" on *Managing* Test Driven and/or Agile development?
    text
    copied!<h3>I am looking for an easily digestible book to present to my boss/team.</h3> <hr> <p><strong>Background info:</strong> More and more of our meetings at work involve my boss/team pondering how to implement more "best practices" around here. ("Here" = a very small application development shop. 4 developers)</p> <p>The following things are items that my whole team agrees that we need:</p> <ul> <li>Nightly builds</li> <li>Decomposing "bugs" in our bug-tracker into smaller, more-specific items</li> <li>Automated testing</li> </ul> <h2><b>The problem we face is how to get started.</b></h2> <p>I believe that if my shop could simply choose <strong><em>a clear and specific plan</em></strong> or set of rules, then everything else would fall into place. Right now we are stuck in discussions of fuzzy, feel-good ideas and nice-sounding buzzwords.</p> <p>Please recommend to me your favorite book (or online resource) that contains clear, discrete, sequential steps for implementing a management scheme for guiding a TDD or Agile team/shop.</p> <p>I realize that there are other paradigms besides TDD and Agile that would also address these concerns, but my own self-interests and biases point toward TDD and Agile so I would love to harness my team's desire for change and "nudge" it in that direction. Or feel free to slap me down if you vehemently disagree with my sentiments! I will take no offense. :)</p> <h3>As others have stated, I think these questions are answered best when respondents list only one book recommendation per answer.</h3> <hr> <p>Thank you all.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload