Join Terri Wagner for an in-depth discussion in this video Classifying requirements, part of Project Management Foundations: Requirements.
- Requirements need to be defined, organized, and clearly understood by the project team members and the involved stakeholders. Classifying requirements helps us define and organize our work. A guide to the business analysis body of knowledge provides a few definitions of a requirement. One of those definitions is a condition or capability needed by a stakeholder to solve a problem or achieve an objective. IEEE tends to focus on capabilities, conditions and constraints.
One of their definitions in part says a capability that must be met or possessed by a product to satisfy a contract, standard, or specification. While there are several requirement schemes out there, for this course, we'll align ours with the BABOK. The BABOK includes business requirements, stakeholder requirements, solution requirements, functional requirements, nonfunctional requirements, and transition requirements.
Business requirements are where you would state higher-level goals, objectives, and needs of the organization. An example from our Kinetico case study would be "The wind-farm-produced electricity "shall be sold to local electric utility companies." Stakeholder requirements state the stakeholder needs and define how a stakeholder will interact with the solution. From our wind farm, an example is "Turbine noise must be kept to an acceptable level "at all times." For this requirement to be accepted into the project, further research will need to be conducted by the project team.
Then it will need to be reviewed and accepted by the stakeholders. The level of acceptability relates directly to proximity of the towers to residence and other buildings and location relative to the direction of the wind. The acceptable decibel measurement range must be specified for this to be a well structured requirement. Solution requirements describe characteristics of a solution. "All wind turbines shall be purchased "from a single manufacturer" would be a wind farm example of a solution requirement.
Solution requirements may also be broken out into function and nonfunctional bits. Functional requirements describe behavior and information that the solution will manage. For example, "Local homes, farms, and businesses "require turbine and tower placement "to be a minimum setback distance of 2,640 feet "or 1/2 mile from their physical locations." Nonfunctional requirements describe environmental conditions and system qualities.
On our wind farm, "Each tower's targeted capacity factor "shall range from 0.25 to 0.30" is a nonfunctional requirement example. Then there are transition requirements that describe a capability needed to transform the project from its current state into its future state. Here's an example from our wind farm. "The Colorado Division of Wildlife will conduct a review "of the designated wind farm area prior to construction "to ensure there are no impacts to protected species "or their habitats." Are you classifying requirements on your projects? If so, what scheme, system, or standard do you follow? Does your entire organization do it the same way or do you believe there is room for improvement?
Lynda.com is a PMI Registered Education Provider. This course qualifies for professional development units (PDUs). To view the activity and PDU details for this course, click here.
The PMI Registered Education Provider logo is a registered mark of the Project Management Institute, Inc.
- Classifying requirements
- Developing requirements
- Investigating requirements
- Documenting requirements
- Validating requirements
- Managing changing requirements