Whole Team Activity

Whole Team Activity

Software development is a whole team activity – avoid silos and barriers to communication.  Extreme Programming introduced the idea of the Whole Team, which includes business representatives, testers, and of course programmers.  These teams work together, ideally within the same … Continued
Pain Driven Development

Pain Driven Development

What is Pain Driven Development (PDD)? It means waiting to apply principles, patterns, and practices to your code until there is some pain the current approach is causing that must be addressed. It’s a variation of YAGNI that ensures you … Continued
Read the Manual

Read the Manual

A great deal of the time, software developers can mostly figure things out by just trying things, and seeing what fits.  Maybe it’s a matter of trying different combinations until the compile error disappears, or maybe it’s a matter of … Continued
Rubber Duck Debugging

Rubber Duck Debugging

Sometimes the process of describing a problem, even to an inanimate object, can reveal the solution. Rubber duck debugging refers to the practice of using a small toy, like a rubber duck, as your first assistant when you are faced … Continued
Shipping Is A Feature

Shipping Is A Feature

Never lose sight of the fact that until you ship your product, it is not providing value to anybody.  Joel Spolsky put it well when he wrote: A 50%-good solution that people actually have solves more problems and survives longer … Continued
Update the Plan

Update the Plan

When you miss a deadline or milestone, don’t just blindly shift the planned deadline back by a day. This is an opportunity to quickly re-assess the project’s status, update the plan, and communicate the new plan to all of the … Continued
Sustainable Pace

Sustainable Pace

Software developers should rarely be made to work more than 40 hour weeks, and if one week does require overtime, the next one certainly should not.  This helps to maintain programmer welfare and avoid a death march project.
System Metaphor

System Metaphor

A metaphor that everyone (whole team, customers, management, stakeholders) agrees on for how the system works.
Simple Design

Simple Design

Kent Beck created four rules of Simple Design. These are sometimes referred to as The Four Commandments or the XP Simplicity Rules. The rules, in priority order, are that code should: Pass all tests Express the author’s ideas Avoid duplication … Continued
Collective Code Ownership

Collective Code Ownership

Collective code ownership breaks down fiefdoms within an application’s codebase. Nobody “owns” a particular part of the code. Everyone on the team is responsible for all of the code.  This enables pair programming and refactoring by the whole team. It … Continued