Change Management vs. Configuration Management - PMP Exam Prep / PMBOK Guide Lingo 

Hey Jeff! How you doing buddy? Thanks for stopping by! Great to hear from you!

⁸ n NJ u 7

Thanks 👍 best wishes.

WOOOHOOO! CONGRATULATIONS SHEY! NICE END TO 2017!!! 😄 What is the secret of your success? How many hours a day? Any tips to help those trying to step into PMP exam greatness?

Praizion Honestly their is no shortcut to hard work. I was clear in my goal and reached out to people for support. I read pmbok many times and read Rita couple of times. Your video on ITTO is very informative. I practiced over 2000 questions from different test bank.. finally reading pmbok until my convept cleared and each time i start again reading. I felt pmbok was shrinking and my concepts were expanding.. i studied everyday. If I can do it anyone cqn do it. Hope this helps

Always a pleasure Sir!

AND MITHUN IS NOW A PMP BAUWUSS!!!! BIG BOSS! CONGRATS BUDDY!

Thank you!

Thank you and all the very best.

Glad it was helpful!

You're welcome!

Ty ty AN!

Thank you Mohmd Balal!

Great explanation Ethan. You got it! On some projects, there may be no CMP or Config MP so the PM and team may have to build from scratch.

Ty Thib!

Collect Requirements Output: Requirements Documentation. PMBOK GUIDE P.147-148 "Requirements documentation describes how individual requirements meet the business need for the project. Requirements may start out at a high level and become progressively more detailed as more information about the requirements is known. Before being baselined, requirements need to be unambiguous (measurable and testable)," --------------------------------------------------------------------------------------------------------------------------------- Also possibly in the Project Scope Statement secondarily - PMBOK GUIDE P.154: Deliverables. Any unique and verifiable product, result, or capability to perform a service that is required to be produced to complete a process, phase, or project. Deliverables also include ancillary results, such as project management reports and documentation. These deliverables may be described at a summary level or in great detail.

Thank you!

Thank you!

Glad it was helpful!

😁 Sorry I missed this one for a while Jhohn! Think about Management of changes to documented characteristics of a windshield (specs) versus Management of changing the windshield itself. In configuration management the engineers who updated the windshield to include an electronic display of temperature and GPS (Version 2.9) document the updated specs and give it a version name (V2.9). In change management the team could be involved in a change request to install the windshield for a customer. In the same vein the team could be involved in a change request to optimize the windshield creation process in firm X. This change request could even become a project with smaller aspects of Configuration Management or Change Management. Its all a Matrix⌨️ ⌨️ ⌨️ 💡 💡 💡 Show less

No problem and thanks for the the reply... and perfect timing too. My PMP exam is tomorrow. Thanks again for all of your youtube content. I've been a regular for months. Take care!

UNBELIEVABLY TIMELY! AND YOU KILLED THE EXAM!!! CONGRATS JHOHN! How did you find it? Please share your lessons learned with us! I have an mp3 to send you. Email us: info@praizion.com What a great start to the year!!!!

Hey Buddy! Sorry this is so late. I needed to create a book to answer you! Lol. Your question about the modification of project documents, including the project management plan and its subsidiary plans, is a great one. In most project management frameworks, these documents are indeed managed under the Configuration Management System. Here's how it typically works: It depends on if the plans and documents are deemed "CONFIGURABLE ITEMS" or not. Some firms have very little PM Plan controls and others have more. Project plans are different from project documents and different from baselines. Project docs could be considered deliverables especially in government and some are tied to performance, milestones and payments. Please take note: ** Documents as Part of Configuration Management: Project documents and plans are considered part of the project's configuration. This includes the project management plan, its subsidiary plans, and other key project documents. ** Version Control: Just like with product specifications, these documents require version control. This ensures that any changes made to them are tracked, approved, and documented. Version control helps maintain consistency, traceability, and accountability throughout the project lifecycle. ** Documents as Deliverables: In a way, project documents and plans can be considered as deliverables, especially in contexts where accurate documentation is crucial. They may not be the final product delivered to the customer, but they are essential for the successful completion and delivery of that product. ** Specifications vs. Management Plans: Project documents and management plans can be seen as "specifications" in a broader sense. They specify the approach, processes, guidelines, and methodologies to be used in the project. So, in this context, they do have their own "specifications" which are outlined within the documents themselves. ** Change Control Process: When changes are needed in these documents, they typically go through a change control process. This process involves evaluating the impact of the change, getting the necessary approvals, and then updating the documents accordingly. ** Documentation Integrity: The Configuration Management System helps in maintaining the integrity and coherence of these documents. It ensures that everyone on the project team is working with the latest and most accurate information. I hope this clears any doubts for you Antonio. Cheers!

Thanks Samir!

You're welcome Poorna!

Hi Sudeep. I think this is the closest one I have: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-FbZDL8mw_mA.html Configuration management plan is not explicitly mentioned as an input to the processes but it can be implied from P. 78 that it is in the project management plan.

A few broad changes. Project change or product change. OR Document changes and Plan changes. People change or Process change.

As the project evolves, change may be necessary in a product's original specs due to progressive elaboration. Specs must be updated to reflect this and document these modifications.

What about? Please expand.

While your frustration with this topic is understood, your response doesn't help the matter. Take responsibility for your lack of understanding and study this topic more (read it in the PMBOK Guide).

Vinay why you don't ask Phill to teach you by asking him to put more light on the ambiguous points you did not understand that would be better than complaining! anyway Phill keep going man you killed the confusion honestly : example of config mgt like you are up to change the car tyre however you got a different version of the spare in the boot then its not gonna fit or sim card not fitting into your devices needs to be configured this is nothing to do with who how this changes will be processed which refers to change mgt I hope you are not confused anymore otherwise ask PHILL

Thank you!