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

How To Manage Using Artificial Intelligence

Categories: future

linkedin twitter facebook Request to reuse this  

I’ve been thinking about a webinar I’m putting together and Artificial Intelligence is on the topic list to discuss during that session.

It’s a trend that project managers and business leaders can’t afford to ignore, but it’s not yet clear to me how it will help businesses do anything particular. In other words: it’s a good theory and I can definitely see the applications, but how do I use it?

In doing some research for that webinar I’ve been digging in to AI in more detail and clarifying my thoughts.

Here’s where I am up to.

Forbes shares survey results from Narrative Science that show that by 2018, more than 60% of all companies are anticipated to use a form of AI programming to manage some aspect of their business. They also cite a study from Forrester that says despite this growth, around 40% of companies currently have no plan for how smart technology can help manage their business.

So we know it has the potential to be great, we just don’t know how to harness it.

Understanding A.I.

Smart software consists of customized algorithms designed to scan large amounts of data very quickly, displaying the output in an easy-to-understand, elegantly designed presentation. The tools don’t actually do any “thinking”; they just look like they do.

You will likely need to do some work to set the any AI programme with your existing infrastructure. But, once you do, you can reduce a formerly mundane and repetitive task to the click of a button! At least, that’s the theory.

Where are the applications, then?

Reliable Recruitment

The internet has become a double-edged sword when it comes to hiring for your team. On the one hand, the rapid communication and social media sites allow leaders to be instantly linked with highly skilled workers from all over the world, with full access to their work history, résumé, and portfolio. On the other hand, there are simply too many sites and too many candidates to possibly review them all.

Project managers and team leaders have better things to do than sift through CVs and this is where AI can help.

Organizations have begun using AI software to scan through the millions of online CVs, across dozens of social media sites, to find the skills and experience that they are looking for, leaving you more time to actually sit down and interview only the most suitable candidates.

Customer Service

You may have noticed that more and more websites now offer round the clock support on their websites. Many don’t even have any waiting time when you open a chat. Intercom does this, and there are Facebook bots that run through Messenger doing a similar job if you engage with a page, sign up to an event or similar.

 And yet...the advice you receive sounds too human to be a pre-programmed response.

Those pre-programme responses aren’t a human waiting in the wings. Chatbots are AI programmes designed to take the pressure off your customer service teams. As a replacement for first-line support, chatbots analyse a customer’s message for key words, scan a database of predefined answers, and then customise a response so lifelike that most humans can’t even tell the difference.

I think that will change in time though, as customers get used to dealing with bots and can pick them out.

Finance Management

Making sense of your project financial data is another area where AI can help. Whether it is scanning projects in the portfolio to better manage investment across the business and capitalise on projects with the most attractive profit projections, or isolating key products and departments where money is being lost, AI can help keep your leadership team ahead of the curve.

This is definitely an area where portfolio management teams should be looking out for advances. We have so much financial information trapped in our project management tools that it’s ripe for processing in an AI way.

I’m sure many project management tools will catch up but for now I’ve seen this done mainly in financial management packages, the kind your Finance team would be using. For example, Sage’s chatbot, Pegg, monitors all your accounts, your income and your expenditure, and provides real-time data as though you were texting your accountant...only Pegg responds faster.

This could be great for small project management firms like design agencies, but even bigger companies using products like this could benefit from not having to dig into the Help files every time they wanted some info. Or maybe project managers could be given access to view some of the financials relating to their projects? It would be a huge help to me when dealing with suppliers if I could use a chatbot to find out if an invoice had been paid.

So, whether you’re already using Facebook’s “Insights” to track who is interacting with your PM training page, or if your heavy machinery could benefit from a programme which tracks sensory data and automatically orders replacement parts when they are needed, AI is the means for taking all that data you’ve been collecting about your company and finally making sense of it.

Do you already use AI in your business? On your projects somehow? Let us know in the comments. You never know, you could end up as a case study in my next webinar!

Posted on: October 05, 2017 06:59 AM | Permalink | Comments (8)

Project Reporting by Role

Categories: reports

linkedin twitter facebook Request to reuse this  

Or: Who Does What When It Comes To Project KPI Reporting

So many KPIs, so little time! There are reporting requirements at every step of the project and at all points in the hierarchy. Not sure who on the team should be involved in what kind of progress tracking? Here are some pointers for who should report what. Adapt these to fit your team, but it’s a good starting point.

Team Member

They should analyse the work they have done themselves, so they’re reporting on progress made and work still to do. And time sheets, if you use them.

There’s an overlap here with skills required, so you’ll need to get them involved with upcoming planning to ensure that they are capable of doing the tasks – otherwise it will take them muhc longer and with much worse outcomes in terms of quality.

Project Manager

Project-level analysis relating to project planning and budgeting. If this is you, you’ll complete the project dashboard and summarise the project performance metrics.

Programme Manager

