{"id":459,"date":"2018-11-27T09:04:31","date_gmt":"2018-11-27T08:04:31","guid":{"rendered":"https:\/\/pmexperts.com\/pmbok-guide-vs-manual-prince2-zarzadzanie-integracja-projektu-cz-3\/"},"modified":"2024-09-23T12:42:24","modified_gmt":"2024-09-23T10:42:24","slug":"pmbok-guide-vs-manual-prince2-zarzadzanie-integracja-projektu-cz-3","status":"publish","type":"post","link":"https:\/\/pmexperts.com\/en\/pmbok-guide-vs-manual-prince2-project-integration-management-part-3\/","title":{"rendered":"PMBOK\u00ae Guide vs manual PRINCE2\u00ae \u2013 Project integration management part 3"},"content":{"rendered":"

In the previous comparison text PMBOK\u00ae Guide <\/em>and the PRINCE\u00ae manual<\/a> I compared two documents, i.e. project management plan according to PMBOK\u00ae Guide <\/em>and project initiation documentation in accordance with the PRINCE2\u00ae methodology. I have examined their construction in detail to demonstrate that they serve the same general purpose, which is to provide a basis for organizing and effectively running a project. Effective project management must involve responding to changes that inevitably occur in every project activity.<\/h4>\n

Will the documents constituting the project also change as a result? Definitely yes.<\/strong> These documents contain a project plan (PRINCE2\u00ae methodology) or base plans (PMBOK\u00ae Guide<\/em>), and of course plans change. US President Dwight Davis Eisenhower, Supreme Commander of the Allied Expeditionary Forces in Europe during World War II, is credited with the phrase: "A plan is nothing, planning is everything" (originally: "When preparing for battle, I always realized that plans are useless , but planning is essential\u201d). Can we therefore afford to approach planning documents in a relaxed manner? Definitely not.<\/strong> PMBOK\u00ae Guide<\/em> w odniesieniu do planu project management.<\/a> stwierdza: Nim elementy bazowe planu zostan\u0105 zdefiniowane, plan zarz\u0105dzania projektem mo\u017ce by\u0107 korygowany tak wiele razy jak to konieczne. \u017baden formalny proces nie jest wymagany w tym czasie. Jednak\u017ce kiedy zdefiniowanie element\u00f3w bazowych nast\u0105pi, to mo\u017ce on zosta\u0107 zmieniony jedynie poprzez proces Prowad\u017a Zintegrowan\u0105 Kontrol\u0119 Zmian (ang. Perform Integrated Change Control). W konsekwencji wnioski o zmian\u0119 b\u0119d\u0105 tworzone i poddane pod decyzj\u0119, kiedy tylko zmiana jest wnioskowana. W wyniku powstaje plan zarz\u0105dzania projektem, kt\u00f3ry jest stopniowo rozwijany i doprecyzowywany poprzez kontrolowane i zatwierdzane uaktualnienia a\u017c do zako\u0144czenia projektu.<\/p>\n

So let's take a closer look at the Drive Integrated Change Control process, which is covered in section 4.6 in PMBOK\u00ae Guide<\/em>. Already in its first sentence we read that "(...) it is the process of reviewing all change applications; Approving and managing changes to products, project documents and the project management plan; and communicating decisions made.\u201d The next paragraph states: "the process is carried out from the beginning of the project to its completion and is the primary responsibility of the project manager. Can we find its equivalent in the PRINCE2\u00ae methodology? Definitely yes.<\/strong> It is the procedure for controlling issues and changes. It includes the following steps:<\/p>\n