Use-Cases Part II: Taming Scope: A List Apart

Lucid "A List Apart" article describing how to translate the programmer nerdiness of use cases for use in web project planning (although similar techniques would be helpful in any variety of project contexts).

We habitually storyboard new functionality for customers so that they can see the consequent increase in complexity. By doing so, we define options for the customer and then decide which bits of proposed functionality are the most important. We also use use-case diagrams to establish boundaries for the project; any use cases devised for the site later on are obviously change requests that add extra effort and therefore increase the project’s cost.

I wish all clients were wise and patient enough to walk through this level of detail before they started choosing new drapes and doorknobs. Understanding the critical pieces and dependencies is arguably the backbone of good project planning; you’ll never get to start coloring until everyone agrees where the lines need to go.

(Part I of the series is worth reading, too.)