How to keep a project simple

Project management success - how to keep a project simpleSometimes I am asked to act as a Project Management consultant on a project where the customer really needs to have a project manager but isn’t willing to put the money into having someone manage the project properly.  This is a difficult ask – after all, if you want the project to be well managed then you need to invest in the project management!  I have recently been involved in such a project and needed to really look at what value I could add to the project without breaking their budget.   In instances like this you really do need to keep project management simple.

Now I do not advocate cutting corners or reducing your standards lightly, but we all know that sometimes there are situations in which we are placed where our options are limited.  After all, it is the real world and things don’t always flow nicely along according to the PMBOK manual!

Here are a few tips if you find you need to ‘keep it simple’:

Make sure the customer understands that they are not getting a full project management service
It is imperative that customer expectations are managed.  When people want to bargain with you about price and scope, something funny can sometimes happen later in the project – they think that they are still getting the same service for the reduced price!  If things go awry, as the ‘project manager’ they will still want to see you as responsible.  You need to ensure that if you decide to take on a role where your full standard of project management cannot be implemented then the customer knows and understands the risk associated.

Establish what exactly will be able to be delivered for the proposed budget
Be clear about what can and cannot be included in the project management service to be offered.  For example, discuss the number of hours you will be able to invest in the project and what they will get for that.  Discuss the expectations around meetings and reporting requirements as people often forget that these are necessary things that must occur and may leave those out of the budgetting process.

Institute simplified reporting systems
If you don’t have time or budget to implement your full reporting sytems – still institute something.  You know the old saying, if you can’t measure it you can’t manage it!  I implement a simple one page excel spreadsheet progress report.  It contains a few basics, including:

  • Summary Section – project % complete, project date due, expected delivery date
  • Deliverables Summary – list of deliverables, date due, expected date, % complete, status updates/comments
  • Issues/Risks Summary – list of issues/risks, including date identified, person responsible, impact, status, status updates/comments

This is really bare bones stuff, but when you’re keeping it simple – well….

Executive management loves this sort of report as it is simple and quick to read and hopefully it is quick and easy for you to prepare and ensures that you are keeping up to date of where things are at.

Maintain regular contact with the project and institute actions quickly
Projects like this, where you are being asked to reduce your normal standard of management really are at risk.  It is easy to lose touch or fail to keep up with what is happening in the project when you’ve been asked to do the ‘bare minimum’ – but it is imperative that you maintain a regular point and time of contact with the project to keep on top of it.  It is also imperative that you act when required – quickly.  Get on top of issues fast.

Document and communicate well with the key stakeholders
Even though your project documentation will be less than usual, do maintain it.  As previously stated, projects like this are often at risk of going awry and if they do, you want everyone to know at what point that occured and why.  I guess this is called ‘covering your own backside’.

Technorati Tags: , , , , ,

Managing Issues for Project Management Success

Issue Management starts when you are planning the project and lasts throughout the entire project lifecycle.

Even before a project starts there can be issues already in play.  You’ll need to identify issues in the planning stage and document them in an issues log.  Issues Logs can be as simple as a text document with a table in it or a simple spreadsheet or can utilize specific software systems designed for logging issues.  Issues log should be regularly monitored and updated throughout a project as part of your general project reporting and as issues come up.

The content of your issues log may vary, but generally there are some basic fields that most issues logs will contain.  These include:  Issue Reference, Name, Description, Severity, Impact.  Then issue updates may include fields such as a date, description, status and actions.  It really is imperative to keep a good issues log.  Just the act of having to update a log keeps you on top of where things are at and pushing along the actions required.  The other good aspect of having well documented issues is that when things hit the fan, and they sometimes do, then you have a detailed, documented trail of the actions you have been taking to rectify or resolve issues.

There are some issues that require documentation beyond the basic Issues Log.  This is where an issue requires further analysis and consideration of impact of possible actions – often where escalation is required.  Where this is the case I use an ‘Issue Report’ or ‘Issue Description’ which is a concise report that descibes the issue background, impact (time, cost, quality) and potential actions with their time, cost and quality impacts.

Keeping on top of issues that arise is imperative for project managment success.  It can stop little issues from becoming ‘showstoppers’, it keeps your project moving on the right path and it fosters confidence in you as a manager – from your stakeholders and your team.

Technorati Tags: , , , , , ,

Getting signoff

