Reasons for Engaging a Requirements Analyst – Humorous, but True!

Welcome to Practical Analyst, a site specializing in practical insight for business analysts and project professionals. If you're new here, you may want to subscribe to my RSS feed or follow me on Twitter. Thanks for stopping by!

geeksmiley.jpgThese are fun and typically true. I may even consider sharing them with my next old school stakeholder who can’t see why it’d be best to get away from the classic 5 bullet e-mail as the requirements spec of record.

Here are 5 reasons why to use a requirements analyst:

  1. You’re in the box. You can’t even smell the cardboard anymore, much less describe it with a critical eye. An outsider will help you see yourselves objectively.
  2. The analyst has been here before. They’ve got the T-shirt, understand the process and they already know what good requirements look like.
  3. Analysts are linear thinkers. These are people who get ill if the condiments are before the buns at the church picnic. Process thinking comes naturally to an analyst. You may or may not have honed that skill in your work.
  4. A good Requirements Analyst is also an experienced facilitator. There are different kinds of interviews to conduct: Executives, managers, staff, customers, etc. Our people can gather the essentials from each audience efficiently.
  5. You have better things to do. You had a full time job before this new project came along. Don’t you really want to leverage your strengths?

Thanks to Disambiguator for the original content.

Filed Under: Business Analysis

About the Author: Jonathan Babcock is a business analyst who thoroughly enjoys what he does. Practical Analyst is his outlet for sharing what he's learned, and for interacting with like-minded folks. To keep up with the latest on Practical Analyst, you can subscribe to the RSS feed, follow Jonathan on Twitter, or view his profile on Linked In.

RSSComments (0)

Trackback URL

Leave a Reply