Requirements Documentation

As I mentioned in the opening to this section, requirements quantify and prioritize the wants, needs, and expectations of the project sponsor and stakeholders. Requirements typically start out high-level and are progressively elaborated as the project progresses. You must be able to track, measure, test, and trace the requirements of the project. If you can't measure or test whether the requirement satisfies the business need of the project, the definition of success is left to the subjective opinions of the stakeholders and team members.

You're worked hard to gather and define requirements and you don't want all that effort going to waste. This output involves recording the requirements in a requirements document. The PMBOK® Guide does not dictate the format of this document and acknowledges it can be formal with lots of detail or a simple list categorized by stakeholder and priority. However, it does state that the requirements document may include at least the following elements:

■ Business need for the project and why it was undertaken

■ Objectives of the project and the business objectives the project hopes to fulfill

■ Functional requirements

■ Nonfunctional requirements

■ Quality requirements

■ Acceptance criteria

■ Business rules

■ Organizational areas and outside entities impacted

■ Support and training requirements

■ Assumptions and constraints occur once data is entered. In non-software terms, functional requirements might describe specifications, quantities, colors, and more. Nonfunctional requirements refer to elements that are related to the product but don't describe the product directly. In the case of a software product, this could be a security requirement or performance criteria.

Functional requirements is a term used often in software development. It typically describes a behavior, such as calculations or processes that should

One of the most important elements of the requirements document that isn't in the preceding list is the signatures of the key stakeholders indicating their acceptance of the requirements. They will also sign the scope statement, which we'll talk about in the section "Defining Scope" later in this chapter.

Project Management Made Easy

Project Management Made Easy

What you need to know about… Project Management Made Easy! Project management consists of more than just a large building project and can encompass small projects as well. No matter what the size of your project, you need to have some sort of project management. How you manage your project has everything to do with its outcome.

Get My Free Ebook


Post a comment