Key learnings of Project Management Foundations: Requirements (2015) Course, Written

By Terri Wagne

Hedieh Nouri
College of Professional Studies, Northeastern University-Toronto
PJM6005 Project Scope Management
Prof. Eizakshiri
January 17, 2023
 2
Key learnings of Project Management Foundations: Requirements

1. Certificate of the LinkedIn Course

2. Key learnings of the Course

This course which is written by Terri Wagne is focused on what process is needed to be done to
recognize the valid requirements of a project. What characteristics does an accurate request have,
 2
Key learnings of Project Management Foundations: Requirements

how to collect the requirements properly and how to classify them as a necessary step.
Based on the International Institute of Business Analysis (IIBA) (2009), Requirement is a
condition or capability needed by a stake holder to solve a problem or achieve an objective.

Understanding the stakeholder's thoughts and then gathering all information to plan the steps
and recognize what needs should be answered is called the request elicitation process. throughout
this process, we have to be careful to choose the right question types like detailed or direct to
prevent emotional expression. After that, we would have unsettled data that should be formed
and organized. This process is called analyzing. at this step it is better to use tables and diagrams
instead of long sentences and paragraphs. Everyone should get the requirements.in other words,
it must not be in technical language. We are helping the stakeholders to find out if their needs are
doable or not, so the sentences should be easy to understand.

After finding all requirements, we have to prioritize them. There are three terms to describe the
importance of requirements that are:

1.High, Medium, Low

2.Nesseccery, Important, Desirable

3.Essential, Conditional, Optional

There are not many differences, we just have to make sure that all members are aware of these
words and could get their true meanings to describe requirements. Then, validation of
requirements begins which makes delivering value to the business and achieving project
objectives. it also helps to address the issues such as incomplete requirements, etc.

After that, the conclusions and reviews should be conducted and tested. Now the managing
change requirements start! At this point the goals should be defined, processes have to be
documented and the way of employing them should be taught. Needless to say, the more the

project is loading, the it is riskier and more expensive to make changes. It is the project
manager's responsibility to sometimes reject the requests or explain the cost of doing them to
stakeholders.
 2
Key learnings of Project Management Foundations: Requirements

References:
 2
Key learnings of Project Management Foundations: Requirements

Wagne, T., (2015). Project Management Foundations: Requirements. LinkedIn learning.

https://www.linkedin.com/learning/project-management-foundations-requirements-2015/
Brennan, K.,(2009). A guide to the Business analysis body of knowledge (BABOK guide).
Toronto: International Institute of Business Analysis.