specs pretend to be complete

There’s something about a functional spec that makes it seem complete. Even when it is clearly marked as being a “Draft”, or when it has “TBD” sections; these just feel like minor blips on the way to completeness. A spec — even a badly written one — has an air of authority.

But express exactly the same information as a set of examples, or as a set of rows in Fit tables, and something magical happens. Suddenly that same information is obviously incomplete, demonstrably sporadic. And suddenly it’s easier to imagine how the solution might be developed incrementally, and that some of the examples could have lower priority than others. Change also becomes less of an issue, because a set of examples doesn’t have that air of being a work of art.

Get past the fear of incompleteness and a whole new world of possibilities opens up.

Advertisements

One thought on “specs pretend to be complete

  1. So true.

    Something related I also notice is that the BA / Product Owner type people who tend to work at the ‘speccy end’ of the process will talk in the present tense about features that are in the spec, as though that functionality were somehow real already!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s