Test# 5 Q167 Closing process actions

Discussion in 'PMP' started by _30498, Aug 11, 2018 at 2:32 PM.

  1. _30498

    _30498 Active Member

    Joined:
    Apr 26, 2018
    Messages:
    17
    Likes Received:
    0
    Which of the following is the correct order of actions that you must take during the closing process?
    A. Get formal acceptance, release the team, write lessons learned, close the contract
    B. Write lessons learned, release the team, get formal acceptance, close the contract
    C. Get formal acceptance, write lessons learned, hand over deliverable to stakeholder(s), close the contract
    D. Get formal acceptance, close the contract, write lessons learned, release the team

    I selected D. The correct answer is C.
    explanation is
    1. release the team is no longer the part of Closing process. However, is one of Key Benefit of Closing process is team resource are released?
    2. closing contract is the last step.
    My questions are
    1. how to get formal acceptance before hand over deliverable?
    2. the "contract" here is "project contract" or "procurement contract"?


     
    #1
  2. tim jerome

    tim jerome Well-Known Member
    Trainer

    Joined:
    May 15, 2015
    Messages:
    1,342
    Likes Received:
    369
    First of all, there are Two (2) actions you may consider 'formal' acceptance. One occurs in Validate Scope, which creates the Accepted Deliverable. This means that the deliverable is complete, and we have concensus. This means work can now cease.

    The Accepted Deliverable is then routed to Close Project or Phase. This is where you are questioning Formal Acceptance - this process. The formal acceptance in this process is not to state we have a deliverable complete, but to ensure that the final owner is ready to receive the deliverable - it is specifically used to transition the deliverable. This will occur before you hand over the deliverable.

    The other actions are secondary to the transition, but we can discuss them if you wish. To your other questions:

    We release the teams whenever necessary - when the team members have no purpose on the project. Close Project or Phase ensures this is concluded.

    We capture and archive lessons learned. We ensure this is complete. Close Project or Phse ensures this is concluded.

    This is key - Close Process or Phase is wrapping all these activities up and concluding them. Again (as an example), harvesting lessons learned has been occurring constantly, and now we prepare for final archive.

    I think we discussed the Formal Acceptance question above.

    The contract (for the purposes of the exam) is GENERALLY a contract where you are outsourcing a piece of your project - you are the buyer. There may be instances on situational questions you are stated to be the seller. Start off with the Buyer's perspective, you'll get more right than wrong.
     
    #2
  3. _30498

    _30498 Active Member

    Joined:
    Apr 26, 2018
    Messages:
    17
    Likes Received:
    0
    Thanks, Tim!
    PMBOK uses "accepted deliverable". some other sources use phase as "formal sign off from customer/buyer" i think these wording is very confusing.
     
    #3
  4. tim jerome

    tim jerome Well-Known Member
    Trainer

    Joined:
    May 15, 2015
    Messages:
    1,342
    Likes Received:
    369
    "Accepted Deliverables" has a very explicit meaning - deliverables are complete and we have consensus. Complete means that User Acceptance Testing is successful, and we can stop work.

    There really isn't such a specific definition for the acceptance in Close Project or Phase, but we do call it generally 'formal acceptance' (for the purpose of transitioning the deliverable). In one way or another, you will be tested on accepted deliverables. Just remember that there is another formal acceptance as well.
     
    #4

Share This Page