Types of Requirements
Last week we defined requirements and showed how they’re essential to the success of the projects managed by GRCC’s IT Project Management Office. This article provides brief descriptions of the six main types of requirements we gather when planning projects.
• Business requirements
o Business requirements describe the higher-level needs of the organization as a whole, such as the business issues or opportunities, and reasons why a project has been undertaken. These requirements are most effective when they align with GRCC’s mission, vision, and values.
• Stakeholder requirements
o Stakeholder requirements focus on impacts to specific people, areas, and departments at GRCC, areas and people outside of GRCC that could be affected by a project, and how a project manager must communicate with each stakeholder group effectively.
• Solutions requirements
o These requirements are associated with the solutions inherent to a project. At GRCC, this typically involves functional and nonfunctional requirements, technology and standard compliance requirements, support and training, quality, and reporting requirements.
• Transition requirements
o This category of requirements must not be overlooked. It involves completely identifying the requirements necessary for transitioning and integrating the solution (or solutions) delivered by a given project to GRCC’s day-to-day operations.
• Project requirements
o Project requirements describe the actions, processes, or other conditions a project must meet. At GRCC, these requirements typically focus on how a project will be run to satisfy the needs of the sponsor and other key stakeholders.
• Quality requirements
o Quality requirements capture any condition or criteria needed to validate the successful completion of a project deliverable or fulfillment of other project requirements. We define these types of requirements to determine how to measure the quality of deliverables for a given project. Documenting these requirements is especially useful when project deliverables must meet an established standard.
Next week we will delve into effective techniques for gathering requirements.
Excerpts of definitions were taken from the following:
(2013) A guide to the project management body of knowledge (PMBOK guide) Fifth edition. Newtown Square, Pa.: Project Management Institute, Inc., pg. 112.