Team Metrics

• How fast are we going?
• What’s our biggest obstacle to velocity?
• Does we have enough requirements defined?
• Are we building the most valuable things we can?
• Is there something we’re deferring that should be worked on now?
• Are we getting things all the way done?
• What would we have if we had to ship tomorrow?

As mentioned previously, this blog series will cover the basic patterns only; advanced topics may be addressed in the future.

I will cover the basics on the principles and process before discussing the team and technical practices. Lean Software Development will be covered subsequently. The following topics will be covered in the order (more or less) listed below:

Pattern Name*** (with confidence level)

Aliases: if any …

Context in which we find the problem

The context is often described via a “situation” rather than stated explicitly. Sometimes, the context is described in terms of the patterns that have already been applied.

???

Forces or trade-offs behind the pattern

The often contradictory considerations that must be taken into account when choosing a solution to a problem. The relative importance of the forces (those that need to be optimized at the expense of others) is implied by the context.

Recently I was interviewing candidates for a couple of positions on an Agile project. As part of the recruiting process, I had to spend considerable time (aka late nights) going through dozens and dozens of resumes in order to shortlist the ones that seemed promising enough to call for a face-to-face interview.