Getting sign off from a customer during a project can be a frustrating experience.  It can hold up the work on the project, pushing out your timeline and impede your project cashflow where payments are dependent on getting acceptance.  All of this is not good for project management success!

The issues that you may come across in getting a document or a deliverable signed off include:

  • Insufficient time allowed in the plan for review of the deliverable item
  • Insufficient support given to customers in the handover of a deliverable
  • Insufficient project management around this crucial period

I’ll talk about each of these briefly in this post.

Insufficient time allowed

It’s hard to stay in front when you didn’t have enough time allowed in the first place.  So consider the review periods that will be required, both internal to your organisation and at the customer end.  The more reviews and the more people involved in getting sign off, the greater the time period that needs to be allowed for.  It can be really tempting when planning a project to reduce these periods so try as hard as you can to resist calls from above to cut down the review times.

Insufficient support given to customer at the time of handover of the deliverable

Think about what you are handing over to the customer and ensure that you give clear instructions on what you need from them.  Be clear about what it is you expect them to do with the deliverable, be clear that you are expecting approval or proposed amendments (or whatever is relevant), be clear about the format you wish to receive feedback in and be clear about the timeframe you expect to have a response by.   Consider also that your customers may need help with their review of the deliverable and provide the necessary assistance.  For example at the handover of a piece of software for User Acceptance Testing you may need to provide a training session or demonstration, along with necessary testing plan and/or scripts and instructions on how and where to log issues with the software.

Insufficient project management

This is not the time to leave people to their own devices.  You should keep in regular contact with your customer and facilitate the approval of the deliverable by pushing them along in performing their actions as well as solving any issues that may impede them from undertaking their review or providing their approval.

Projects can really blow out around approval times, so to maximise your chances of project management success make sure you allow enough review and signoff time, provide support and manage the process.

Technorati Tags: , , , ,

Project Management Success – Quick Fire Strategies

Managing projects can be a difficult job and sure isn’t for the faint hearted!  All projects have challenges to overcome, in fact the complexity our projects, time and budget constraints in our high paced work environments mean that ‘putting out fires’ is an everyday part of managing projects.  But take heart, there are strategies that can help you to deal with challenges, issues, risks and problems and find Project Management success!

Here’s a few quick-fire strategies to get you moving straight away – strategies that take just a moment to employ, but can really make a difference in you everyday project world:

1.  Get Amongst It – Know your project inside and out, really understand what it’s about, talk to each member of your team and understand what they are doing, where they are at, what problems they are facing.  Really get amongst it.  Managing from afar just doesn’t work.

2.  Believe that you can – Ever heard that saying ‘whether you think you can or you think you can’t, you’re probably right’?  Well project management is a bit like that.  Often we are given projects where the resources, time, scope and budget just don’t point to success even at the get-go, however, we need to keep believing that we can do it.  We can deliver it.  We will find a way.  This belief not only focuses our mind on solving problems and taking actions but it sends a message to the whole team.

3.  Get on top of issues – No, they just don’t tend to go away by themselves, do they?  If you or another team member have identified an issue – solve it.  Nip it in the bud.  Solve it now, while it’s still small.  Come up with the options, communicate with the team and with the stakeholders.  Some issues are just carried all the way through the project like a grumbling under the surface until the project has to grind to a halt.  If you know something is going to cause a problem, get on top of it.

4.  Make deadline – all projects have key dates where deliverables are due to customers.  Isn’t it amazing what a flurry of activity can occur in the week or so when the next deliverable is due.  Funny what deadlines can do, isn’t it?  Having goals that are bound by a date really focus people’s time and energy, so set internal deadlines for the next piece of work with your team and get focused.

5.  Prioritize – Prioritize your time and energy into doing things that matter, things that are directly related to the completion of key project deliverables or the solving of project issues.  Sometimes we get so caught up in the small stuff that we lose sight of what’s important.  Project Management success, particularly where you have multiple projects to manage, is dependent upon your ability to determine what is important – and what isn’t.

6.  Communicate – talk to the team, talk to the customer, tell people what’s going on.  If there’s a problem, if there’s a success, whatever, just communicate.  Being visible as a leader and manager is important and ensures both your team and your stakeholders are confident that you are on top of things.

So there are a few strategies for you to employ, that can help you to achieve Project Managment Success.  Good luck!

Technorati Tags: , , , , , , , , , , ,