Its supose that the close contract activities are made in the control procurement process, but in the close project or phase there are activities like that too. I think that is an error in the PMBOK . Saving Changes...
Isabel,
I have found that when there is something that appears missing from the PMBoK, it is often found as a component of another input or output. The key to finding what you are looking at the description of those I&O.
Procurement Documentation is an Input to Close Project or Phase (Fig. 4-14). The way PMI depicts it, closing the contract occurs before closing the project much like "accepted deliverables" is also an input. The contract may not be closed before closing a phase, so close contract activities is not always appropriate since the section describes either closing a project or a phase.
Whether that is an error, or simply not as explicit as desired can be a subject of debate. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
You can see that Work Performance Date is an input of Control Procurement. Depending of that data perhaps you will update your procurement documentation or you will close the contract and that does not mean the project has to be closed. That is you will not execute Close Project And it does not meant that a phase has to be closed too (remember the phase definition is up to you, is related to the life cycle and PMBOK do not follows a life cycle). If you see the table inside page 556 you will find that Close Project or Phase has no process inside it. So, it supposse that at this time all your process has been executed (all your activities has been completed) and the only thing you do inside it is to update documentation. Because of that some people in the past said that Close Project is an administrative activity only. I meant, when you go to a Close Project or Phase there is nothing to do except to update documenation. Saving Changes...
Hola Isabel. Can you identify what you feel is duplicated in the Close Project process? I reviewed it and did not see any activities related to contracts. There are, of course, accounting activities which are not procurement related. Saving Changes...
Joseph PanganSenior Principal Consultant| Genpact PhilippinesAngeles City, Philippines, Philippines
Hi Isabel,
In PMBOK v5, the process "Close Procurements" is under the Closing Process Group.
The "Close Procurements" process is removed from the PMBOK v6.
The Close Procurement process is now part of the Control Procurement process
...
1 reply by Joseph Pangan
Apr 30, 2019 10:11 AM
Joseph Pangan
...
Yes. What I am trying to say perhaps is that it is no longer a process of its own but of course, procurement should be closed, as part of the control process (v6), if conducted.
What I am also trying to point out is where the confusion may be coming from as it was part of the Close project process group in v5.
The Close Procurement process is now part of the Control Procurement process
Yes. What I am trying to say perhaps is that it is no longer a process of its own but of course, procurement should be closed, as part of the control process (v6), if conducted.
What I am also trying to point out is where the confusion may be coming from as it was part of the Close project process group in v5.
In PMBOK 6th edition state: "Activities related to the completion of the contractual agreements applicable to the project or project phase
such as: confirming the formal acceptance of the seller’s work,
finalizing open claims,"
it's not in control procurements we confirming the formal acceptance and close open claims?
...
1 reply by Andrew Soswa
Apr 10, 2020 2:00 PM
Andrew Soswa
...
Anas, I don't mean to undervalue your response but my comment is not directed to you but to those who create PMBOK and methodologies.
Are we sticklers to methodology? Or as PMBOK states, we need to adjust our methodology to our needs. It's the same question that Agile people have... if it is not Scrum, not Kanban, and just Agile, but it has some additions from waterfal, or even top-down methodologies - do we still consider it Agile? The Agile people say yes - and so following this trail of thought - everything is called Agile. The not-Agile people say no - but description falls outside naming conventions because they are not yet fully understood or established.
Saving Changes...
Andrew SoswaTechnology leader| Leading global financial institutionElk Grove Village, Il, United States
Apr 09, 2020 4:58 PM
Replying to Anas AL Saidi
...
In PMBOK 6th edition state: "Activities related to the completion of the contractual agreements applicable to the project or project phase
such as: confirming the formal acceptance of the seller’s work,
finalizing open claims,"
it's not in control procurements we confirming the formal acceptance and close open claims?
Anas, I don't mean to undervalue your response but my comment is not directed to you but to those who create PMBOK and methodologies.
Are we sticklers to methodology? Or as PMBOK states, we need to adjust our methodology to our needs. It's the same question that Agile people have... if it is not Scrum, not Kanban, and just Agile, but it has some additions from waterfal, or even top-down methodologies - do we still consider it Agile? The Agile people say yes - and so following this trail of thought - everything is called Agile. The not-Agile people say no - but description falls outside naming conventions because they are not yet fully understood or established. Saving Changes...
Close Procurements is the process of completing each procurement. It documents agreements and related documentation for future reference. It also involves administrative activities such as finalizing open claims, updating records to reflect final results, and archiving such information for future use. Close procurements process has been deleted from the PMBOK Guide Six Edition.
There is a good article regarding the topic. https://www.projectcubicle.com/close-procu...-close-project/ Saving Changes...
Dhaval JoshiSr. Project Manager| Dell TechnologiesHalifax, Nova Scotia, Canada
Hi everybody, trying to wrap my head around this scenario. You and your team completed all the work specified in the procurement statement of work and the final deliverable has been received by the customer. The customer has confirmed that the deliverable satisfies the contract requirements. From your perspective, what is the status of the project? My thought process is - The procurement is completed but someone pointed out that the procurement is in the closure process(The procurement must be closed before the project can be closed)? As Alice mentioned above, the close procurement process has been deleted from PMBOK guide six edition. Saving Changes...
