Project management, tools, process, plans and project planning tips.
Table of contents
3.2. The Project Team
3.5. Fishbone diagrams
3.9. Gantt charts
3.10. Gantt chart example
Here are rules, processes and tools for project planning and project management.
Large or complex projects in big organizations often require some sort of executive 'sponsorship' or leadership. This is commonly termed 'project sponsorship' (see the separate section about project sponsorship).
While project management skills are obviously important for overseeing projects, interestingly the methods and tools that project managers use can be helpful for everyone.
A 'task' does not necessarily have to be called a 'project' in order for these methods to be very useful in its planning and implementation. Even the smallest task can benefit from the use of a well-chosen technique or tool, especially in the planning stage.
Any task that requires some preparation to achieve a successful outcome, will probably be done better by using a few project management methods somewhere in the process. The following methods can help in the planning and managing of all sorts of tasks, especially complex activities.
Project management is chiefly associated with planning and managing change in an organization, but a project can also be something unrelated to business - even a domestic situation, such as moving house, or planning a wedding. Therefore, these methods and tools can be useful far more widely than people assume.
Project management techniques and project planning tools are useful for any tasks in which different outcomes are possible - where risks of problems and failures exist - and so require planning and assessing options, and organizing activities and resources to deliver a successful result.
Projects can be various shapes and sizes, from the small and straightforward to extremely large and highly complex.
In organizations and businesses, project management can be concerned with anything, particularly introducing or changing things, in any area or function, for example:
- people, staffing and management
- products and services
- materials, manufacturing and production
- IT and communications
- plant, vehicles, equipment
- storage, distribution, logistics
- buildings and premises
- finance, administration, acquisition and divestment
- sales, selling, marketing
- human resources development and training
- customer service and relations
- quality, health and safety,
- legal and professional
- technical, scientific, research and development
- new business development
- and anything else which needs planning and managing within organizations.
Successful management, for projects both large or small, tends to follow the process outlined below.
The same principles used selectively and appropriately, also apply to smaller tasks.
- Agree precise specification for the project - 'Terms of Reference'
- Plan the project - time, team, activities, resources, financials - using suitable project management tools.
- Communicate the project plan to your project team - and to any other interested people and groups.
- Agree and delegate project actions.
- Manage and motivate - inform, encourage, enable the project team.
- Check, measure, monitor, review project progress - adjust project plans and inform the project team and others.
- Complete project - review and report on project performance; give praise and thanks to the project team.
- Project follow-up - train, support, measure and report results and benefits.
Often called the project 'terms of reference', the project specification should be an accurate description of what the plan aims to achieve, and the criteria and flexibilities involved, its parameters, scope, range, outputs, sources, participants, budgets and timescales (beware - see note below about planning timescales).
Typically and prior to the project's formal establishment the scheme 'terms of reference' are produced or at least drafted at a fundamental level by a 'project sponsor', or 'executive in charge' (of the project). Often such an initial top-level general project description (a 'business case' basically) is required for the plan to be justified, approved, and funded at a corporate level, prior to the commencement of detailed project planning. The project manager, typically appointed by the 'project sponsor' or the 'executive in charge', may be involved to varying degrees in the drafting of the initial corporate project description or business case. It is not unusual for someone to first be unofficially appointed to the role, pending corporate approval of the project itself and the formal appointment of the project manager. The project sponsor is usually more senior than the project manager, although not necessarily the 'boss' or senior up-line manager to which they normally report. All substantial projects generally require a formal and senior 'project sponsor' or 'executive in charge', although minor plans forming part of a manager's conventional duties, and not requiring specific board or corporate approval, may not require a 'project sponsor' as such, in which case executive accountability for the project and the project manager belongs to the normal up-line reporting manager/executive.
Usually, the project manager must consult with others (especially the project sponsor) and then agree on the detailed project specification with superiors and/or relevant authorities. The specification may involve several drafts before it is agreed. A specification is essential in that it creates measurable accountability for anyone wishing at any time to assess how the project is going, or its success on completion. Project terms of reference also provide an essential discipline and framework to keep the enterprise on track, and concerned with the original agreed aims and parameters. A properly formulated and agreed project specification also protects the supervisor from being held to account for issues that are beyond their control or outside the original scope.
This is the stage to agree special conditions or exceptions with those in authority. Once you've published the terms of reference you have created a very firm set of expectations by which you will be judged. So if you have any concerns, or want to renegotiate, now's the time to do it.
The largest projects can require several weeks to produce terms of reference. Most normal business proposals however require a few days thinking and consulting to produce a suitable project specification. Establishing and agreeing on a project specification is an important process even if your task is simple one.
A template for a project specification:
- Describe purpose, aims and deliverables.
- State parameters (timescales, budgets, range, scope, territory, authority).
- State people involved and the way the team will work (frequency of meetings, decision-making process).
- Establish 'break-points' at which to review and check progress, and how progress and results will be measured.
Separately the acronym BOSCARDET provides a useful example structure for Terms of Reference headings/sections: Background, Objectives, Scope, Constraints, Assumptions, Reporting, Dependencies, Estimates, Timescales. This structure contains no specific heading for costs/budgets - these considerations can be included within 'Constraints' or 'Estimates'.
Since projects (and other activities requiring Terms of Reference) vary considerably there is no standard universal structure for a Terms of Reference document. The responsibility lies with the project manager or leader to ensure all relevant and necessary issues are included, and this local interpretation tends to imply TOR headings and document structure. Brainstorming can be a helpful process by which all relevant Terms of Reference criteria can be identified and structured.
Organizations may have standard TOR structures, such as the BOSCARDET example, which it is sensible to use where applicable, mindful of risks of omission or over-complication that can arise when following standard practice. See also Terms of Reference in the business dictionary section.
See also project sponsorship.
Plan the various stages and activities of the project. Where possible (and certainly where necessary) involve your team in the planning. A useful tip is to work backwards from the end aim, identifying all the things that need to be put in place and done, in reverse order. Additionally, from the bare beginnings of the project, use brainstorming (noting ideas and points at random - typically with a project team), to help gather points and issues and to explore innovations and ideas. Fishbone diagrams are also useful for brainstorming and identifying causal factors which might otherwise be forgotten. For complex proposals, or when you lack experience of the issues, involve others in the brainstorming process. Thereafter it's a question of putting the issues in the right order, and establishing relationships and links between each issue. Complex projects will have a number of activities running in parallel. Some parts of the plan will need other parts of the plan to be completed before they can begin or progress. Such 'interdependent' parts of a project need particularly careful consideration and planning. Sometimes they will require a feasibility stage before the completion of a detailed plan. Gantt Charts and Critical Path Analysis Flow Diagramsare two commonly used tools for detailed project management planning, enabling scheduling, costing and budgeting and other financials, and project management and reporting. See also project sponsorship to understand how project sponsorship may be integrated with the project manager's responsibilities for planning.
Most projects come in late - that's just the way it is - so don't plan a timescale that is over-ambitious. Ideally plan for some slippage. If you have been given an fixed deadline, plan to meet it earlier, and work back from that earlier date. Build some slippage or leeway into each phase of the project. Err on the side of caution where you can. Projects which slip back and are delivered late, or which run over budget or fail to meet other financial requirements often cause significant problems. Many planners are put under pressure to deliver projects sooner and more cost-effectively than is realistic. Ambition and aiming high are good attitudes, but planning without proper prudence and responsibility is daft. Investors and executives tend rarely to question an over-ambitious plan, but they will quickly make very ruthless decisions when any overly ambitious project starts to fail. Exercising a little realism at the outset of a venture regarding financials and timescales can save an enormous amount of trouble later.
Another important part of the planning stage is picking your team. Take great care, especially if you have team-members imposed on you by the brief. Selecting and gaining commitment from the best team members - whether directly employed, freelance, contractors, suppliers, consultants or other partners - is crucial to the quality of the project, and the ease with which you are able to manage it. Generally try to establish your team as soon as possible. Identifying or appointing one or two people even during the terms of reference stage is possible sometimes. Appointing the team early maximises their ownership and buy-in to the project, and maximises what they can contribute. But be very wary of appointing people before you are sure how good they are, and not until they have committed themselves with terms that are clearly understood and acceptable. Don't imagine that teams need to be full of paid, official project team members. Some of the most valuable team members are informal advisors, mentors, helpers, who want nothing other than to be involved and a few words of thanks. Project management on a tight budget can be a lonely business - get some help from good people you can trust, whatever the budget.
To plan and maintain large complex projects with various parallel and dependent activities you will need to put together a 'Critical Path Analysis' and a spreadsheet on MS Excel or equivalent. Critical Path Analysis will show you the order in which tasks must be performed, and the relative importance of tasks. Some tasks can appear small and insignificant when they might actually be hugely influential in enabling much bigger activities to proceed or give best results. A Gantt chart is a useful way of showing blocks of activities over time and at a given cost and for managing the project and its costs along the way.
Various software is available for this, much of which is useful, but before trying it you should understand and concentrate on developing the pure skills, which are described in this process. The best software in the world will not help you if you can't do the basic things.
See also project sponsorship for detailed explanation of how the sponsor may be involved with the main team.
Here are examples and explanations of four commonly used tools in project planning and management, namely: Brainstorming, Fishbone Diagrams, Critical Path Analysis Flow Diagrams, and Gantt Charts. Additionally and separately see business process modelling and quality management, which contain related tools and methods aside from the main project management models shown below.
The tools here each have their strengths and particular purposes, summarised as a basic guide in the matrix below.
|Importance of commonly used Project Management skills|
*** - main tool
** - optional/secondary tool
* - sometimes useful
|Project brainstorming and initial concepts, ideas, structures, aims, etc||***||**|
|Gathering and identifying all elements, especially causal and hidden factors||*||***||**|
|Scheduling and timescales||**||***|
|Identifying and sequencing parallel and interdependent activities and stages||*||***||*|
|Financials - costings, budgets, revenues, profits, variances, etc||*||*||**||***|
|Monitoring, forecasting, reporting||*||**||***|
|Troubleshooting, problem identification, diagnosis and solutions||**||***||**||*|
|'Snapshot' or 'map' overview - non-sequential, non-scheduled||**||***|
|Format for communications, presentations, updates, progress reports, etc||*||*||***|
Brainstorming is usually the first crucial creative stage of the project management and project planning process. See the brainstorming method in detail and explained separately, because it many other useful applications outside of project management.
Unlike most project management skills and methods, the first stages of the brainstorming process is ideally a free-thinking and random technique. Consequently, it can be overlooked or under-utilized because it not a natural approach for many people whose mains strengths are in systems and processes. Consequently, this stage of the planning process can benefit from being facilitated by a team member able to lead such a session, specifically to help very organised people to think randomly and creatively.
Fishbone diagrams are chiefly used in quality management fault-detection, and in business process improvement, especially in manufacturing and production, but the model is also very useful in project and task management generally.
Fishbone diagrams are useful for early planning, notably when gathering and organising factors, such as during brainstorming. They also are very good for identifying hidden factors which can be significant in enabling larger activities, resources areas, or parts of a process.
Fishbone diagrams are not good for scheduling or showing interdependent time-critical factors.
They are sometimes called 'cause and effect diagrams' and Ishikawa diagrams, after Kaoru Ishikawa (1915-89), a Japanese professor specialising in industrial quality management and engineering who devised the technique in the 1960s. His diagram became known as a fishbone diagram, obviously, because it looks like a fishbone.
A fishbone diagram has a central spine running left to right, around which is built a map of factors which contribute to the final result (or problem).
For each project the main categories of factors are identified and shown as the main 'bones' leading to the spine.
Into each category can be drawn 'primary' elements or factors (shown as P in the diagram), and into these can be drawn secondary elements or factors (shown as S). This is done for every category and can be extended to third or fourth level factors if necessary.
The diagram above is a very simple one. Typically fishbone diagrams have six or more main bones feeding into the spine. Other main category factors can include Environment, Management, Systems, Training, Legal, etc.
The categories used in a fishbone diagram should be whatever makes sense for the project. Various standard category sets exist for different industrial applications, however it is important that your chosen structure is right for your own situation, rather than taking a standard set of category headings and hoping that it fits.
At a simple level this diagram is a very effective planning model and tool - especially for 'mapping' an entire operation.
Where a fishbone diagram is used for project planning the 'Effect' is shown as an aim, outcome or result, not a problem.
The 'Problem' term is used in fault diagnosis and in quality management problem-solving. Some fishbone diagrams can become very complex indeed, which is common in specialised quality management areas, especially where systems are computerised.
This model, and the critical path analysis diagram are similar to the even more complex diagrams used on business process modelling within areas of business planning and business process improvement.
'Critical Path Analysis' sounds very complicated, but it's a very logical and effective method for planning and managing complex projects. A critical path analysis is normally shown as a flow diagram, whose format is linear (organised in a line), and specifically a time-line.
Critical Path Analysis is also called Critical Path Method - it's the same thing - and the terms are commonly abbreviated, to CPA and CPM.
A commonly used tool within Critical Path Analysis is PERT (Program/Programme/Project Evaluation and Review Technique) which is a specialised method for identifying related and interdependent activities and events, especially where a big venture may contain hundreds or thousands of connected elements. PERT is not normally relevant when the project is simple, but when it is of considerable size and complexity - particularly when timings and interdependency issues are crucial - they can benefit from the detailed analysis enabled by PERT methods. PERT analysis commonly feeds into Critical Path Analysis and to other broader management systems, such as those mentioned here.
Critical Path Analysis flow diagrams are very good for showing interdependent factors whose timings overlap or coincide. They also enable a plan to be scheduled according to a timescale. Critical Path Analysis flow diagrams also enable costings and budgeting, although not quite as easily as Gantt charts (below), and they also help planners to identify causal elements, although not quite so easily as fishbone diagrams (below).
This is how to create a Critical Path Analysis. As an example, the project is a simple one - making a fried breakfast.
First note down all the issues (resources and activities in a rough order), again for example:
Assemble crockery and utensils, assemble ingredients, prepare equipment, make toast, fry sausages and eggs, grill bacon and tomatoes, lay table, warm plates, serve.
Note that some of these activities must happen in parallel - and crucially they are interdependent. That is to say, if you tried to make a fried breakfast by doing one task at a time, and one after the other, things would go wrong. Certain tasks must be started before others, and certain tasks must be completed in order for others to begin. The plates need to be warming while other activities are going on. The toast needs to be toasting while the sausages are frying, and at the same time the bacon and sausages are under the grill. The eggs need to be fried last. A Critical Path Analysis is a diagrammatical representation of what needs doing and when. Timescales and costs can be applied to each activity and resource. Here's the Critical Path Analysis for making a fried breakfast:
This Critical Path Analysis example below shows just a few activities over a few minutes. Normal business projects would see the analysis extending several times wider than this example, and the time line would be based on weeks or months. It is possible to use MS Excel or a similar spreadsheet to create a Critical Path Analysis, which allows financial totals and time totals to be planned and tracked. Various specialised project management software enable the same thing. Beware however of spending weeks on the intricacies of computer modelling, when in the early stages especially, a carefully hand drawn diagram - which requires no computer training at all - can put 90% of the thinking and structure in place. (See the details about the most incredible planning and communications tool ever invented, and available for just a tiny fraction of the price of all the alternatives.)
Gantt Charts (commonly wrongly called gant charts) are extremely useful project management tools. The Gantt Chart is named after US engineer and consultant Henry Gantt (1861-1919) who devised the technique in the 1910s.
Gantt charts are excellent models for scheduling and for budgeting, and for reporting and presenting and communicating project plans and progress easily and quickly, but as a rule Gantt Charts are not as good as a Critical Path Analysis Flow Diagram for identifying and showing interdependent factors, or for 'mapping' a plan from and/or into all of its detailed causal or contributing elements.
You can construct a Gantt Chart using MSExcel or a similar spreadsheet. Every activity has a separate line. Create a timeline for the duration of the project (the breakfast example shows minutes, but normally you would use weeks, or for very big long-term projects, months). You can colour code the time blocks to denote the type of activity (for example, intense, watching briefly, directly managed, delegated and left-to-run, etc.) You can schedule review and insert breakpoints. At the end of each line you can show as many cost columns for the activities as you need. The breakfast example shows just the capital cost of the consumable items and a revenue cost for labour and fuel. A Gantt chart like this can be used to keep track of progress for each activity and how the costs are running. You can move the time blocks around to report on actuals versus planned, and to re-schedule, and to create new plan updates. Costs columns can show plan and actuals and variances, and calculate whatever totals, averages, ratios, etc., that you need. Gantt Charts are probably the most flexible and useful of all project management tools, but remember they do not very easily or obviously show the importance and inter-dependence of related parallel activities, and they won't obviously show the necessity to complete one task before another can begin, as a Critical Path Analysis will do, so you may need both tools, especially at the planning stage, and almost certainly for large complex projects.
Project planning tools naturally become used also for subsequent project reporting, presentations, etc., and you will make life easier for everyone if you use formats that people recognize and find familiar.
A wide range of computerised systems/software now exists for project management and planning, and new methods continue to be developed. It is an area of high innovation, with lots of scope for improvement and development. I welcome suggestions of particularly good systems, especially if inexpensive or free. Many organizations develop or specify particular computerised tools, so it's a good idea to seek local relevant advice and examples of best practice before deciding the best computerised project management system(s) for your own situation.
I am grateful to I Kerr who wrote (Oct 2013): "...I teach a module on Project management as part of a volunteer programme and have found the free tool GanttProject to be very effective and user friendly..."
Indeed GanttProject seems to be excellent free software. I've not tested it fully so would appreciate further reports about it.
For projects involving more than petty cash you'll probably need a spreadsheet to plan and report planned and actual expenditure. Use MSExcel or similar. Financial accounting for small projects can sometimes be managed using the project's Gantt Chart. Large projects are likely to require some sort of dedicated accounting system, although conceivably Gantt Charts and financial management accounts can easily be administered within a spreadsheet system given sufficient expertise. If you don't know how to put together a basic financial plan, get some help from someone who does, and make sure you bring a good friendly, flexible financial person into your team - it's a key function of project management, and if you can't manage the financial processes your self you need to be able to rely completely on whoever does it for you. The spreadsheet must enable you to plan, administer and report the detailed finances of your project. Create a cost line for main expenditure activity, and break this down into individual elements. Create a system for allocating incoming invoices to the correct activities (your bought-ledger people won't know unless you tell them), and showing when the costs hit the project account. Establish clear payment terms with all suppliers and stick to them. Projects develop problems when team members get dissatisfied; rest assured, non- or late-payment is a primary cause of dissatisfaction.
Remember to set some budget aside for 'contingencies' - you will almost certainly need it.
See also project sponsorship, for details of how that role may be involved with aspects of project planning and reporting.
Planning for and anticipating the unforeseen, or the possibility that things may not go as expected, is called 'contingency planning'. Contingency planning is vital in any task when results and outcomes cannot be absolutely guaranteed. Often a contingency budget needs to be planned as there are usually costs associated. Contingency planning is about preparing fall-back actions, and making sure that leeway for time, activity and resource exists to rectify or replace first-choice plans. A simple contingency plan for the fried breakfast would be to plan for the possibility of breaking the yolk of an egg, in which case spare resource (eggs) should be budgeted for and available if needed. Another might be to prepare some hash-browns and mushrooms in the event that any of the diners are vegetarian. It may be difficult to anticipate precisely what contingency to plan for in complex long-term projects, in which case simply a contingency budget is provided, to be allocated later when and if required.
This serves two purposes: it informs people what's happening, and it obtains essential support, agreement and commitment. If your project is complex and involves a team, then you should involve the team in the planning process to maximise buy-in, ownership, and thereby accountability. Your project will also benefit from input and consultation from relevant people at an early stage.
Also consider how best to communicate the aims and approach of your project to others in your organization and wider network.
Your project 'team' can extend more widely than you might first imagine. Consider all the possible 'stakeholders' - those who have an interest in your project and the areas it touches and needs to attract support or tolerance.
Involvement and communication are vital for cooperation and support. Failing to communicate to people (who might have no great input, but whose cooperation is crucial) is a common reason for arousing suspicion and objections, defensiveness or resistance.
See also project sponsorship, for details of how that role may be involved communicating to the wider environment and stakeholders.
Your plan will have identified those responsible for each activity. Activities need to be very clearly described, including all relevant parameters, timescales, costs, and deliverables. Use the SMART acronym to help you delegate tasks properly. See the delegation tips and processes. Using proper delegation methods is vital for successful project management involving teams. When delegated tasks fail this is typically because they have not been explained clearly, agreed with the other person, or supported and checked while in progress. So publish the full plan to all in the team, and consider carefully how to delegate medium-to-long-term tasks in light of team members' forward-planning capabilities. Long-term complex projects need to be planned in more detail, and great care must be taken in delegating and supporting them. Only delegate tasks which pass the SMART test. Other useful materials to help understand team delegation are the Tannenbaum and Schmidt Continuum, and Tuckman's group forming/performing model. The Johari Window model is also an excellent review framework for quickly checking or reminding about mutual awareness among team members in large complex projects, where there is often a risk of project fragmentation and people 'doing their own thing' in blissful isolation - which seriously undermines even the best planned projects.
Manage the team and activities in meetings, communicating, supporting, and helping with decisions (but not making them for people who can make them for themselves). 'Praise loudly; blame softly.' (a wonderful maxim attributed to Catherine the Great). One of the big challenges for a project manager is deciding how much freedom to give for each delegated activity. Tight parameters and lots of checking are necessary for inexperienced people who like clear instructions, but this approach is the kiss of death to experienced, entrepreneurial and creative people. They need a wider brief, more freedom, and less checking. Manage these people by the results they get - not how they get them. Look out for differences in personality and working styles in your team. Misunderstanding personal styles can get in the way of team cooperation. Your role here is to enable and translate. Face to face meetings, when you can bring team members together, are generally the best way to avoid issues and relationships becoming personalised and emotional. Communicate progress and successes regularly to everyone. Give the people in your team the plaudits, particularly when someone high up expresses satisfaction - never, never accept plaudits yourself. Conversely - you must take the blame for anything that goes wrong - never 'dump' (your problems or stresses) on anyone in your team. As project manager any problem is always ultimately down to you anyway. Use empathy and conflict handling techniques, and look out for signs of stress and manage it accordingly. A happy positive team with a basic plan will outperform a miserable team with a brilliant plan, every time.
6 - Check, measure, and review project performance; adjust project plans; inform project team and others
Check the progress of activities against the plan. Review performance regularly and at the stipulated review points, and confirm the validity and relevance of the remainder of the plan. Adjust the plan if necessary in light of performance, changing circumstances, and new information, but remain on track and within the original terms of reference. Be sure to use transparent, pre-agreed measurements when judging performance. (Which shows how essential it is to have these measures in place and clearly agreed before the task begins.) Identify, agree and delegate new actions as appropriate. Inform team members and those in authority about developments, clearly, concisely and in writing. Plan team review meetings. Stick to the monitoring systems you established. Probe the apparent situations to get at the real facts and figures. Analyse causes and learn from mistakes. Identify reliable advisors and experts in the team and use them. Keep talking to people, and make yourself available to all.
See also project sponsorship, to appreciate the higher-level responsibilities for monitoring and reporting of a project's progress, status, implications, etc.
At the end of your successful project hold a review with the team. Ensure you understand what happened and why. Reflect on any failures and mistakes positively, objectively, and without allocating personal blame. Reflect on successes gratefully and realistically. Write a review report, and make observations and recommendations about follow up issues and priorities - there will be plenty.
Where a project sponsor is involved it is reasonable for this role to be responsible for top-level reporting/review, and where applicable recognizing and rewarding the successful project manager and team too.
Traditionally this stage would be considered part of the project completion, but increasingly an emphasised additional stage of project follow-up is appropriate.
This is particularly so in very political environments, and/or where projects benefits have relatively low visibility and meaning to stakeholders (staff, customers, investors, etc), especially if the project also has very high costs, as ICT projects tend to do.
ICT (information and communications technology) projects often are like this - low visibility of benefits but very high costs, and also very high stress and risk levels too.
Project management almost always involves change management too, within which it's very important to consider the effects of the project on people who have to adapt to the change. There is often a training or education need. There will almost certainly be an explanation need, in which for example methods like team briefing have prove very useful.
Whatever, when you are focused on project management it is easy to forget or ignore that many people are affected in some way by the results of the project. Change is difficult, even when it is good and for right reasons. Remembering this during and at the end of your project will help you achieve a project that is well received, as well as successful purely in project management terms.
And again, see the relevance and typical responsibilities of project sponsorship within the overall successful conception, management and delivery of a project.
Someone once said "Don't you love it when a plan comes together?"
As project manager, to be at the end of a project and to report that the project plan has been fully met, on time and on budget, is a significant achievement, whatever the project size and complexity. The mix of skills required are such that good project managers can manage anything.
To the optimist, the glass is half full. To the pessimist, the glass is half empty. To the project manager, the glass is twice as big as it needs to be.
A clergyman, a doctor and a project manager were playing golf together one day and were waiting for a particularly slow group ahead. The project manager exclaimed, "What's with these people? We've been waiting over half and hour! It's a complete disgrace." The doctor agreed, "They're hopeless, I've never seen such a rabble on a golf course." The clergyman spotted the approaching greenkeeper and asked him what was going on, "What's happening with that group ahead of us? They're surely too slow and useless to be playing, aren't they?" The greenkeeper replied, "Oh, yes, that's a group of blind fire-fighters. They lost their sight saving our clubhouse from a fire last year, so we always let them play for free anytime." The three golfers fell silent for a moment. The clergyman said, "Oh dear, that's so sad. I shall say some special prayers for them tonight." The doctor added, rather meekly, "That's a good thought. I'll get in touch with an ophthalmic surgeon friend of mine to see if there's anything that can be done for them." After pondering the situation for a few seconds, the project manager turned to the greenkeeper and asked, "Why can't they play at night?"
And this (thanks G Bee)... A project manager was out walking in the countryside one day when a frog called out to him. He bent down, picked up the frog and put it in his pocket. The frog called out again, saying, "If you kiss me I shall turn me back into a beautiful princess, and I'll stay with you for a week as your mistress." The project manager took the frog out of his pocket, smiled at it, and put it back into his pocket. The frog called out once more, "If you kiss me and turn me back into a princess, I'll stay with you for as long as you wish and do absolutely anything that you want. Again the Project manager took the frog out of his pocket, smiled at it and put it back. Finally, the frog demanded, "What's the matter? You can turn me back into a beautiful princess, and I'll stay with you for ever and do anything you want. Why won't you kiss me?" to which the project manager replied, "Understand, I'm a project manager. I simply don't have time for a girlfriend, but a talking frog .... that's cool."
- ETHICAL MANAGEMENT AND LEADERSHIP
- PEOPLE PERFORMANCE POTENTIAL MODEL
- PROJECT SPONSORSHIP
- THE PSYCHOLOGICAL CONTRACT
- QUALITY MANAGEMENT, HISTORY, GURUS, TQM, PROCESS IMPROVEMENT, ETC
- SIX SIGMA - DEFINITIONS, HISTORY, OVERVIEW
- TIME MANAGEMENT TIPS
- TREE SWING CARTOON PICTURES (EARLY VERSIONS)
- STRESS AND STRESS MANAGEMENT
- DECISION-MAKING AND PROBLEM-SOLVING
- DELEGATION - HOW TO