It's human nature to only do the stuff that's familiar and fun, and that's what has happened with Agile.

What is good design?

Introducing: The Spag.

How, when, and why to use Kanban systems to eliminate iterations.

How to use risk multipliers and risk-adjusted burn-up charts to make solid commitments to your executives.

CI tools make it easy to do the wrong thing.

Agile requirements, in-depth.

Why we trash seven-figure software investments.

An easier, cheaper (and better) way to do continuous integration.

Six months of changing an organization from within.

A fresh look at XP, sans humility, maturity, and wisdom.

Six months of changing an organization from within.

We keep forgetting that we're here to develop software.

A comparison of Scrum, both editions of XP, and The Art of Agile Development.

In order to do agile development your way, you have to do it some way first.

The right method for your team is customized to the needs of your team. The question is, how do you get there?

A story cut from The Art of Agile Development. With a monkey.

What's more important, using agile practices or understanding agile principles and values?

Real success takes real work. It's worth it.

A thoughtful look at two methodology choices.

Following the rituals of agile development without understanding the underlying ideas.

The most common issues I see new teams struggle with.

It's human nature to only do the stuff that's familiar and fun, and that's what has happened with Agile.

A bedtime story.

Boy, do they ever.

An easier, cheaper (and better) way to do continuous integration.

How is it possible for codebases to get easier to modify over time? This is how.

Exercises for improving coding skills.

Good builds are game-changing.

Warning: this brain dump is long, aimed at advanced readers, and not particularly well written.

What to do when you want to test a private method.

Produce more valuable software by replacing process with collaboration.

What you didn't know about agile documentation.

If the customer isn't in charge, then who is?

Split into pairs, and use the worksheet to take turns interviewing each other.

It's so damned personal.

People get really worked up over coding standards, and I mean really worked up.

Collective ownership doesn't have the flash or controversy of other practices, but it's part of what makes an agile team "agile."

What are we really looking for when we turn to documentation?

Experiences with hard problems in agile design.

Why we trash seven-figure software investments.

Fail immediately and visibly when an error occurs.

Skills needed for continuous design.

Use risk-based assessments to guide agile architecture.

Don't get seduced by the Dark Side.

Fundamental design skills.

A taxonomy of design.

An instructive building is built outside my window.

A 25-dollar term for a 5-cent concept.

What is good design?

When I decide to change this design decision, how hard will it be?

Ubiquitous Language, System Metaphor, and a bit of history.

The inevitable rise of HTML+Javascript.

Notes on installing JS-Kit, a comments and ratings service.

How I produce this website.

An experimental programming language from Jonathan Edwards.

How to use slack in XP's planning game.

Two reasons teams can't make and meet iteration commitments.

If you have trouble making and meeting commitments, start here.

How, when, and why to use Kanban systems to eliminate iterations.

Improve productivity by reducing task switching.

Use defect lists to troubleshoot organizational problems.

The overtime trap.

Classic lessons from a hundred-million dollar loss.

Generate goodwill for your agile team.

Six months of changing an organization from within.

Look them straight in the eye and say "No."

I can't convince anybody to do anything.

When shit rolls downhill, expect crappy results.

Notes from the field... far afield.

Avoid common productivity measurement mistakes.

Another approach to measuring productivity.

How do we get people to do what we want?

The challenges of measuring performance.

Introducing: The Spag.

A simple, valuable technique you can start using immediately.

Painlessly gather retrospective information.

Doctor, doctor, it hurts when I do this!

Exploring the alternatives to functional testing.

Keep your brain switched on at all times.

"Failures, repeated failures, are finger posts on the road to achievement."

Vacation planning instructs us about agile planning.

It's only funny if you're not living it.

Projects... or products?

When will the project finish?

When you're buying something expensive and valuable that's meant to last a long time, you put real effort into it.

In MoSCoW, plans prioritize you!

How to use risk multipliers and risk-adjusted burn-up charts to make solid commitments to your executives.

An example of What Not To Do, featuring scope creep, pushy stakeholders, and poor decisions.

Use Fit to collaborate on requirements during an iteration.

Agile requirements, in-depth.

What really happens when users read requirements documents.

By the time an idea is a requirement, the most interesting part of its life is over.

A look at two basic types of Fit examples, with a recommendation.

A story of Fit workflow in practice.

How to construct a single Fit document.

Without the vision of a good product manager, the team is likely to flounder.

Doctor, doctor, it hurts when I do this!

Beth was smart and capable, but everyone knew she wasn't Charlie.

CI tools make it easy... to do the wrong thing.

Discover planning problems early by planning as a group.

Stop being a slave to the software.

Software configuration management is important, but the tools aren't up to the task.

Sometimes, truth isn't clear, and clarity isn't truthful.

The evolution of the "Pair Programming" outline in The Art of Agile Development.

A screencast showing how I wrote the first draft of the "Sit Together" practice in The Art of Agile Development.

The evolution of the "No Bugs" text in The Art of Agile Development.

Introducing: The Spag.

It's human nature to only do the stuff that's familiar and fun, and that's what has happened with Agile.

How, when, and why to use Kanban systems to eliminate iterations.

An example of What Not To Do, featuring scope creep, pushy stakeholders, and poor decisions.

How to use risk multipliers and risk-adjusted burn-up charts to make solid commitments to your executives.

In MoSCoW, plans prioritize you!

Beth was smart and capable, but everyone knew she wasn't Charlie.

What are we really looking for when we turn to documentation?

Collective ownership doesn't have the flash or controversy of other practices, but it's part of what makes an agile team "agile."

What to do when you want to test a private method.

Warning: this brain dump is long, aimed at advanced readers, and not particularly well written.

Good builds are game-changing.

Software configuration management is important, but the tools aren't up to the task.

The evolution of the "No Bugs" section in The Art of Agile Development.

If you have trouble making and meeting commitments, start here.

The challenges of measuring performance.

The most common issues I see new teams struggle with.

Two reasons teams can't make and meet iteration commitments.

People get really worked up over coding standards, and I mean really worked up.

Following the rituals of agile development without understanding the underlying ideas.

Ubiquitous Language, System Metaphor, and a bit of history.

A thoughtful look at two methodology choices.

It's so damned personal.

An experimental programming language from Jonathan Edwards.

A screencast showing how I wrote the first draft of the "Sit Together" practice in The Art of Agile Development.

How I produce this website.

Notes from the field... far afield.

Notes on installing JS-Kit, a comments and ratings service.

Split into pairs, and use the worksheet to take turns interviewing each other.

How do we get people to do what we want?

"Failures, repeated failures, are finger posts on the road to achievement."

Keep your brain switched on at all times.

Stop being a slave to the software.

When shit rolls downhill, expect crappy results.

The evolution of the "Pair Programming" practice in The Art of Agile Development.

Real success takes real work. It's worth it.

What's more important, using agile practices or understanding agile principles and values?

Sometimes, truth isn't clear, and clarity isn't truthful.

A story cut from The Art of Agile Development. With a monkey.

When you're buying something expensive and valuable that's meant to last a long time, you put real effort into it.

Exercises for improving coding skills.

If the customer isn't in charge, then who is?

The right method for your team is customized to the needs of your team. The question is, how do you get there?

I can't convince anybody to do anything.

Look them straight in the eye and say "No."

When will the project finish?

In order to do agile development your way, you have to do it some way first.

How is it possible for codebases to get easier to modify over time? This is how.

Another approach to measuring productivity.

A comparison of Scrum, both editions of XP, and The Art of Agile Development.