Radha IyerVice President, Global Data Loss Prevention| Deutsche BankChantilly, Va, United States
Does anyone know if there is an industry standard or rule of thumb to determine the Project Management hours for a typical development project? If the Dev +QA + Architecture = 2000 hrs, how much shoud the Project management hours should be? I have 15% as the baseline in some companies. Could someone please guide? Saving Changes...
Sylvain CostyCIO| Handball French FederationDraveil, France, France
For an ERP project (rollout, integration...) there is some ABACs like :
- Governance : 15%
- Consulting : 55 %
- Engeneering : 30%
But it is just lesson learned : each context is different but this is a good basis for estimating Saving Changes...
Jeanine de AlmeidaSenior Project Manager| NTT LtdBrisbane, Qld, Australia
I don't understand how we can estimate PM hours based on engineers total hours not considering the project duration. Let's say that a project require 80h of an engineer, according to some feedbacks above, we would estimate 8-16h for PM. What if the project will take 10 weeks of duration. Every week the PM will have to have meetings with the client and the engineer, update the schedule, issues and risks and send updates to the client. It means that the PM will spend much more than 0.8-1.6h per week. So, in my humble view, we always have to take in consideration the project duration to estimate the hours required to manage a project.
...
1 reply by Bryant Baker
Sep 14, 2020 11:03 AM
Bryant Baker
...
Hello Jeanine. Some questions to consider:
- If there is not much happening in the project, would you need as much time to update these communication objects (schedule, issue list, etc.)?
- Would it be possible to change the frequency of these updates, based on effort expended? Using your case, what if you refreshed these communication objects for every 16 or 20 hours of engineering effort expended?
Saving Changes...
Bryant BakerProject Manager| State of Delaware - Office of PensionsDover, De, United States
Sep 14, 2020 4:03 AM
Replying to Jeanine de Almeida
...
I don't understand how we can estimate PM hours based on engineers total hours not considering the project duration. Let's say that a project require 80h of an engineer, according to some feedbacks above, we would estimate 8-16h for PM. What if the project will take 10 weeks of duration. Every week the PM will have to have meetings with the client and the engineer, update the schedule, issues and risks and send updates to the client. It means that the PM will spend much more than 0.8-1.6h per week. So, in my humble view, we always have to take in consideration the project duration to estimate the hours required to manage a project.
Hello Jeanine. Some questions to consider:
- If there is not much happening in the project, would you need as much time to update these communication objects (schedule, issue list, etc.)?
- Would it be possible to change the frequency of these updates, based on effort expended? Using your case, what if you refreshed these communication objects for every 16 or 20 hours of engineering effort expended?
...
1 reply by Jeanine de Almeida
Sep 14, 2020 10:48 PM
Jeanine de Almeida
...
Thanks for your reply Bryant. That's exactly my point. The minimum hours per week will be required even if there is no much happening in terms of technical work. We still need to have internal meetings with the engineer(s) to confirm everything is on track, is there is any new issue or risk, we still need to update the client on the progress, and also do the project financials. Hence, in my view, the project duration is essential to estimate PM hours.
Saving Changes...
Jeanine de AlmeidaSenior Project Manager| NTT LtdBrisbane, Qld, Australia
Sep 14, 2020 11:03 AM
Replying to Bryant Baker
...
Hello Jeanine. Some questions to consider:
- If there is not much happening in the project, would you need as much time to update these communication objects (schedule, issue list, etc.)?
- Would it be possible to change the frequency of these updates, based on effort expended? Using your case, what if you refreshed these communication objects for every 16 or 20 hours of engineering effort expended?
Thanks for your reply Bryant. That's exactly my point. The minimum hours per week will be required even if there is no much happening in terms of technical work. We still need to have internal meetings with the engineer(s) to confirm everything is on track, is there is any new issue or risk, we still need to update the client on the progress, and also do the project financials. Hence, in my view, the project duration is essential to estimate PM hours. Saving Changes...
Typically across IT projects of any size and once the total work effort for all other resources has been determined, I’ve found the % effort required for the project manager has been between 15 and 40%. The lower percentage would apply for smaller and well known scopes of work and higher percentages for implementations of newer products/technology and where the customer or recipient of the services requires a lot of guidance. Saving Changes...
