Project Management

Home / Discussions / Project Management Central /

Is it the right time to have Requirments Management Knowledge Area?

Requirements Management Scope Management Using PMI Standards Work Breakdown Structures (WBS)

Ahmed Khalil Ex. Chief Projects Officer & Current COO & GM | FFS LLC Dubai, Dubai, United Arab Emirates

Introducing Collect Requirements process was a very good step in the right direction.

But isn't it time to take it to a higher level emphasizing on the importance of requirements management for projects success.

Introducing a new knowledge area in the PMBOK called "Requirements Management Knowledge Area" isn't it the right time?

Isn't it adopted by most practitioners in most of the projects most of the time which qualify it to be part of a standard when its recognized, documented and approved.

Posted: Aug 8, 2016 4:19 AM

Sort By:

< 1 2 >

Venkata Rama Satish Nyayapati Hyderabad, Telangana, India

I agree with what most of you have said about requirements being a subset of scope. Though managing requirements is important, most of it overlaps with other KAs and there are detailed in separate guides. Hence I don't see a reason to have a separate KA.

Posted: Aug 9, 2016 1:53 AM

Eduard Hernandez

Community Champion

Product Operations Program Manager Barcelona, Cataluña, Spain

Great answers. When I read the question, I answered NO in my head. Then I read the posts and realized that I can't put out the reasoning in better words.

Posted: Aug 9, 2016 2:44 AM

ahmed Gaballa Civil Engineer| AL-ID Engineering Consultants Dammam, Eastern Province, Saudi Arabia

I think that a lot of prject management process are very important, so we can not include its as KA .

Posted: Aug 9, 2016 3:01 AM

Hazem Ibrahim Sr IT Specialist| Turner International Middle East Hawally, Salmiya, Kuwait

I think since PMI has introduced PMI-PBA that the Requirement Management is the job of the Business Analyst not the Project Manager.
PMI should emphasise the role of BA and the cooperation and coordination between BA and PM as the BA is one the Project Management Team and he/she provides the PM with the User/Organization "Needed" requirement through the elicitation and other requirement management processes and techniques used by BA.

I think PMI should focus more on value management and value realization in the new version on PMBOK instead.

Posted: Aug 10, 2016 12:02 AM

Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina

Hazem: product/service/result requirements is the job of business analyst. Project requirements is the job of project manager, not business analyst. Of course, while you work on determine product/service/result requirements (the solution the business analyst is contributing to define and create) some requirements that will be project requirements arrives like project constraints and project assumptions.

...

1 reply by Hazem Ibrahim

Aug 11, 2016 9:34 AM

Hazem Ibrahim

...

Thank you I was really talking about the product requirement as the basic for the project requirement.

Posted: Aug 10, 2016 7:24 AM

Nouman Rahim Mining Engineer| Qadir and Co, Kohat Cement Factory Peshawar, Pakistan, Pakistan

student like me will feel what's going on - every day adding new areas in the PMBOK.. :(

Posted: Aug 10, 2016 12:47 PM

Hazem Ibrahim Sr IT Specialist| Turner International Middle East Hawally, Salmiya, Kuwait

Aug 10, 2016 7:24 AM

Replying to Sergio Luis Conte

...

Thank you I was really talking about the product requirement as the basic for the project requirement.

Posted: Aug 11, 2016 9:34 AM

< 1 2 >

Please login or join to reply

Is it the right time to have Requirments Management Knowledge Area?

Sponsors

Vendor Events

Guessing is not a strategy: How to build decision velocity with AI and real-time data

Newsletters