Posted by tac_admin, April 3, 2012

Ambiguous Terms – Avoid Them

One of the most important things you will do as a business analyst is document requirements. If those requirements are ambiguous, you’re going to have trouble later in the project.

Ambiguous terms leave room for interpretation by the development team and can also create requirements that are not testable.

Karl Wiegers, a well-respected requirements management consultant, in his book Software Requirements, provides this list of words to avoid and ways to improve them. You may want to print this list and post it in your office as a visual reminder.

Click this link to download and save the list of terms (this file is in PowerPoint format).

Ambiguous Terms

4 responses to “Ambiguous Terms – Avoid Them”

  1. Cristina says:

    The attachment for the Ambigous terms is not PowerPoint. It’s a zip file with xml attachments.

    • Teresa Bennett says:

      Hi Cristina – I’m not sure what the issue was. I just reloaded the file. Please try again.

      Thanks for letting me know you had an issue with this!

      • Peter Corduan says:

        FYI, Theresa:
        I am also only seeing folders within the Zip file containing several xml files, but nothing that looks like a presentation (nor *.pp* type file). You might try looking at it from your web browser for reference. Best of luck.

Leave a Reply

Your email address will not be published. Required fields are marked *

Get in touch today

Speak directly with The Analyst Coach
and get pointed in the right direction.

Preferred Contact EmailPhone

Subscribe to receive our free white paper on how weak requirements effect strong companies


Sign up to get your FREE Business Analyst Survival Guide

Don't worry, we hate spam too. We will never share your information to third parties.