Copyright

Project Requirements: Definition, Types & Process

An error occurred trying to load this video.

Try refreshing the page, or contact customer support.

Coming up next: The Initiation Phase of Project Management

You're on a roll. Keep up the good work!

Take Quiz Watch Next Lesson
 Replay
Your next lesson will play in 10 seconds
  • 0:02 What Are Project Requirements?
  • 0:58 Categories
  • 3:19 Requirement Gathering Methods
  • 6:00 Requirements…
  • 6:32 Lesson Summary
Save Save Save

Want to watch this again later?

Log in or sign up to add this lesson to a Custom Course.

Log in or Sign up

Timeline
Autoplay
Autoplay
Speed Speed

Recommended Lessons and Courses for You

Lesson Transcript
Instructor: Gail Raynor

Gail is a PMP Charterholder and currently works as Director of Continuing Professional Development.

In this lesson, we will discuss project requirements. We will define what they are, along with the different types of project requirements. We will also discuss the process upon which to create clear project requirements.

What Are Project Requirements?

Imagine that you're building your dream house. You've purchased the land, hired the architect, and secured your construction crew. That's a good place to start, but without your blueprint, your dream house will remain just that: a dream. Your blueprint gives the architect, contractor, electrician, plumber, and anyone involved in the build, a clear idea of what needs to be done to finish the house. This plan provides them with the requirements needed to complete their jobs.

Project requirements are conditions or tasks that must be completed to ensure the success or completion of the project. They provide a clear picture of the work that needs to be done. They're meant to align the project's resources with the objectives of the organization. The benefits of effectively gathering project requirements include cost reduction, higher project success rates, more effective change management, and improved communication among stakeholders.

Categories

Project requirements can be categorized into three main categories: business, solution, and stakeholder requirements.

Business requirements are the high-level needs of the business. They address what's required and why the project is happening. Getting back to our house example, a business requirement might include, 'build an eco-friendly house with high-efficiency solar panels that will reduce carbon emissions and reduce environmental impact.' This is the starting point of the project and provides guidance for the other types of requirements. It's imperative that these requirements are communicated clearly and early on.

Solution requirements, which include both functional and non-functional requirements, are the specific features and characteristics of the product or service that meet all requirements, both business and stakeholder. Functional requirements describe something that a product or service is required to do. Non-functional requirements describe how a system is supposed to function. A functional requirement for your solar panel is to 'convert light into electricity,' while the non-functional requirement is to 'produce this electricity at an efficiency rate of 20%.'

A stakeholder is anyone who has an interest in the product or service that's being produced or provided. They may be internal stakeholders (employees) or external stakeholders (customers, regulators, or suppliers). Every individual stakeholder has specific needs or requirements that they want to be fulfilled. Each of these needs must be balanced during the course of the project. Often times, stakeholders have competing needs, which can impact the schedule, budget, and scope of the project if not managed effectively. Suppose, as the owner of the house, you decide that you want repurposed composite wood for the exterior of your house. However, after your builder has placed the order, you discover that your Home Owners Association only allows for stucco and brick exteriors. This change will have a knock-on effect in terms of pricing, materials and design and will ultimately slow down the project.

When a stakeholder happens to be your customer, you need to ensure that you're eliciting their exact requirements in order to deliver on your product or service. If the right questions are not asked using the right method, you will not meet customer needs and, in the end, the project will have failed.

Requirement Gathering Methods

There are several different ways to collect requirements that vary depending on the type and complexity of the project. There are advantages and drawbacks to each method. It's best to use a combination of these techniques and avoid taking shortcuts when it comes to collecting project requirements. The success of the project is directly related to how well requirements are communicated, documented, and carried out. A best practice is to ensure that you're including as many stakeholders as possible.

To unlock this lesson you must be a Study.com Member.
Create your account

Register to view this lesson

Are you a student or a teacher?

Unlock Your Education

See for yourself why 30 million people use Study.com

Become a Study.com member and start learning now.
Become a Member  Back
What teachers are saying about Study.com
Try it risk-free for 30 days

Earning College Credit

Did you know… We have over 200 college courses that prepare you to earn credit by exam that is accepted by over 1,500 colleges and universities. You can test out of the first two years of college and save thousands off your degree. Anyone can earn credit-by-exam regardless of age or education level.

To learn more, visit our Earning Credit Page

Transferring credit to the school of your choice

Not sure what college you want to attend yet? Study.com has thousands of articles about every imaginable degree, area of study and career path that can help you find the school that's right for you.

Create an account to start this course today
Try it risk-free for 30 days!
Create an account
Support