To me project objectives should be equivalent to the project benefits.
Project requirements are the technical description of the project. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
The defintion is inside the PMBOK itself. Project requirements are derived and created from product requirements. It is all required to complete the project scope. Project objectives are things you have to achieve to consider the project successful. Project objectives related to scope, time, quality and cost will address the project requirements.
...
1 reply by Moutaz Tarbin
Jul 22, 2019 11:58 PM
Moutaz Tarbin
...
Requirements, I think, are not limited to product requirements or scope only, there are product requirement, project requirements, requirements for quality, schedule, and cost.
Saving Changes...
Moutaz TarbinC.E.O| Syrian engineering studies & consulting co. ( SESCO)Daphne, Al, United States
Aug 03, 2017 3:56 PM
Replying to Sergio Luis Conte
...
The defintion is inside the PMBOK itself. Project requirements are derived and created from product requirements. It is all required to complete the project scope. Project objectives are things you have to achieve to consider the project successful. Project objectives related to scope, time, quality and cost will address the project requirements.
Requirements, I think, are not limited to product requirements or scope only, there are product requirement, project requirements, requirements for quality, schedule, and cost. Saving Changes...
ANSI/PMI 99-001-2017 defines: PROJECT MANAGEMENT is the application of knowledge, skills, tools, and techniques to project activities to meet project requirements. It seems that the requirement is much broader than the objectives. Objectives tends to be SMART--Measurable, while requirements can have qualitative attributes. I am new to this standard and would appreciate any feedback. Thank you. Saving Changes...
Strictly speaking, a requirement is something that is mandatory while an objective is something that is desirable.
If the project "must" or "shall" achieve some criteria, that is a requirement. If it "may" or "should" achieve it, then it is an objective.
Both can be directly measurable or not, explicit or vague. The more subjective or vague the requirement, the greater the risk that Person A may decide the requirement is met, while Person B concludes otherwise. Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Objectives are what you agree on with key stakeholders to achieve by the project.
Requirements may come from different stakeholders (like the sponsor: make a profit, a user: make it easy for me, a manager: embed these features, customer: keep that budget, government: adhere to these regulations). Requirements tend to pop up or change during a project and might lead to scope creep and project failure, if not managed well.
Once you have most requirements, you design your output and the way how to get there and this is called scope or solution. From the scope you can derive objectives, and they are SMART because you deselected requirements and they are needed to align all stakeholders.
You can't satisfy all requirements, there is a balance to strike. Saving Changes...
Latha Thamma reddiSr Product and Portfolio Management (Automation Innovation)| DXC TechnologyMckinney, Tx, United States
