Requirements Gathering Service

Our requirements gathering service ensures your team performs the right project work. From requirements capture and analysis to documentation and scope definition, we place project deliverables in focus.

What We Deliver

We elicit, analyze and quantify the project requirements then deliver the appropriate documentation. For most projects, our deliverable is the project scope baseline. We define the project scope, develop the work breakdown structure, obtain approval and deliver what’s needed to finish planning and begin work.

Requirements Gathering Service

To ensure each requirement meets a business need, we also generate the requirements documentation. We make certain that the work performed by our client adds value to their customer.

Lastly, we head off problems of scope creep long before they appear. We lay the groundwork for formal change control procedures. Where our work ends, the road ahead for our client is clear.

Our Requirements Gathering Process

The largest portion of our time is spent eliciting the project requirements. Elicitation is the process of pulling out and identifying what’s needed or what must happen. Depending on the project type and the source of the requirements, we use several tools to assist us. They’re all aimed at identifying the mark upon which to take aim. They include:

  • Brainstorming – used to capture as many thoughts as possible, without attempts to limit ideas. We like this technique when working with multiple stakeholders who, as a group, have not yet identified preferred outcomes.
  • Document Analysis – involves reviewing existing project documents, like project charters or RFPs, and pulling out requirements. It could also involve reviewing existing system documentation for the same purpose. The latter is useful when converting older software or systems to new technology.
  • Focus Groups – with this technique we bring together prequalified stakeholders and subject matter experts. The objective is to learn about their expectations and attitudes about a proposed product, service or result.
  • Interviewing – is a basic, yet critical tool. It involves asking the right questions and listening. When done right, listening is the dominant activity.
  • Observation – involves watching what happens. At times, we shadow users and document workflows. We find observation most useful when a system or procedure has been in place for an extended time. Here, seasoned users may be numb to pain points and fail to identify them verbally. Problems in workflow are often more easily identified by a fresh set of eyes. Where words aren’t sufficient to document what was observed, we use photographs, charts, diagrams, video and sound recording.
  • Story Boarding – involves the use of a sequence of images, graphics or sketches. In software development, it provides a fast and inexpensive way to gather user interface requirements. A layout of a page can be created and discussed, without the development of code.
  • Surveys – are used to gather information from a large number of people, perhaps in diverse locations.

Requirements Gathering for Multiple Project Types

We provide service to organizations who develop new products and to those who implement new services. Some project examples include custom software development projects, product design projects, higher education projects and projects that concern the public. Our requirements gathering service adds considerable value where the requirements are complex, numerous or spread out among many stakeholders in various locations.

What About Projects in Agile Environments?

For projects managed in an iterative or agile environment, our work is more collaborative. Here, we remain customer-facing throughout the project life cycle. We’re a fluid go-between that continuously gathers feedback and delivers clarity to the product vision.

Why You Need Effective Requirements Gathering

If you’ve been involved with project work, chances are you’ve seen problems associated with missing, misunderstood or changing project requirements. They’re a common source of issues and project failure. They can ruin a budget, a schedule and sometimes a reputation.

It’s not difficult to justify the time spent on requirements gathering. Effective requirements gathering:

  Facilitates schedule estimation
      Facilitates cost estimation

  Fosters better design
  Reduces misunderstandings

  Establishes acceptance criteria
    Reduces rework and waste

Let’s Begin the Conversation

Our professionals provide project management services for several types of projects. We rely on a dependable approach that’s used by practitioners around the world for producing measurable, repeatable results. We perform requirements gathering on the projects we manage and we provide our requirements gathering service to others as a stand-alone activity. Whether you need project management support, a requirements gathering service or something in middle, let’s talk.