noscito What do you see...? We see things differently! +44 (0) 870 351 5922  
Home
SOLUTIONS
Noscito User
Noscito Remote
White Paper
SERVICES
Creating a Security Culture
IT Change Management
Business Process Management
Effective Presentations
Effective Presentation Skills
Programme Management
Project Healthcheck
Project Management
Project Management Skills
Document Management
Systems Architecture
NOSCITO
About Noscito
Partners
CONTACT US
LOGIN
project management skills
This paper contains a number of checklists to help you manage your projects. Use them to document your successes and mistakes. Project management is an art, not a science. Develop your own style.
Project Management is a skill that most people assume involves attention to detail. This is true but, when managing a team, it is essential that the manager understands the dynamics of the team and considers each player’s drivers. Often bottlenecks will occur when communication breaks down between individuals.

Never draw up a plan without building in wasted time. Events will occur that will lose several days from your target. When these happen, deal with them aggressively to get back on track and review your plan.

Give your customers conservative estimates of delivery. It is better to impress than to disappoint. Don’t let your internal targets make you complacent. Set internal deadlines that will keep you focused.

This paper contains a number of checklists to help you manage your projects. Use them to document your successes and mistakes. Project management is an art, not a science. Develop your own style.

What is a project?
An indeterminate number of unknown activities conducted to variable standards by different people all of whom have their own objectives, perceptions and misapprehensions.

What are the characteristics of a project?
It has specific, measurable objectives.
It is a one-off undertaking, perhaps breaking new ground within the organisation.
It has a definite start and finish.
It is usually multi-disciplinary and complex
There are time, cost and quality targets that must be met.

How to write your plan
This is the stumbling block for most of us. This is a “living” roadmap and should be reviewed every week. Structure it using the following headings:

Goals. Describe your purpose and mission.
Objectives. What do you have to do to make your goals possible? Objectives are quantifiable, measurable targets.
Strategy. How will you make your project happen?
Assumptions. Describe them and the approach that you will take.
Plans. Describe actions and work packages.
Activities. This is the detailed description of tasks and responsibilities. Build a plan that outlines who does what, when. Where are your “hot spots” where you might experience a bottleneck? What are your risks? Assume that your “ideal world” plan will run over by at least 30%. Take this into account.

Project management checklist
How detailed should your plans be? Are the links between activities well-planned or is the logic fuzzy?
How often will progress be monitored and who needs the information? How will progress be measured and who will provide the information?
Are resources critical? Do you need to monitor as well as schedule resource usage?
Remember to track costs. How do they relate to other company needs?
What other requirements do you have? Examples include equipment and stock.
What type of reports is required? What and who are they for?
What graphical output will be required?
What other company systems will feed or be fed by the project management system?

The following supporting documents should be crafted to support the overall
project plan.


The baseline plan
This is your detailed project plan. This should be done before the project starts.

Statement of work
Project work is based on deliverables of which there are three types:

Ultimate deliverables which together make up the end product of the project.
Intermediate deliverables which are required to produce the end product such as a discussion database.
Support deliverables which are required to undertake the project successfully but are not part of the end product such as contract documents and plans.

Work plan
This is a detailed plan of work to be undertaken. It should include:

A project plan. This will help you understand potential bottlenecks and critical paths. This is your baseline but will not highlight any management issues. Don’t forget to include elapsed days for each task. Review this weekly.
Supporting information. What are your resources? Do your team members have any other commitments that might impact their ability to deliver on time and to budget with the desired quality? Consider equipment availability and other materials. Can your suppliers meet their targets?

Expenditure plan
Produce a detailed statement of costs, broken down over time.

Quality plan
Describe:

Working practices (standards and procedures) that should be followed.
Quality reviews to be undertaken and who will be responsible for them.

Pilot
Always pilot your project. Before you begin a pilot, solicit the support of your key stakeholders and influencers. If you miss this stage they are liable to halt your progress until they feel personal commitment and understanding of the benefit of what you are trying to do for the business. Your technical proficiency and understanding of what you are doing is not a guarantee of success.

Project Management is not easy. Remember always to work on a “no surprises” basis. If you are concerned that your project might slip then talk to your client and/or manager immediately and work together to resolve the problem. Often you might have to consider other options to ensure that you can deliver.
© Copyright 2005 Noscito Limited Terms of Use | Privacy