How many of you have seen project reporting structures that strongly encourage you to present just the “nice looking” status to the CIO, subtracting any real project issues or concerns from the reporting? It's a problem on PM is very familiar with.
What tools do you need to manage a project, and how do you find them? You cannot plan for every eventuality, but by covering the bases, you can deal with most problems and expand your tool set along the way.
A Theoretical Approach to Traditional Project Metrics-Bridging the Gap Between Earned Value and Critical Path Project Managementby
Since work completed from tasks not on the critical path does not affect the completion date of a project, it is important to differentiate tasks that are “critical” from those that are not in order to better monitor and control them. The project performance metric, critical path task index (CPTI), offers a more holistic view in terms of schedule performance for tasks directly related to schedule completion.
There are some project managers who will set high expectations or low expectations strategically depending upon their stakeholders. In reporting project status, as in all things, the truth will serve you best.
What are the functions of a manager? What is his or her job? Here we look at the management processes one by one, and try to find out how the manager does the job--and what the job really is.
What happens when a project manager faces team attrition? This article covers three strategies that can be applied during project planning, executing and controlling within the project human resources management and project risk management knowledge areas.
Effective Use of Kanban for Monitoring and Controlling Low-Complexity Projects in a High-Volume Project Environmentby
Kanban is an effective tool for monitoring and controlling high-volume/low-complexity projects when the goal is to increase throughput, limit work in process (WIP), and measure flow in project environments. Implementation of this approach has the ability to reduce the project management team’s level of effort while optimizing resource utilization.
Dividing your project into smaller parts that are more controllable helps you move closer to your ultimate goal: successfully achieving your project deliverables and high user satisfaction. Follow these seven tips to gain more direct control over your project.
Budget overruns are typical for all industries, especially for those dealing with complex, non-repetitive projects. Control over projects is often lost because the most popular project control tools simplify the control issue to the extent that vital steering parameters are lost or missed. A probabilistic forecasting tool like the Range Forecasting Method (RFM) can help address uncertainty and reduce extra costs.
There will come a day when you will face an issue and not be able to resolve it on your own. What will you do to ensure the project is not compromised?
A project is only useful if it produces benefits to the organization or client. The project manager and project team should be prepared to track those benefits during the project lifecycle. Here we provide some things to keep in mind.
Document a business case to persuade upper management to fund your project. Keep it short and succinct enough that the busy executive management audience will read and digest it. It should directly convey the information they need to know with salient, hard-hitting, supporting evidence that addresses the bottom line. This is a basic instructional framework of the information you should include in your business case. Enhance it as you wish!
Finding sponsors to back your project is an art. Make a compelling case for the project to gain sponsor support when you are pitching your business case to executive management. Here is an example of a brief, direct project concept designed to lure sponsors into your camp.
This checklist is a quick and dirty way of weighing risk factors against project criteria to discover level of risk.
Formulating a business case and proposing your project to senior management for buy-in can be tricky. Don't dive right in and start writing. Begin with a solid checklist of guidelines to ensure a business case that's more than buzzword hype.
Mission-critical projects need to be well-justified, with clear goals that can be referenced throughout the life of the project. This business case template offers an excellent approach to goal-setting and a way to communicate those goals effectively.
This is a high-level example of a Project Charter for implementing a methodology, but the structure and approach will work for many projects. This example is heavy on risks and assumptions, light on budgeting, role descriptions and conflict resolution.
The project sponsor is your project's champion. This guideline will help you pick the right person for this important job.
The attached tool has been developed to assist you in generating some solid payback data to be used to evaluate the return potential of your proposed method. Not only will it help the gods of finance see the light, but will also help you to understand whether your project is a winner or loser before you ever put your signature on the purchase requisition.
This excellent project justification guide will provide sophisticated advice to maximize the impact of your business case, making it accurate, complete and persuasive. In addition, learn some handy tips, techniques and strategies to complement existing procedures, templates and spreadsheets that you already use.
Presenting a winning business case with the right amount of the right information for the right audience is the key to getting approval and funding for your project! Here is a presentation that will give you the fine points on how to do just that.
No project was ever completed on time and within budget. Identifying risks associated with a project and mitigating them is a crucial activity of project planning. Managers need to not only analyze project risks, but also must develop contingency plans to address those risks.
The project sponsor checklist describes ways for the project sponsor to provide commitment and project support in an effective, visible manner.
Building an application? This checklist outlines 52 potential risk areas in application development, defining low, medium and high risk levels for each. Classifying your project risk in each of these areas will not only guide you in forming mitigation strategies, but really help you focus your management attention during the course of the project.
What's the first step in looking at the risks you face in delivering your project? Before performing a full-blow assessment, you may want to ask yourself a few simple questions. This 10 minute, 27 question worksheet will help you quickly identify a number of risk factors common to many projects. It's a great first step in looking at the risks you may be facing at a macro level.
This template outlines a classic Project Charter with a focus on project definition and strategic ties. Risks and stakeholder needs are covered, but not in granular detail. It is appropriate for fairly low-risk projects where the goal is to get everyone on the same page up front.