It is amazing to me the difference between the way that project management is tought versus the way it is practiced. If you follow the PMBOK, the PM is expected to have quite a bit of influence. If you look at how project management is practiced, it seems that most PM's are just order takers. For instance, in Rita Mulcahy's PMP Exam Prep, she goes over what she has coined as PMI'isms. Some of the key ones are:
- PMI stresses the fact that a project manager must work within the existing systems and culture of the company. They call these enterprise environmental factors and they are imputs to many processes.
- Percent complete is an almost meaningless number. Project managers should not spend time collecting useless ingformation. It is better to control the project and know the status through other actions.
- A project manager has authority and power. She can say "No" and work to control the project to the benefit of the customer.
- If at all possible, all the work and all the stakeholders are identifieid before the project begins.
- The work breakdown structure (WBS) is the foundation of all project planning and should be used on every project.
- Many project managers do not properly plan their projects. Therefore, the work they do while the project work is ongoing is vastly different from what should be done.
- There is a basic assumption on the exam that you have company project management policies (son't laugh, we will get there) and that you will adapt them for use on your projects. These may include project management methodologies, risk procedures, and quality procedures. So, assume you have them when you take the exam.
Many of you may scoff at these suggestions. Here is the key.....Rita is absolutely right! She couldn't be more right! So then why is project management practiced in such a different manner? Most organizations just truly do not understand the profession. Our day is coming. Our day is on the horizon. The day where the project manager can say no, can push back, can be fearless in the delivery of messages.
Until that day comes, you must still try to follow the principles of project management. Why? Because they work! The days of dictating dates and budgets while demanding scope are coming to an end. Companies simply can't continue to operate with the blinders on.
Project managers, do not be afraid! It is ok to push back! It is ok to question the date! It is ok to provide options! I promise......one day you will be heard!
Keep pushing,
Rick
Friday, July 23, 2010
Monday, July 12, 2010
New Blog Listing
My log has just been listed at http://ppmcommunity.com/. Thanks team! Please visit this site as they have a tremendous amount of links to some great project management blogs!
Wednesday, June 16, 2010
Top Ten PM Desktop Clients
Here is a great review of the latest in software for project managers. It is missing some of the open source proejct tracking tools like Open Workbench (http://www.openworkbench.org/). Good hunting!
Wednesday, June 2, 2010
Creating Proper Metrics
There has been quite a bit of debate around the selection of metrics for project reporting. Most organizations simply look at the "On Time, On Budget" statement and feel that is an acceptable status. Then there are the organizations that try to invest in Earned Value which is a technique that is widely taught in project management circles. The appeal of Earned Value is the reporting of % complete and % of budget expended were not sufficient in telling executives where the project actually stood. Earned Value gives two metrics (Cost Performance Index and Schedule Performance Index) that is engineered to give a quicker and more efficient status to executives. The problem with Earned Value is that it is extremely complex to maintain and most project managers do not have adequate information (like estimated hours to complete and work completed versus hours expended) to create an accurate picture. This is where the stoplight report comes in. Most companies rely on the subjective guess and feelings of the project manager on where the project cost, budget, and quality stand. So what metrics should be reported? The list can vary based on industry and corporate culture, but the following list can help create some metrics to get you started:
• Cost and Schedule: These metrics are still important and understanding where the project stands from a budget and time perspective is still vital information. It just can't be the only information provided.
• Project Plan Quality: How many tasks show a past due start date or a past due finish date? When was the last time the project plan was updated? How many times have the dates slid or moved on the plan? These metrics will show how closely the project manager is managing the plan. Also, by publishing these metrics, it gives the project manager notice that the plan must be managed.
• Project Issues Raised: How many issues have been raised? Too many can be a sign of a project in trouble and too few can be a sign of the project not being managed appropriately.
• Project Issue Close Rate: How many have been closed by the due date? Do issues have a due date? Metrics like this one will make sure that the team is putting appropriate focus on the issues of the project.
• Risks Planned For: How many risks have been raised and planned for? Again, too many shows a risky project and too few shows one that has not been managed appropriately.
• Meeting Attendance: How many meetings have been called and how well attended were they? This helps understand the effectiveness of called meetings. If there are too many or they are not well attended, or too few, this could be a sign.
• Communication Plan Execution: How many communications did the project manager plan during the project and were they effectively communicated? For instance, if they said an issue log would be created and disseminated every Thursday, did they send one every Thursday? This will assist in ensuring that everyone is getting the information that they planned to receive for the project.
• Decisions Requested and Received: How many decisions or issues have been raised to the stakeholders and/or sponsors and how many have had appropriate decisions? This shows the attention that the key people affected by the project are paying. If a decision seems to drag or items requested are overdue, this can put the project at risk.
These are just a few items that can be tracked to paint a clearer picture of how the project is being managed and the level of trust you can put into the reports received. Utilizing a broader metric base will allow you to give a confidence level to the reports and allow you to focus on the proper problem areas. For instance, if a project does not seem to be moving, where does the blame lie? It is easy to simply blame the project manager. However, if the project manager is waiting on the CEO of the company to make decisions and the decisions have not been made, the project manager may be wary to raise a red flag. It is important to make sure that all information is level set so that the most complete picture can be painted for statuses. Then, you truly have the right information in front of you to make the proper adjustment.
• Cost and Schedule: These metrics are still important and understanding where the project stands from a budget and time perspective is still vital information. It just can't be the only information provided.
• Project Plan Quality: How many tasks show a past due start date or a past due finish date? When was the last time the project plan was updated? How many times have the dates slid or moved on the plan? These metrics will show how closely the project manager is managing the plan. Also, by publishing these metrics, it gives the project manager notice that the plan must be managed.
• Project Issues Raised: How many issues have been raised? Too many can be a sign of a project in trouble and too few can be a sign of the project not being managed appropriately.
• Project Issue Close Rate: How many have been closed by the due date? Do issues have a due date? Metrics like this one will make sure that the team is putting appropriate focus on the issues of the project.
• Risks Planned For: How many risks have been raised and planned for? Again, too many shows a risky project and too few shows one that has not been managed appropriately.
• Meeting Attendance: How many meetings have been called and how well attended were they? This helps understand the effectiveness of called meetings. If there are too many or they are not well attended, or too few, this could be a sign.
• Communication Plan Execution: How many communications did the project manager plan during the project and were they effectively communicated? For instance, if they said an issue log would be created and disseminated every Thursday, did they send one every Thursday? This will assist in ensuring that everyone is getting the information that they planned to receive for the project.
• Decisions Requested and Received: How many decisions or issues have been raised to the stakeholders and/or sponsors and how many have had appropriate decisions? This shows the attention that the key people affected by the project are paying. If a decision seems to drag or items requested are overdue, this can put the project at risk.
These are just a few items that can be tracked to paint a clearer picture of how the project is being managed and the level of trust you can put into the reports received. Utilizing a broader metric base will allow you to give a confidence level to the reports and allow you to focus on the proper problem areas. For instance, if a project does not seem to be moving, where does the blame lie? It is easy to simply blame the project manager. However, if the project manager is waiting on the CEO of the company to make decisions and the decisions have not been made, the project manager may be wary to raise a red flag. It is important to make sure that all information is level set so that the most complete picture can be painted for statuses. Then, you truly have the right information in front of you to make the proper adjustment.
Subscribe to:
Posts (Atom)