While there are many governance data points that can be gathered and analyzed to help make go/no-go decisions, there are three in this writer's experience that stand out as being the most important.
Closing Q&A webinar for March 2017 Book Club on How to Manage Complex Programs; High-Impact Techniques for Handling Project Workflow, Deliverables, and Teams by Tom Kendrick
Save Time With Tools + Templates
The scope statement is first defined in an early stage of the project, so that right from the start it’s clear what should be achieved and what not. Besides a clear description of what is included, the scope statement also contains a description of deliverables, exclusions, assumptions and constraints that might apply. All these aspects of the scope can be described in this simple document.
While numerous key performance indicators (KPIs) typically influence IT projects generally, the benefit of tracking all of them may be outweighed by the cost to do so. Therefore, each project must carefully select and manage those KPIs most relevant to its specific situation. This sample template can be used to define KPIs; also included is a table with examples of possible KPIs for each of the previously defined project-critical success factors (PCSFs) and a metric (measure and dimension) for each KPI. Use in conjunction with the article Determining IT Project Health.
This report helps you provide a concise and precise update on the current status of a clinical study and the achieved progress during the reporting period. It is usually distributed to a sponsor of the project, as well as the management of the company where the PM works. The main benefit of this report is that it addresses the major project constraints and provides only the relevant information needed to successfully manage the project and communicate with a diverse international team, typical for a matrix-based pharmaceutical company.
This single-page PDF flowchart depicts the process for facilitating communication about requested changes among the stakeholders of any project, providing a common process for resolving requested changes and reported problems, and reducing the uncertainty around the existence, state and outcome of a change that has been requested in a work product. Use it as a visual refresher or teaching tool.
This checklist is designed to help you ask and answer the tough questions about what defines your project and its mission. Before you start any work, take a quick look to make sure you haven't forgotten something important. (Hint: This document is excellent material for putting together your project plan!)
Learn From Others
Our bias toward comfortable processes hides the root cause of failure. One of the root causes on experienced teams? The misalignment of purpose and process. Here, the author provides an easy-to-implement, purpose-driven organizational methodology that helps eliminate this risk.
One of the major reasons for project failure is the occurrence of unforeseen events that disrupt the smooth running of the project and cause irrecoverable deviation from the plan. How can we help minimize the risk when it comes to scope definition in construction projects?
Your cost, schedule and resource estimates need to be realistic. But for this practitioner, that wasn't always the case in an effort to garner sponsor and customer approval. What would you do in this situation?
No matter where you work or what project you are assigned to, there is bound to be a funnel somewhere in the organizational hierarchy. How you work through and around that funnel may determine just how successful your project will be.
私たちは皆、一般にビジネス界の落とし穴を知っていて、避けなければならないことを理解していますが、最も明らかなトラップは、時には私たちが陥りやすいものです。特に、数多くの競合する優先事項を持つプロジェクトを管理し、 先行する道を離れてください。 この2部構成の記事シリーズは、プロジェクトが失敗する上位10の理由を特定し、共通のプロジェクト管理の落とし穴を回避する方法に焦点を当てています。
We generally talk about managing projects that were sold to our customers. But how about the management of a presales project? Is that just like managing any other project? Do we have the same constraints? Is it less stressful?
Some baseline calculations become much more intricate when dealing with large projects, especially when fielding new technologies. But at the end of the day, the premise is the same. Is our project within scope, on schedule and within budgeted costs?
Spending decisions in a PMO can foster or impede the organization. The process is volatile by the nature of its political implications. To allocate budget and resources in a smart way—and to achieve organizational goals—a measurable approach needs to take the following dimensions into consideration…
Do project managers really need to plan for project activities? Is it really worth the effort? What do we lose if we simply execute the project? When a PM practices agile and DevOps, do they still need to plan, or do these discourage it? Here, the author reinforces the power of planning.
Ask a Question