Note: This product is included as part of the 'Complete Project Management plus PRINCE2®'
where it is called 'Project management (non PRINCE2®)'.
It does not include coverage of PRINCE2 2005, PRINCE2 2009 or Directing Projects with PRINCE2.
It does contain copious cross references to PRINCE2 2005 and PRINCE2 2009.
|Complete Project ManagementThis product contains many items either not
specifically covered in PRINCE2 2005® and PRINCE2® 2009
or covers many items in more detail.
|Problem statementIt is important that the project team agree on the problem.
A poor definition of the problem will always cause ambiguity
and confusion and personnel will be unsure of the purpose of the project.
|Mission statementWho is aware of the Mission Statement?
The Mission Statement is a summary of what the project is trying to achieve.
However, if you ask many people involved in a project what is the Mission Statement most will not know.
|ScopeWhen most people consider a project they think about the cost (C), time factor (T) and quality (Q)
but the scope can be left out. It is important to consider the limitations of the project.
It is necessary to think about what is included but equally what isn’t for the project, and define limits for these.
|ObjectivesThe overall project has a single goal which is to produce the final product.
The project can then be broken down to ever smaller goals.
These smaller goals are often called objectives.
|DeliverablesDeliverables derive from the measurement of objectives.
Individuals will have personal objectives as will the project.
Milestones are natural breaks in the project where there is an opportunity to review the progress of the project.
|Exit criteriaExit criteria refers to ‘how can you tell that an element of the plan is complete?’
This is so that you can ‘exit’ that phase and move on to the next.
|Work breakdown structureThe work breakdown structure (wbs) should form part of the Project Notebook.
Should, because it will exist in terms of the project schedule. Strictly speaking the work breakdown structure is
merely a list of component events that require actions to achieve them.
|Types of planThis covers Initial plan, Reference plan, Base plan,
Contingency plan, Horizon plan and Action plan.
|PlanningPlanning concerns knowing what you want to achieve but as yet not knowing how to get there. It usually begins with devising various strategies, assessing them and then choosing one of the options to go with. At this point, you have, in effect, cut all ties with the other options. If you choose incorrectly it can be prove very costly.|
|MilestonesAll projects of any length will be broken down into stages often referred to as milestones.
There will be a progress review at each milestone.
Without this, control will be lacking and project success will be unlikely.
|Detailed PlanningIt covers, identifying tasks, estimating effort / duration,
identifying dependencies, constructing the dependency network, assigning responsibilities,
allocating resources, producing a Gantt chart and refining the plan
|Cash flowIt describes the classic S-curve showing cash flow throughout the lifecycle of a project.||Statistical process controlIn order to highlight some of the principles and advantages of using statistical techniques
we have included FED (factorial experiment design) and
SPC (statistical process control) for an introduction of this area.
|Project managerKey responsibilities are to plan, organise, co-ordinate, control and lead.
No project will succeed without adequate planning and organisation.
Co-ordination of activity will require excellent communication skills.
|Construction projectsThis area is designed to show some general aspects of project management within the construction industry.
You will find here some techniques that the small business or individual may find useful.
How you apply the techniques will also depend upon the size of the project.
|Problem solvingCovers simple techniques such as the process of assessing, planning, implementing, monitoring and acting.
The use of brain storming, Pareto analysis, cause and effect diagrams, process analysis, and the six word system.
|Writing reportsReport writing is a specialised section of the wider use of writing techniques.
This will include writing for essays and dissertations at various levels of education.
Project management will require them at some point.
|Manual methodsMuch project management is now carried out using computer software.
However, it is often useful to understand some manual techniques which underpin the former.
These sections try to give a brief indication of some manual methods.
|Resource levellingClearly resource needs cannot be eliminated just by having as much of it as you wish.
The procurement of the resource is one issue and the efficient use of that resource is another.
|Project management systemsAreas covered are Six Sigma, SCRUM, Earned Value Management,
Sensitivity Analysis and PMBOK.
|Quality function deploymentQuality Function Deployment is a process for customer driven product design.
It is a process that takes the input from a customer and converts
this into design requirements for a product or service.
|TRIZTRIZ, unlike techniques such as brainstorming (which is based on random idea generation), aims to create an algorithmic approach to the invention of new systems, and the refinement of old systems.|
PRINCE2® is a Registered Trade Mark of the Office of Government Commerce in the United Kingdom and other countries.
A simple yet detailed example in Word format tries to show how the major areas of project management may be used in practice.
Much of the information is cross referenced to a detailed glossary.
39 project management templates with full accompanying notes will help project managers save time.
The product contains nearly 150,000 words.
A glossary identifies approaching 400 project management definitions.
These range from generic terminology to those specific to PRINCE2 2005 and 2009 as well as other project management systems.
The product includes a PowerPoint presentation containing over 200 slides
with full accompanying notes and copious cross references.
In addition, the product includes templates and many supporting files in Excel and Word.
Each part covers key areas and much more, see additional details below.
The example uses the construction of a shed or outhouse to demonstrate the key areas of project management.
A content page provides direct access via links to each section for ease of access.
Within each section the user can link to definitions easily.
- 28 page Word document
- Easy document navigation
- Covers the key areas of project management
- Links to definitions in the glossary
- Comments on PRINCE2® where appropriate
They are designed to help the project manager save time.
Each template contains specific notes that explain aspects of the template and aid in their use.
It is easy to modify them for particular projects.
PRINCE2® comments are added where relevant for comparison purposes usually to indicate areas not covered by PRINCE2.
- 39 useful, time saving templates
- Each contains note to aid usage
- Easy to modify and tailor to a project
- Comments relating to PRINCE2 are added where necessary
The glossary brings together project management definitions from a variety of methodologies.
This includes definitions for PRINCE2 2005 and PRINCE2 2009. Where they differ for the same term they are both included.
Other systems include SCRUM, Six Sigma and many more terms.
Simple definitions are often expanded to provide additional information.
- Approaching 400 definitions with 18,000 words
- Some definitions have links to the project management detailed example
- Includes all terms covered by and specific to PRINCE2 2005 and PRINCE2 2009
- Definitions cover other systems and generic practices
- Product can be downloaded
- No prior skills are needed
- Saves a lot of time
- Easy to modify and train yourself and others
- Simple to understand
- You don't have to be a project manager
- 12 month money back guarantee
- Prices include VAT
- NO shipping charges