Corollary Practices for Extreme Programming

<p>This week we look at chapter 9 of Extreme Programming Explained 2nd edition by Kent Beck and reflect on the exercise from chapter 8, Getting Started, that we did live last Thursday on Twitch.</p> <p>After doing the exercise, I recommend the following format. Spend 5 minutes brainstorming on each of the three questions. After that, go back and refine what you came up with; this should take 10-5 minutes for a total of 20 minutes per practice.</p> <p>The three questions to answer are</p> <p>Why do you want to do the practice?<br /> What are the things that lead towards doing the practice well?<br /> What are the signs that you are moving in the wrong direction?</p> <p>In this chapter, Beck described 11 corollary practices for XP. These are more advanced than the original 14 primary practices.</p> <ul> <li>Real Cusomter Involvment</li> <li>Incremental Deployment</li> <li>Team Continuity</li> <li>Shrinking Teams</li> <li>Root-Cause Analysis</li> <li>Shared Code</li> <li>Code and Tests</li> <li>Single Codebase</li> <li>Daily Deployment</li> <li>Negotiated Scope Contract</li> <li>Pay-Per-Use</li> </ul> <p>We will discuss these practices live on Twitch this Thursday at 7 pm eastern You can join the discussion by going to <a href= "https://bookclub.dev/live">bookclub.dev/live</a>.</p>