Documente Academic
Documente Profesional
Documente Cultură
The tools are techniques for the Determine Budget process aren’t rocket
science. In fact, the whole process is really about adding up your
estimates, making sure nothing is overlooked and then presenting the
total as a summary figure.
Having said that, it does help to work through the process because it is
remarkably easy to overlook something and getting the budget wrong is
embarrassing (trust me, I’ve been there).
The tools and techniques you can draw on to prepare your project budget
are:
Cost aggregation
Reserve analysis
Expert judgement
Historical relationships
Funding limit reconciliation.
1. Create a WBS. Use the individual tasks identified within the WBS to
determine the resource requirement
A question of resource
By defining the independent and interlocking nature of each task required
by the project, the WBS helps to clearly pinpoint all resources needed at
each stage. These resources include ensuring the right people with the
relevant qualifications and experience are employed to oversee and work
on each task. When examining this, the project manager needs to take a
human resources management approach to project management.
Having the wrong people in place will have an adverse effect on quality,
cost, and time.
First, take your project task list. You might also have a work breakdown
structure and if you have one, it’s best to use that. But a task list will do as
long as it comprehensively covers everything that you need to do on the
project.
If you don’t have a task list, it’s time to create one. Write down everything
that you have to do and the things you have to build or make or complete
before the project can be finished. It doesn’t have to be in any particular
order, but it does need to include everything.
Finally on this step, brainstorm ideas with your project team, as there is
bound to be something you have forgotten. Many heads are better than
one!
10. Review your project. How effective was your project cost management?
The project leadership reviews the effect of trust—or lack of trust—on the
project and the effectiveness of alignment meetings at building trust. The
team determines which problems might have been foreseen and mitigated
and which ones could not have been reasonably predicted. What were the
cues that were missed by the team that indicated a problem was
emerging? What could the team have done to better predict and prevent
trust issues?
The original schedule of activities and the network diagram are compared
to the actual schedule of events. Events that caused changes to the
schedule are reviewed to see how the use of contingency reserves and
float mitigated the disruption caused by those events. The original
estimates of contingency time are reviewed to determine if they were
adequate and if the estimates of duration and float were accurate. These
activities are necessary for the project team to develop expertise in
estimating schedule elements in future projects—they are not used to
place blame.