While many projects may not have to adopt the elements of the Federal Incident Command System, some are set up to resolve a certain time-bound resolution of organizational priorities and can reap the benefits.
It doesn’t seem to matter what methodologies are used--success is not a guarantee. While eyes always turn to the PM for blame, isn’t it time we examined why another significant party should also be sharing that burden?
While “blame” is not a constructive term to use in establishing where things went wrong, every element of a project should have clearly defined owners. If it isn’t clear where that ownership lies, there's a fundamental problem in the way your project is structured. Here we look at how we can establish that ownership--and ensure that the model is applied effectively.
Managing issues on a project takes strategic planning and a little finesse so that issues do not turn into show stoppers. Do you have an issue management plan that can handle any problems and still keep the project on track?
Since it’s the cold season, we wanted to share a list of maladies that will take your project down if you aren't paying attention or fail to keep your guard up. Each are preventable, and as the old saying goes: an ounce of prevention is worth a pound of cure.
Project failure is inevitable, and failing to deal with it is inexcusable. Many projects fail to deliver against the plan that the approval of the project was based on. But few projects are ever actually cancelled--projects are delayed, costs are escalated, scope is cut…but ultimately the project is delivered, even if it bears little resemblance to what was originally approved. Stop the insanity!
When one PM looks back at his project career, he knows it has had its share of missteps--hurdles both large and small that weren't so easy to clear. Here, he relates an early and misguided experience.
There are many ways a project can fail, but it's how the project manager handles the failing project that will make a big difference in how the failure impacts the people and organizations involved. Are you going to make this easy or hard?
Quality analysis and quality management can be a full-time occupation for an entire team of people on a project. Unfortunately, not all projects have the scope or resources available to hire a quality team to work on a project. This article explores some basic guidelines for using analysis to manage quality on a project.
With the steady industry shift away from custom code applications to more commercial software packages and services, IT project management practices are necessarily changing to adapt to the new conditions. Is this a glimpse into what the future holds?
No manager wants to demotivate their team, but sometimes their actions have unintended consequences. How can well-intentioned actions backfire?
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.