Stakeholder requirements, the needs of a stakeholder or group.Business requirements are often documented during project initiation. Business requirements, the high-level needs of the organization.

Solution requirements are based on business and stakeholder requirements. These requirements are defined as non-functional as the system can work without such elements.įunctional and non-functional requirements are also known as Solution Requirements. Non-functional requirements typically focus on usability – behaviors and features that affect user experience. Non-functional requirements are often directly related to functional requirements, for example, how quickly an app loads in a browser.Functional requirements describe the response of a system to inputs such as user behavior or data. Functional requirements refers to the capabilities, usability, features, or operations of a product.Requirements are typically categorized as functional or non-functional requirements: Later on, we’ll take a closer look at various techniques to identify and document requirements.Īs you’ll see in the next section, there are several types of requirements to consider. If the project is deemed unviable, the work may be canceled. If the project veers too far from stakeholder expectations, extensive re-work may be needed to deliver the original requirements. Balancing stakeholder expectations, new change requests, and the original project scope is tricky! ‘Expect’ is an important phrase in this context. Once the project is underway, requirements become the basis of monitoring and controlling work, including change requests.įinally, stakeholders expect to see their requirements in the final product or service before closing the project. Using a list of prioritized requirements, you can delve into detailed planning with tools such as the Work Breakdown Structure. You will use a range of techniques to identify, gather, analyze, and select project requirements. Typically, high-level requirements are documented at this early stage.ĭuring the planning phase, you’ll need to work closely with stakeholders to explore existing requirements in further detail.

Requirements drive every stage of the project.Ī project is initiated to solve a business need. The final outcomes of the project – a product, service, or result – are measured against the agreed requirements.

A description of how a system should behave.

Something that is needed or that must be done.

Requirements, “a condition or capability that should be present in a product, service, or result to satisfy its specifications’’ (Project Management Body of Knowledge).

Product scope, the features, and functions of a product, service, or result.

The Project Scope Statement also defines the acceptance criteria for deliverables. Scope is recorded in the Project Scope Document, which describes project deliverables, the required work, expected business value, and any exclusions to the project. Project scope refers to the work, and only the work, needed to deliver the project on time and within budget. To understand the importance of project requirements, we need to start with project scope and product scope.

Project manager requirements