Project Management

Please login or join to subscribe to this thread

requirements management plan is parto of configuration plan?

linkedin twitter facebook   Agile   Information Technology   Using PMI Standards  
avatar
William Meza Soria Ing| personal Quito, Ecuador
requirements management plan is part of configuration plan?
Sort By:
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
Hola William. Voy a escribir en español. Los requerimientos "atraviesan" todo lo referente a un proyecto. Quiero decir, vas a tener requerimientos relativos a al manejo de la configuración. El Requirements Management Plan lo que te va a permitir es administrar todo lo relativo a todos los requerimientos. Acá hay algo importante. Como project managers nuestro foco son los requerientos del proyecto (no del producto) y en el caso de configuracion nuestro foco es la configuracion del proyecto, no del producto. Tuve la oportunidad de ser parte del grupo de autores de la "Requirements Management; A practice guide" y de "Practice Standard for Project Configuration Management". Si bien no son todo lo que yo esperaría te recomiendo que las leas al menos, como su nombre indica, para tenerlas como guía.
avatar
Thomas Walenta Global Project Economy Expert Hackenheim, Germany
William

according to PMBoK Guide ed6, the requirements mgmt plan is one of the subsidiary plans of the overall project management plan. Any configuration plan is not. So, formally, the answer is no.

Practically, requirements can be included the configuration management system (CMS). There might be a plan in a project defining this system, or not, it might just exist on company level. The configuration management system is a (digital) place, where project artifacts are tracked and also changes to them are handled.
If you use a requirements traceability matrix, it would probably be part of the CMS.

Thomas
avatar
Keith Novak Tukwila, Wa, United States
In the context of a project, requirements management is generally about the requirements of the product produced. Configuration management involves the requirements relating to processes, tools, and documentation that create and define the product.

A project might contain both if you need to meet new or unique configuration management requirements. Those CM requirements would not typically be included in the requirements traceability matrix which is about the product, not the organizational process assets (OPAs) which we use to define the product.
...
1 reply by Kwiyuh Michael Wepngong
Aug 10, 2021 6:57 AM
Kwiyuh Michael Wepngong
...
Thanks Keith
avatar
Kwiyuh Michael Wepngong
Community Champion
Financial Management Specialist | US Peace Corps Yaounde, Centre, Cameroon
Aug 09, 2021 3:02 PM
Replying to Keith Novak
...
In the context of a project, requirements management is generally about the requirements of the product produced. Configuration management involves the requirements relating to processes, tools, and documentation that create and define the product.

A project might contain both if you need to meet new or unique configuration management requirements. Those CM requirements would not typically be included in the requirements traceability matrix which is about the product, not the organizational process assets (OPAs) which we use to define the product.
Thanks Keith

Please login or join to reply

Content ID:
ADVERTISEMENTS

"It is best to keep your mouth shut and be presumed ignorant than to open it and remove all doubt."

- Mark Twain

ADVERTISEMENT

Sponsors







Newsletters

Jun 3: The Career Problem Facing New PMs
May 20: Your PM Career as a Project Life Cycle
May 13: The Big Lie After Layoffs

See all newsletters