Project Management

The Money Files

by
A blog that looks at all aspects of project and program finances from budgets, estimating and accounting to getting a pay rise and managing contracts. Written by Elizabeth Harrin from RebelsGuideToPM.com.

About this Blog

RSS

Recent Posts

Who really owns the project budget? Clarifying financial accountability

How to learn AI the sensible way

Making sense of project cost reports

How real PM mentoring actually works

The Accidental Product Manager: What project managers need to know

Categories

accounting, agile, ai, appraisals, Artificial Intelligence, audit, Backlog, Benchmarking, benefits, Benefits Management, Benefits Realization, Bias, books, budget, Business Case, business case, business case, Career Development, Career Development, carnival, case study, Change Management, checklist, collaboration tools, communication, Communications Management, competition, complex projects, Conferences, config management, consultancy, contingency, contracts, corporate finance, corporate finance, cost, Cost Management, cost management, credit crunch, CRM, data, data security, debate, Decision Making, delegating, digite, earned value, Education, Energy and Utilities, Estimating, events, FAQ, financial management, financial management, forecasting, future, GDPR, general, Goals, Governance, green, Information Technology, Innovation, insurance, interviews, it, Knowledge Management, Leadership, Lessons Learned, measuring performance, Mentoring, merger, methods, metrics, multiple projects, negotiating, Networking, news, Olympics, organization, Organizational Culture, outsourcing, personal finance, Planning, pmi, PMO, PMO, Portfolio Management, portfolio management, presentations, privacy policy, process, procurement, product management, productivity, Program Management, project closure, project data, project delivery, Project Success, project testing, prototyping, qualifications, Quality, quality, Quarterly Review, records, recruitment, reports, requirements, research, resilience, Resource Management, resources, risk, Risk Management, ROI, salaries, Schedule Management, Scheduling, scope, Scope Management, security, small projects, Social Impact, social impact, social media, software, software, software, Stakeholder Management, stakeholders, Strategy, success factors, supplier management, team, Teams, testing, testing, timesheets, tips, training, transparency, trends, value management, vendors, video, virtual teams, workflow

Date

5 Factors That Affect Estimates

linkedin twitter facebook Request to reuse this  

Factors that affect estimates

When you are trying to put estimates together, whether it’s for time or cost, it’s important to be as accurate as possible because the estimates form the basis of your plan. They also set the expectations of your stakeholders, so getting them right – or as close to ‘right’ as possible – makes for an easier project for everyone.

So, what things could affect your project estimates? Here are 5 things to look out for when putting your estimates together – whether it is you doing the estimating or someone on your team.

1. Optimism Bias

We are predisposed, most of us, to look on the bright side of things. How long will it take me to drive there? 20 minutes? Then you do it and realise it took 40.

Being positive is fine, but it’s not realistic most of the time in a project environment. We need to look out for where being overly optimistic, or even just a little bit optimistic, is going to have an implication for the project.

Manage it by: Have several people do the estimate and then take an average. PERT is also a good estimating technique to use if you are worried about estimating bias because it takes best and worst case scenarios into account.

2. Pessimism Bias

I don’t know if this is actually a thing, but it’s the opposite of people being too optimistic. Estimates are either deliberately padded with extra contingency or people are unrealistically negative about the amount of time it will take them to get the work done.

Manage it by: PERT again. If you don’t want to use that, then at least get the estimates peer reviewed so that any that are unrealistic can be weeded out.

3. Experience

The experience of the estimator makes a huge difference.

Manage it by: Finding people who are skilled at what they do to work on your estimates. If you can’t get estimates done by the most experienced people in the room, then again a technique like PERT will help average them out. Alternatively, look outside your immediate team or company for people who could help you estimate.

4. Timescales

Have to do an estimate quickly? It’s not going to be very good because you won’t have had time to check out all the assumptions. Rushing makes for poor estimates.

