Regardless of why your project has ended, you still need to collect information about it. By methodically reviewing a completed project and identifying the performance of key areas, teams learn what to do--and what not to do--in the next project. Use theis template for your stakeholder review.
TOOLS TRAINING LIVE WEBINARS USER-GENERATED
|Deliverable Templates Project Plans Checklists Presentations|
|Language:||All English Arabic French Japanese Korean Portuguese Romanian Russian Spanish|
|Access:||All Free Premium|
|All A B C D E F G H I J K L M N O P Q R S T U V W X Y Z|
95 items found
Use this spreadsheet in conjunction with the The Stakeholder Tool story to help pinpoint the key relationships between project stakeholders--and the ones that need the most work.
By completing and referencing this template, you will gain an improved understanding of the project from the perspective of each stakeholder. You will find this template indispensable throughout the project for managing and getting the most out of your stakeholder relationships.
Here's a template you can use to standardize bug or error message reports.
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!
If your company doesn't already have a standard change control form, you'll need to come up with one of your own. Use ours as a model.
PMOs launched with broad mandates or fuzzy objectives often struggle to gain traction and quickly lose momentum. To earn support from the organization for the long haul, it is critical to get the PMO started on the right foot and show immediate and measurable value. This document captures questions you’ll need to consider in building a successful PMO.
What is our purpose in acquiring and using an application package and what compromises are permissible? Determine the key business drivers, must-haves and tradeoffs before you begin the acquisition and implementation process. This information is critical to making a business case for a packaged application business solution.
A Statement of Work (SOW) establishes a written contract of work to be performed. Use this review and approach material to whip your SOW into shape. There's no pork in this SOW, just stuff you can use!
UPDATED for 2020! Statistical PERT® (SPERT®) is a freely licensed, probabilistic, estimation technique. Use Statistical PERT to estimate uncertainties that have bell-shaped risk properties, like: task duration, work effort, revenue, expenses, agile story points, project portfolios, event attendance and more. Use in conjunction with the article Getting Beta with Statistical PERT.