If this is you, you’ll be doing programme level reporting, using inputs from the project managers. As your programme is probably broken down into stages, you can report actual progress (on all the projects) against the forecasted progress for the stage. Do  this for time and budget as a minimum.

There may also be other programme level key performance metrics that you choose to track such as resource allocation across the project with a view to managing skill levels.

Portfolio Manager

The kind of thing you’re reporting on is even more rolled up than that of Programme Manager. You’re looking at analysis by the type of work carried out, progress across phases and stages of programme against forecast and juggling the budgets across the portfolio so you’ll want to know top level budget performance to feed into portfolio metrics.

Look at metrics related to time to complete work so you’re also keeping an eye of capability and performance as well as time/cost/quality of the work done.

Director/Executive

As a project sponsor, you’ll want to digest the project-level reporting from the project manager. But as a senior exec responsible for diverse portfolios, your data needs are more aligned to the governance and strategic functions you perform.

Look for metrics that analyse time for the different types of work that you have in the business. Splitting activities by runners, repeaters and strangers is a good starting point, and then you can apply the governance metrics to those.

‘Runners, repeaters and strangers’ is a Lean technique to help you know where to concentrate your efforts.

  • Runners are things your team is working on all the time: normal processes and tasks you require to be completed every day. For example, the fundamental customer service processes for selling your products.
  • Repeaters are the activities that you see regularly but they aren’t daily occurrences. For example, handling complaints or the change management process.
  • Strangers are activities that rarely happen, like a one-off project to close down a facility and lay off 100 staff.

As an exec, look at the time/cost analysis relating to these tasks to see if the business is spending its resources wisely.

Posted on: September 26, 2017 08:00 AM | Permalink | Comments (10)

How To Deliver When Your Project Budget is Cut

Categories: budget

linkedin twitter facebook Request to reuse this  

Budget cuts… this is something every project manager faces at some time in their career. Your healthy budget of whatever is suddenly subject to scrutiny because your sponsor’s department has been told to find savings of X% and all projects are at risk.

Then you find that your project has generously ‘handed back’ a sizeable amount to the corporate coffers. And yet somehow you’re still expected to carry on.

The good news is that in situations like this your project sponsor will know what has happened and should be broadly sympathetic to the idea that they can’t have everything they wanted after all. If the money isn’t there, they know you’re going to have some limitations on what you can deliver. But where do you start with that conversation?

Start With the Requirements

A closer working relationship is exactly what you should be aiming for when budgets are stretched. The more you can understand what it is your customer wants – in really granular detail – the better it is for everyone as you’ll (hopefully) be able to come up with solutions that achieve the ‘right’ outcomes in a cost-effective way.

Check that there’s nothing extra that has found its way into the scope. Check that you understand what’s expected from the contract so that you aren’t inflating or gold plating anything unnecessarily. What could you lose from scope (with everyone’s agreement) that would still end up with the customer getting broadly what they wanted?

Look at the processes and bureaucracy involved in getting the work done: often closer working relationships can strip time out of these processes and time is money, so there could be savings there.

Basically, think collaboratively about what’s possible. Lean in.

Stagger the Work

Look at what could possibly be removed from the initial scope of your project and pushed to a further delivery phase. Financial years are cyclical – there might be more money available next year to finish a particular element. Consider what parts of scope you could agree to postpone.

Small Changes Make the Difference

It’s rare that you’ll be able to make one sweeping change to your project and have all your financial issues go away. Rather, you’ll be making lots of smaller changes and tweaks across the board with a view to improving the budget position holistically.

Together, small changes really do add up. Unfortunately, identifying the right small changes and doing the planning work to incorporate lots of changes does take time. You might want to slow down progress on your project while you’re doing all this reforecasting work as you don’t want to incur additional (and perhaps unnecessary cost) at this time.

Work with your project sponsor, key suppliers and other people on the team to look at where savings could be made that would contribute to meeting the financial challenges overall.

Keep Talking

Projects move on and evolve frequently, and if you hit a problem that is going to affect the budget you should bring that to the attention of the project sponsor straight away. You should do that anyway, but in times of financial pressure and when your budget is challenged, it’s even more important to involve them in the planning and response to issues when money is at stake.

Keeping honest communication channels open is also helpful for building trust, and it ensures that you hear about changes that might affect you. For example, there might be more budget that needs to be reallocated, or you might be lucky and find that some extra cash is flowing your way.

How Much is Too Much?

In an article for PMToday Magazine way back in March 2010, John Judge explained the four stages of budget cuts, which I’ve elaborated on here:

  • Budget cut by up to 15%: you can work within reasonable cost reductions across the project and hopefully minimise the impact on the project scope.
  • Budget cut by 15-25%: more noticeable scope impacts with likely impact on the functionality of your end result as well.
  • Budget cut by 25-35%: you’ll have to look seriously at what can be removed from scope or deprioritised, or moved into a future phase or the next financial year.
  • Budget cut by >35%: consider pausing closing down the project as with this level of cuts it’s unlikely that you’ll be able to deliver effectively.

