As each an energetic project supervisor and project management trainer, I usually get asked whether the project management finest practices which might be applicable for large projects could be utilized on smaller projects. It is a really vital query and one which all project managers must withstand when managing small projects.
Specializing in project delivery
One of many arguments against utilizing project management templates methodologies is that they’re very course of-centric resulting in vast quantities of project documentation which are simply not sensible or fascinating on small projects. This can be a highly effective argument and any technique which focuses on producing documentation at the expense of delivering the actual business advantages of the project might be a hindrance reasonably than a benefit. In spite of everything, the secret in project management is delivering enterprise aims, not producing reams of documents.
There’s an ongoing and energetic dialogue throughout the software program growth neighborhood about one of the simplest ways to supply software on projects. More just lately, some software program professionals have argued for more agile strategies of manufacturing software moderately than the extra conventional heavyweight methods which targeted on producing vast portions of documentation.
Agile methods give attention to delivery of software program moderately than documentation (project management templates). With this in mind, I think project managers everywhere can be taught something from the agile methods employed in software program development. In short, this leads us to focus on project delivery reasonably than project documentation, although the vital choice project managers in all places must make is how a lot documentation is basically essential?
Apply the perfect practices
I am a agency believer in only producing as much as is required by the project. Nothing more and nothing less. A simple rule of thumb is: if it is useful in serving to us to ship the enterprise targets of the project then produce it, if it is not useful in helping us to deliver the enterprise aims of the project then do not waste time to produce it. With this in thoughts, I believe that in all projects, at a minimum it’s best to use project management finest practices.
Let’s consider one of the best practices in turn and see whether or not the overhead lost in applying finest practices is value the benefits which may be gained.
Defining goals and scope
Even on the smallest project there will be goals which should be achieved. As a project manager, it is in your interest to outline what these aims are since you are more likely to be assessed on whether or not the project meets those objectives. It’s your accountability to ensure the project meets these aims and you are accountable for this. In brief, the guide stops with you.
Now suppose you do not define and write down what the aims are, you might be always going to be at the mercy of any boss who decides he’s obtained it in for you. The defined and documented set of targets is your insurance coverage coverage towards your supervisor later coming along and saying you did not meet the objectives.
Nonetheless, there is one more reason why you still must define and doc the targets even on a small project. You wish to satisfy the needs of the stakeholders since that’s what you are paid to do as a project manager. If the objectives aren’t defined, then you definately will not be capable of meet these wants by way of your project.
Equally with defining the scope. The scope varieties the boundary of your project. In the event you don’t outline what it’s, the likelihood is that it’s going to develop and develop as the project progresses and though you might need began managing a really small project, earlier than lengthy your project could become very much larger than once you set out.
You still have to doc who are the stakeholders on a small project as well. By defining who these are, you may be sure that you cover all of their needs once you outline the targets and deliverables.
Defining deliverables
Somebody goes to have to carry out the precise work to produce whatever is delivered from your project. Even when the deliverables might be
small and do not take a lot time to produce, they should nonetheless be written down. By documenting these items and then having them reviewed by others permits errors to be found. Your intention should be to doc a detailed sufficient set of descriptions of the merchandise to be delivered.
These descriptions will then be utilized by the individuals who will produce the deliverables. Even if these descriptions take not more than a page of text, you will need to write them in a transparent and unambiguous way. In case you don’t write down a description, it signifies that the particular person making the deliverable can interpret what is required in surprising methods which is able to only result in work being performed later to appropriate the mistakes. So, all the time define and doc the deliverables.
Project planning
Should you had been to walk up Mount Ben Nevis, you would by no means do it without a appreciable quantity of planning. Even should you walk up the hill behind your own home, there may be in all probability some planning involved – what time do you go? What should you take with you? It’s the same on even the smallest project the place you’ll still need to work out which actions are required to supply a deliverable, estimate how long the activities will take, work out what number of workers and resources are required and assign activities and tasks to staff.
All of this stuff must be written down and communicated effectively to the project staff members. I’ve seen numerous people turn out to be unstuck as a result of they suppose they need to use some type of project management planning software program comparable to Microsoft Project. This is an unnecessary overhead. I’ve observed that individuals are likely to waste an excessive amount of time making their Microsoft Project Gantt charts look pretty, in order that they lose sight of the explanation why they’re utilizing the tool.
Instead, for small projects I find that making a bar chart in Microsoft Excel is the best. It’s easy and more than sufficient for small projects. Simply make each column a sequential date, write your duties within the first column, and fill within the cells to characterize the time the activity takes.
In addition to the bar chart, you will have to doc the milestones on the project. Milestones are the dates by which you should deliver certain issues, or would be the date on which a serious activity ends. The obligations of each project member should even be documented in the project plan.
Communication
Even in the smallest project workforce comprised of just a project supervisor and one different individual, the project supervisor will nonetheless have to assign duties and tasks to the other person. It could’t be assumed that they will know what they need to do with out it being effectively communicated from the project manager. If the project manager doesn’t assign them particular actions, then the possibilities are they’ll go forward and work on issues which aren’t wanted by the project. So, either the project will find yourself delivering the fallacious things, or the project will get delayed since time will should be spent later on doing the activities which ought to have been accomplished earlier.
You may communicate the plans via electronic mail, or give a print out of the plan to your project crew member(s), or higher nonetheless, name a gathering and run by means of the plan with the project group members. Bear in mind, if the plan changes, you will also need to communicate the changes to your staff as well.
Tracking and reporting progress
If we still think about our two particular person project crew – the project manager and one different individual – the project supervisor might want to know the progress of the activities which the opposite particular person is working on. This can be done in a variety of methods: a short day by day e-mail detailing the work completed, the work nonetheless left to do, and a list of any issues/problems. Most often this will likely be sufficient.
Alternatively a short 15 minute face to face catch up can accomplish the same thing. Or a combination of the 2 things is likely to be best. In any event, the project manager still must be totally aware of the progress that’s being made in order that progress might be tracked effectively.
Change management
Even on our two particular person project, changes are prone to occur. Requests for change usually come from stakeholders and it is your responsibility as project manager to evaluate the impression of accepting these into the project. To do that, you need a superb estimate of the affect the change can have in terms of the additional effort and value involved. It will often affect the schedule as well, so by having a clear understanding of how the schedule and funds will likely be affected you may make the decision as as to if or not you’ll accept the change into your project.
On a small project there should not be any want for any fancy change control board to resolve if the change is accepted. A quick discussion with the important thing stakeholder(s) should be ample for you to come to a decision providing you will have worked out the influence on price and schedule.
One thing it’s best to never do is just settle for the change. Even in the event you assume the change is small, it’s best to never settle for any change(s) without fully understanding what its affect will likely be on cost and schedule. That is a recipe for what we call ‘scope creep’ where the project grows greater and bigger as increasingly more changes are added into the project. Before you already know it, your small project has turn out to be a a lot larger one and you will inevitably fail to ship your project to your authentic funds and schedule.
Threat management
There will probably be risks even on a small project. Make sure you have thought through all the potential dangers in the beginning of the project, monitor the top ten dangers each week (or high five if the variety of dangers is small) and preserve looking out for brand spanking new risks. Failing to manage threat correctly is one the primary causes for projects to fail.
The overhead in managing risks may be very low. On a recent project, I drew up an inventory of what I thought of to be all of the dangers on the project. It came to about 10 risks in all. Of those, five had been severe risks. I labored out a plan to avoid or minimise every risk. In all, it took me little over a few hours to do this. Then, each week on the project, I’d spend say half an hour reviewing all the dangers and thinking of any new ones. On the finish of the project, while some risks truly had materialised, as a result of I’d recognized a plan in the beginning of the project to minimise the affect of these risks, the influence of these risks on the project ended up being minimal.
So, with little up front and ongoing effort, you get a giant pay again when you manage the dangers throughout the project.
Summary
So, in abstract, applying the most effective practices to even a small project could be carried out without creating too much paperwork or overhead. The very best practices are the issues which numerous project managers have executed on thousands of projects and are deemed to be the ‘greatest practice’ as a result of they tend that can assist you to achieve the most effective results.
Do not think that since you’re managing a small project that you can ditch these best practices as a result of for those who do, you’ll regret it later when your project will get in a mess.
James Leal is a project director and consultant that has extensive experience within the business change in the UK and USA. Find out more @ Project Templates website www.ProjectTemplates.co.uk