BSBPMG514
BSBPMG514
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
• Identify the specific activities and milestones. The activities are the
tasks of the project. The milestones are the events that mark the
beginning and the end of one or more activities.
• Estimate the time required for each activity. Weeks are a commonly
used unit of time for activity completion, but any consistent unit of
time can be used. A distinguishing feature of PERT is it's ability to
deal with uncertainty in activity completion times. For each activity,
the model usually includes three time estimates:
o Most likely time - the completion time having the highest probability.
1. The hardest project budget you’ll ever write is the first one. After
that, you have both a model for budgeting similar projects, and the
experience for writing detailed budgets going forward. For your first
budget, get help from an experienced team member or mentor. If you’re
a collaborative group, get input from everyone’s work estimates. The
point is, you don’t have to do this alone.
2. Learn from other projects. Find a past project that was similar in type
or scope to the current one, and use it a model. Some teams turn to
their project management tool to mine data and information on how
much time and money went into certain projects—and identify where
resources were added or subtracted.
3. Know your core costs. Start by entering costs—the absolute must-
haves to get the project up and running. They include team members,
equipment, software, travel, etc. Next, compare those core costs to the
total budget. If your costs fit under the total cost figure, you fit under
the cap. If not, you need to have that first conversation with your boss
or stakeholders about how to scale the project to be completed within
the budget—or about expanding the budget.
4. Prepare to change budget estimates. Most initial estimates are just
that—estimates. With the common occurrences of scope creep,
unexpected surprises and the nature of doing business, at some point in
the project the budget can easily change. This fact just underscores the
need to manage the project budget continually. Vigilant project manager
compares actuals-to-date against the initial budget and then against
anticipated costs toward completion at regular intervals. And then it’s
time to tweak the work plan to bring expenses in line with the total
budget.
5. Monitor resources. You want your team members working on the
right tasks to their full potential. Salaries are a big component of the
budget, so review resource usage weekly to make sure that everyone is
working the highest priorities and putting the proper amount of hours
per week into their tasks. A project management tool with strong
resource leveling features can help manage this.
6. Be transparent. Keep your team informed of the evolving budget
forecast. Communicate what’s expected of them to stay within budget.
People might start watching how they designate hours and other costs
to your project. And they’ll understand any requests to change
directions if they come up.
7. Manage scope. Scope creep busts budgets. To avoid unplanned work
that leads to cost overruns, create change orders for work that goes
beyond initial project requirements, with accurate projections of
additional cost. Seek additional funding for the project to cover change
orders.
• Monitor all costs and ensure that they remain aligned with the
forecasted budget
• demonstrate accountability
While all cost-benefit analyses have these common characteristics, the level of
analysis required will differ depending on the project’s complexity, risk pro le
and sensitivity and the level of financial and economic resources required to
implement the project.
The decision making process for the application of these Cost-benefit analysis
guidelines are listed in Table 1 and are outlined in greater detail in the
following sub-sections of this document.
Not everyone is right for every task. Even though you try to hire well-rounded
team members, there will always be areas where one outperforms the rest.
Know your team’s strengths and weaknesses. Be familiar with their work habits
and attitudes, so that you can accurately predict how long it will take someone
to do a particular task.
Many project managers rely on the “planned vs. actual” system, which can
predict how timely a project is, but says nothing about budget management.
Earned Value Analysis is a much more effective method. It uses three factors:
cost, schedule, and scope, in order to predict completion dates, future team
performance and the likely end cost.
4. Move On
When one of your team members gets bogged down in a task, ask yourself this
question: “Is it essential to the project as a whole?” Many project managers
employ the “critical path” method, where there is a “chain” of tasks that are an
absolute requirement for the project to be considered complete. If the
problem is for a secondary (or even tertiary) task, you may be better off
shifting to something else and coming back to it later—even if it means setting
a whole chain of secondary tasks aside.