Each board is presented following this plan:
- The Board, in a very short sentence. Example: "Keep it releasable"
- A little devil logo criticizing the council. Example: "We found a bug
blocking, stop everything you're doing and correct it without you to worry about the usual procedure, we will send a quick patch, no one will know "
- A section that develops on the subject in a few pages, and argues against critics.
- A small angel logo concluded. Example: "make sure that at any moment your project is buildable, testable, and deployable"
- A "What it feels like" section, which summarizes the gain of the approach
- A section "Keeping your Balance", which weights the rule. Example: If you need to send a patch as quickly, consider making a branch in subversion, not to make the system in an unstable state "
The only thing missing for the book to be perfect is a final section to each board, which offers the reader a reading or advice then, because the order of advice in each chapter seemed completely arbitrary. But this is minimal.
To conclude, "Practices of an Agile Developer" should be read by all developers, regardless of their experience. This is a great tool for progress, but also to evangelize your friends: all criticisms agility are shelled and dismantled intelligently, following a perfect pitch.