Manage it by: Build enough time into the plan to do a decent job of estimating. If you absolutely have to have a quick turn around on  estimates get your best people on it and make sure that the person asking for the estimate knows that it is of the ‘quick and dirty’ kind.

5. Incorrect Spec

If you estimate from a specification or set of requirements and then find out that these are wrong, you are necessarily going to be wrong in your estimate too. Whether it’s because the users want more put in or some elements taken out, you’ll have to adjust your estimates as well.

Manage it by: It would be lovely to say that you must insist on fully-thought out estimates every single time but I know that isn’t realistic. You can only do your best and have a great change control process in place to deal with the changes when they happen along the way.

What else do you think affects the quality of your estimates? Let us know in the comments.

Posted on: September 12, 2016 12:00 AM | Permalink | Comments (17)

Timetracking Questions! [Video]

Categories: video, timesheets

linkedin twitter facebook Request to reuse this  

In this video I talk about some of the commonly asked Q&A around timetracking, especially about people feel about filling them in. For example, what about those experts who only want to take part in your project when they can cross-charge you for their time?

Posted on: September 05, 2016 12:00 AM | Permalink | Comments (1)

Payback Period: A Beginner’s Guide

Categories: business case

linkedin twitter facebook Request to reuse this  

Payback period is an investment analysis technique and it’s personally one of my favourite tools to use for investment appraisal because in my view it’s the easiest to understand of the tools at my disposal.

Today I’m going to work through an example to show you what it looks like. But before we do that, let’s remind ourselves why we might want to use it at all.

Why Do An Investment Appraisal?

Investment appraisals are what goes into your business case to show why your project is financially viable. They are decision-making tools.

The investment appraisal also allows the decision makers to compare your project with others, which they’ll need to do as all the projects are competing for the same corporate funds. The figures from the investment appraisal, and the associated blurb in the business case, confirm why the project is worth the investment based on forecasted cost and time. It justifies the project based on the expected benefits.

So, investment appraisals matter because they help get your business case approved. Obviously, if the numbers don’t stack up then your project doesn’t get approved. Investment appraisal techniques help you show the cost and benefits of your project in a way that makes it easy to compare with others.

What Is Payback Period?

There’s a little video I made about payback period here, but in essence it’s this:

Payback period is the time taken to recoup the project investment.

Let’s take an example.

A project costs £1,000,000. The benefits are:

  • Year 1: £500k
  • Year 2: £300k
  • Year 3: £200k
  • Year 4: £200k
  • Year 5: £200k

As you can see from the graph below, the project investment equals the benefits for the first three years, so the payback period is three years.

Payback period

In other words, you’ll earn back the amount spent on the project through the project’s benefits once three years have passed. At that point you ‘break even’. Benefits from Year 4 are cash in the bank.

From a business case and project justification point of view, the shorter the payback period, the better.

Problems With Payback

So far, so straightforward.

The problems come when you try to be a bit more sophisticated.

For example, payback period doesn’t take into account discount rates (how much money will be worth in the future: is the £200k benefit in Year 4 really worth the same as £200k would be today?).

As with all investment appraisal techniques you can’t measure intangible benefits in this way. Payback is only good for working out the financial side of benefits: the monetary cost and the financial benefit gained.

That makes payback period a bit crude but as long as everyone is aware of the limitations, it can still be a useful tool to forecast when the project will break even and start to turn a profit.

There are other ways that you can put financial information into your business case: Net Present Value and Discounted Cash Flow are others.

What investment appraisal techniques do you use?

Posted on: September 02, 2016 10:49 AM | Permalink | Comments (4)

7 Things That Should Be In Your Project Business Case

Categories: business case

linkedin twitter facebook Request to reuse this  

Always a fan of a snazzy graphic, I put this one together to summarise the things that you should be including in your project business cases.

Do you (or your management team) include all of these in your business case template? What else do you think should be in there that I haven't covered below?

7 Things That Should Be In Your Business Case

Posted on: August 20, 2016 11:28 AM | Permalink | Comments (6)

Ask The Expert: Eileen O’Loughlin on Collaboration Tools