These are useful rules of thumb, but it does beg the question: if we can manage with budget cuts of up to 15%, why don’t we stretch ourselves to deliver under budget by that amount anyway?

Do you think you could cope if you lost 15% of your budget tomorrow? Let us know in the comments section!

Posted on: September 18, 2017 06:00 AM | Permalink | Comments (7)

5 Differences Between Project Accounting & Financial Accounting

Categories: budget, accounting

linkedin twitter facebook Request to reuse this  

In this video I share 5 differences between what it means to do accounting on your project (and manage the financials/budget) and how financial accounting can work. Understanding these differences makes it easier for you to work with your Finance teams and run your project budgeting processes.

Posted on: September 13, 2017 08:00 AM | Permalink | Comments (5)

How To Manage A Project Audit

Categories: reports, PMO

linkedin twitter facebook Request to reuse this  

So your project is being audited? Lucky you! There’s quite a lot to think about if this is happening to your project, whether the audit is a formal thing or whether you’ve been selected as the project that’s being scrutinised by the PMO this month as part of an informal ongoing review process.

But auditing isn’t that big of a deal if you know what to expect. Every audit process is going to be slightly different but here are some common things that you can prepare for.

project audit process

Provide The Information

The first step is that you’ll have to provide a whole pile of information to the people doing the audit. Whether that’s your best mate from the PMO or a scary-looking external auditor, they’ll give you a list of the kind of things they want to see. This will include:

  • Your plans and project initiation document
  • Latest project reports and budget spreadsheet
  • Risk, issue and change logs
  • Process documents
  • Test scenarios
  • Access control information or policies
  • Strategies that relate to your project such as your approach for data consolidation, cleansing or validation or coding quality approaches.

The auditor (or audit team) will then take some time to go through all of this. It’s likely to be around two weeks as there’s a lot to digest, and they’ll want to understand it so they might come back to you with follow up questions.

They’re preparing to dig deep into the material and establishing what else they might need to know.

First Meeting

Once the audit team has reviewed your paperwork, they’ll start digging more deeply into the project. At your first meeting (for which there should be an agenda so you can prepare adequately in advance), expect to be taken through a list of points. Consider this the orientation meeting.

It can help if you provide an overview of the project and the objectives as part of the scene setting so be prepared to do that on the spot if asked.

Use the time to really understand what is expected of you and what the process is going forward. For example, what are the reporting expectations during the audit period? If they are asking you for updates, how long will you have to put those together and send them over? In what format?

And if you are expected to make changes to the way you are doing things (which might not be at the request of the auditors but by your manager or the PMO perhaps) then how long will you have for doing that?

Try to establish what the outcome of the audit process will be – they should be able to tell you, and should be able to explain what input you will have to the format and content of the final report. There should be a process by which you can comment on a draft and put your points across before anything is published to senior management.

Find out what your management team or project sponsor intends to use the audit output for, so you can better prepare for any action that is coming your way at the end of the audit.

Follow Up

Following the first meeting you should expect lots of emails! The auditors may want to speak to people in your team or subject matter experts, so make the right people available. If you are submitting follow up or additional documentation you may need to upload this to a secure online repository (if they are external) or provide it over email. There are lots of documents whizzing around in a formal audit situation so try to keep track of what you’ve sent to whom and when.

You might find that after a flurry of activity it all goes quiet for a while. This is the time when the report is being written up. Try to find out when the draft will be coming to you for review so you can block out some time to look at it and add your comments. Be honest in your commentary back but be prepared to challenge anything that you don’t think is accurately representative of your project or the processes being used to manage it.

All that sounds quite daunting but taking part in a project audit shouldn’t be scary – it’s just time consuming and a drain on your team’s resources while you are also trying to get work done. Make sure that your stakeholders and project sponsor know what is going on so that they can give you a bit of grace when it comes to short deadlines and the like during the audit period.

Audits like this won’t take more than about 8 weeks start to end as a maximum, from finalising commercial terms and the engagement letter that kicks off the audit process with an external group to the submission of the final report. However, that time can drag when you are trying to hit project milestones and keep all the plates spinning as well!

Remember that audits are supposed to be highly useful, informative exercises, whether that’s a formal external review or an informal assessment by your PMO peers. The outputs are going to help you manage the project more effectively and get better results for the business, so don’t take the recommendations personally and work together with your team to put the advice into action. Not everyone is lucky enough to go through an audit and what you learn can be invaluable to helping you manage future projects more effectively.

Posted on: September 08, 2017 08:44 AM | Permalink | Comments (12)
ADVERTISEMENTS

Solutions are not the answer.

- Richard M. Nixon

ADVERTISEMENT

Sponsors