Skip to content


May 15, 2008

You are responsible for making your users understand the requirements. Here are a few things you can do:

1) From day one make sure your client understands that changes in scope will lead to changes in schedule and price

2) Try hard to communicate well. Use prototypes. It’s hard to find a client who will read all the requirements docs you produced, but they’ll review the prototype.

3) Make sure your specs are easy to read… a bunch of use cases is not enough. Write a spec doc like as if you were telling your users a story of what the system will be and how they will interact with it. Link to your use cases so they can see the details when needed. Use diagrams (I’m not UML diagrams, use visio with shapes and clipart)

4) Review the prototype and specs with the users. Update them based on feedback and review it again until there are no big changes requested.

5) Work iteratively or you’ll never finish your spec and prototype

No comments yet

Leave a Reply

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

You are commenting using your 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

%d bloggers like this: