The following pages and posts are tagged with
| Title | Type | Excerpt |
|---|---|---|
| Practices | Page | Needs > Values > Principles > PRACTICES > Tools |
| Practices of Extreme Programming | Post | Note: For more information, review the eXtreme Programming archetype. XP’s philosophy on Practices is very non-prescriptive, and advises an explorative approach, based on the XP Principles and XP Values. Practices recommended by Kent Beck Practices as presented in “eXtreme... |
| Whole Team | Post | Note: For more information, review the eXtreme Programming archetype. All the contributors to an XP project sit together, members of one team. This team must include a business representative – the “Customer” – who provides the requirements, sets the priorities, and steers the... |
| Test Driven Development | Post | Note: For more information, review the eXtreme Programming archetype. Extreme Programming is obsessed with feedback, and in software development, good feedback requires good testing. Top XP teams practice “test-driven development”, working in very short cycles of adding a test, then making it work.... |
| Sustainable Pace | Post | Note: For more information, review the eXtreme Programming archetype. Extreme Programming teams are in it for the long term. They work hard, and at a pace that can be sustained indefinitely. This means that they work overtime when it is effective, and that... |
| Small Releases | Post | Note: For more information, review the eXtreme Programming archetype. XP teams practice small releases in two important ways: First, the team releases running, tested software, delivering business value chosen by the Customer, every iteration. The Customer can use this software for any purpose,... |
| Simple Design | Post | Note: For more information, review the eXtreme Programming archetype. XP teams build software to a simple but always adequate design. They start simple, and through programmer testing and design improvement, they keep it that way. An XP team keeps the... |
| Design Improvement (Refactoring) | Post | Note: For more information, review the eXtreme Programming archetype. Extreme Programming focuses on delivering business value in every iteration. To accomplish this over the course of the whole project, the software must be well-designed. The alternative would be to slow down and ultimately... |
| Planning Game | Post | Note: For more information, review the eXtreme Programming archetype. XP planning addresses two key questions in software development: predicting what will be accomplished by the due date, and determining what to do next. The emphasis is on steering the project – which is... |
| Pair Programming | Post | Note: For more information, review the eXtreme Programming archetype. All production software in XP is built by two programmers, sitting side by side, at the same machine. This practice ensures that all production code is reviewed by at least one other programmer, and... |
| Metaphor | Post | Note: For more information, review the eXtreme Programming archetype. Extreme Programming teams develop a common vision of how the program works, which we call the “metaphor”. At its best, the metaphor is a simple evocative description of how the program works, such as... |
| Customer Tests | Post | Note: For more information, review the eXtreme Programming archetype. As part of presenting each desired feature, the XP Customer defines one or more automated acceptance tests to show that the feature is working. The team builds these tests and uses them to prove... |
| Continuous Integration | Post | Note: For more information, review the eXtreme Programming archetype. Extreme Programming teams keep the system fully integrated at all times. We say that daily builds are for wimps: XP teams build multiple times per day. (One XP team of forty people builds at... |
| Collective Code Ownership | Post | Note: For more information, review the eXtreme Programming archetype. On an Extreme Programming project, any pair of programmers can improve any code at any time. This means that all code gets the benefit of many people’s attention, which increases code quality and reduces... |
| Coding Standard | Post | Note: For more information, review the eXtreme Programming archetype. XP teams follow a common coding standard, so that all the code in the system looks as if it was written by a single – very competent – individual. The specifics of the standard... |
| Practices of Scrum | Post | Note: For more information, review the Scrum archetype. Scrum Master TODO |
| Scrum Master | Post | The Scrum Master is responsible for ensuring SCRUM is understood and enacted. Scrum Masters do this by ensuring that the Scrum Team adheres to Scrum theory, practices, and rules. The Scrum Master is a servant-leader for the Scrum Team. The Scrum Master helps those outside the Scrum Team understand... |