linkedin twitter facebook Request to reuse this  

My irregular Ask The Expert feature is back! In today’s interview I talk to Eileen O’Loughlin, market research associate at Software Advice, about trends in collaboration tech, building a business case for investment and more. We started by talking about the nature of the teams that use these tools.

Eileen, what sort of teams work remotely?

All sorts of teams can work remotely. Advances in communication and collaboration software help facilitate a standardized work environment for employees across industries whether they’re in or outside the office.

In fact, a report by WorldatWork found that in 2015, 80% of North American companies offered telecommuting and flexible work arrangements as a competitive benefit.

That being said, we see a high number of remote workers in more tech-centric industries, such as IT services (and related software and technology fields) as well as marketing and advertising. These fast-paced industries use project management software to help structure their workflows and increase communication and collaboration among employees.

In your experience, what does remote collaboration look like? Do you always need software to do it?

Although teams don’t require specialized collaboration software (after all, as our analysis has shown, email remains one of top go-to communication tools used by remote teams), collaboration software has capabilities not available in other methods that benefit the user tremendously.

Take a marketing team, for example. Using a collaboration tool with content management functionality, teams can upload and store documents in a centralized location, share files, track changes—even edit the same document in real-time.

That same team trying to collaborate over email faces version control issues, productivity loss due to a lag between responses, not to mention the potential for error and miscommunication over long email threads.

Yes, I can see that being the case. How can you justify the cost of adding new software into your business when it's hard to measure the ROI?

The business case for investing in a collaboration platform can be made easily. Studies have shown that on average, less than 40 percent of an employee’s time is spent on work-related tasks. The rest of their workweek is spent coordinating and communicating with team members. As such, a platform that helps streamline this process can increase worker productivity and provide sufficient ROI.

Wow, that’s really interesting! Any other tips for helping build a case?

Collaboration software helps centralize a team’s communication and collaboration efforts. Managers can create schedules, assign tasks to workers and track the time it takes each worker to complete each task. Team members know what is expected of them and when it is due.

Team calendars are a common feature of collaboration software. These tools provide managers with visibility into employee workloads, current and future availability and can even help identify issues before they become problems. For example, managers can set up automatic notifications to alert employees of an impending due date, prior to the deadline being missed.

Are you noticing any trends in remote collaboration and the growth of virtual teams?

One trend that stands out is the shift toward BYOD collaboration. Cloud-based collaboration software can be accessed from any location, on any device with an internet connection. Employees that have a personal mobile device, such as a laptop, iPad or even a smartphone, are already set up to work remotely.

Why do you think BYOD is taking off?

Many employees prefer to use their personal devices, due to familiarity and convenience. With BYOD, organizations have more freedom to invest in a software that connects employees, rather than spending on office hardware.

So where do you think collaboration software is going next? More consolidation in the marketplace or more explosion? And what does that mean for managers?

The mobile workforce is growing at an exponential rate. As such, it’s imperative that remote employees—and the managers of remote employees—are comfortable relying on technology to communicate.

Managers should take steps to ensure that requirements for virtual teams are clearly defined and understood by both parties. For example, if remote workers need to be active in a group chat, or have a one-on-one video call with their manager once a day or once a week. Carefully outlining any rules and regulations helps create trust between management and remote staff.

Thanks, Eileen!

More about my interviewee: Eileen O’Loughlin is a Market Research Associate at Software Advice. She joined the team in 2015 and covers the accounting, project management, legal management and professional services markets.

Eileen received her B.A. in English Writing and Rhetoric from St. Edward’s University in Austin, TX. When she’s not in the office, Eileen enjoys spending time outdoors, visiting with friends and family or reading a good book.

Posted on: August 15, 2016 12:00 AM | Permalink | Comments (1)
ADVERTISEMENTS

Women, poets, and especially artists, like cats; delicate natures only can realize their sensitive nervous systems.

- Helen M. Winslow

ADVERTISEMENT

Sponsors