Need some clarifications..

Submitted by chullan88 on Sat, 04/26/2014 - 09:38

Following are some of the doubts which I came across during the prep.If anybody could throw some light,it would be of great help.

1)Work performance Reports

The Work Performance Data generated from Direct and Manage Proj. Work goes as input to all monitor and Control processes to give work performance information as output.this goes as input to the Monitor and Control process which gives Work Performance reports(status reports,recomendations).This is fed into the Integrated Change Control process.
Also it serves input to other three processes:-manage Project Team,manage Communications,control Risks,Control Procurements.Can anyone give an explanation to how WPR serves as input to these processes?

2)When are procurement documents created?

The stakeholder register needs procurement documents as an input.So it gets complete only after procurement documents are created(iteration).ritas process chart says procurement documents are created after the project scope statement is defined.any explanation?

3.The approved change requests goes as input only to the Quality and Procurement control processes apart from Direct and manage Project Work process.Why is this so?The approved change requests can have impact also on schedule as well.

4.The difference between Validated Changes and Approved Change Requests??

Thanks in advance

Forums: 
General Discussion
  • Log in to post comments
  • 94 reads
admin's picture

admin

Sat, 04/26/2014 - 11:05

Work performance information contains following
 
1. Status of deliverables. Like the % completion or number of deliverables completed
2. Schedule progress , activies started, in-progress and completed
3. Actual costs till date.
4. Acheived calue of technical performance measures, like system response time, number of errors per thousand transactions.
5. Implementation status of Change requests, defect repairs etc.
6. Status of Risks , new identified risks, effectiveness of risk response plan, management reserves or contingency reserves used.
7. Procurement related - like seller performance information, extent to Quality standards followed by them and warranties , invoices paid. 
 
This is like raw data gathered. 
 
So all this is an input to manage Project Team,manage Communications,control Risks,Control Procurements etc. 
 
 
 
4. Validate changes, - changes done and validated , approved changes are to be taken up for execution. 

kevinkkyip

Sat, 04/26/2014 - 13:15

1) For 'Manage Project Team', use of WPR is self-explanatory as project performance is somehow affected by team performance.  For 'Control Risks', it's mainly the variance analysis, EV data, forecast data etc. are used.  For 'Control Procurements', WPR are basically the seller's invoices, which detail the % or stage of completion and therefore can be viewed as kind of project performance reports before it would be processed through the Payment system.  My intepretation is that, in order to make informed decision for all these 3 processes, a more formal report with focus on cost, time & quality performance is preferred to just raw data.

2) Stakeholder register is a live document & needs to be constantly reviewed & updated.  Once there is a contract involved, the Procurement documents would provide information as to some of the stakeholders and their needs & therefore it's time to update the stakeholder register.

3) The 'Approved Change requests' input to 'Direct and Manage Project Work' would output 'Project management plan updates'.  The Schedule baseline may be updated in the process, if needed.

4) 'Approved change requests' is input to 'Direct & Manage Project Work' process to output 'Deliverables'.  'Deliverables' is then input to 'Control Quality' process to ensure the 'Approved change requests' is implemented properly.  If yes, the process would output the 'Validated changes'.
 

philstinnet

Sat, 04/26/2014 - 19:27

You have asked 4 nice questions. I will answer them one by one. 

Let's start with Point 2 - When are Procurement documents created ?

Let's take an example -  

1) You are a Project Manager for Rio Tinto.

2) Rio Tinto has mine operations all over the world.

3) Caterpiller (another company) is a supplier of mining haul trucks and other such toys to Rio Tinto and other such mining companies.  

4) One day Caterpiller proposes to Rio Tinto - "Hey man, you guys are buying our trucks and other services for many years. Why don't you sign a contract with us? As per the contract, we will give you the best deal in terms of cost and you will have to give us the promise that you will seek our tools or services in your projects."

5) Rio Tinto signs the agreement. 

6) Few years later, Government of Indonesia says that their geolists have found gold deposits in certain part of the country. But, the country does not have enough skilled labor or organization to dig out that gold. Therefore, it is seeking proposal from International Mining Companies.

7) Rio Tinto, Newmont, Freeport etc submit their proposals.

8) Government of Indonesia gives the contract to Rio Tinto.

9) Rio Tinto assigns you as a project manager to develop the mine in Indonesia.

10) You try to identify the stakeholders for this project. You look into that agreement (a procurement document) between Rio Tinto and Caterpillar. And, you identify Caterpillar as one of your stakeholder.

Got the gist ?

Now - keep in mind - this is only one example. This example does not mean that all the contracts are signed before the project is awarded. It is an example and a very true and real-life example.  

A procurement document (agreement) may have got created even before the project was conceptualized. Or it may get created during the project. Things do not follow a straight line track. Interactions and Iterations are going on all the time...

Hope it helps....

 

 

chullan88

Sun, 04/27/2014 - 06:08

Thanks philstinnet for the explanation

Waiting for the other answers..