| GIS Project Management Process |
|
| Templates & Examples List |
| Deliverable | Description | Phase | Examples |
| Action Items & Issues | Document used for tracking action items and issues through closure. | Analyze Project Control |
|
| Application Disaster Recovery Process (R) | Indicates what is required to recover an application from a catastrophic event. | Develop & Test Deploy |
|
|
Architectural Design (Examples Only) |
Pictorial representation of the application or system. | Analyze | |
| Assumptions & Constraints | Documents project assumptions and constraints. | Analyze Project Control |
|
| Business Case |
Spreadsheet used by project requestors, sponsors and GIS business development contacts to estimate the benefits associated with the project. This information is used to assist the GIS PST in project approval and prioritization decisions. | Project Initiation | |
| Business Rollout Plan |
Specific business activities required to prepare the business organization for the new or enhanced product or service. | Develop & Test | |
| Communication Plan | Document used to plan project communications including who needs what communication, when the communication needs to occur and who is responsible for the communication. | Analyze Project Control |
|
| Cost Plan (R) | Spreadsheet used to identify and document project costs. Requires formal approval by the sponsor & requestor at the end of the Design phase. | Analyze Design Project Control |
|
| Critical Computer Resource Log |
Used to document and track computer resource needs (e.g., installation of new hardware) whenever the resources are considered critical to the success of the project. | Analyze Project Control |
|
| Customer Satisfaction Survey (R) | Survey used to gather customer feedback on the completed project. | Post-Deploy | |
| Design, Cost Plan & Schedule Signoff (R) | Formal document signed by the sponsor and requestor indicating they accept the design and the schedule. | Design | |
| Escalation Guidelines | Guidelines for appropriate communication of project related issues. | Control | |
| Functional Test Checklist | Provides a list of items to consider when developing the functional test plan. | Design Develop & Test |
|
| Functional Test Plan | Includes test scenarios, who will perform the test, how the results will be tracked to closure, etc. | Design Develop & Test |
|
| Lessons Learned (R) | Used to record a brainstorming session with project team members and customers to identify, analyze and document what worked well and not so well during the project. | Post-Deploy | |
| Maintenance & Support Turnover Plan | Specific activities required to prepare for for the turnover of support from the project team to the maintenance & support teams. | Develop & Test Deploy |
|
|
Measurement Guidelines (R) | Document identifying project measurements (target, actual and variance). | Analyze Post-Deploy Project Control |
|
| Meeting Minutes | Records attendance, agenda, action items, decisions, and discussions from a meeting. | Analyze Design Develop & Test Deploy Post-Deploy Project Control |
|
| Percent Project Complete Definitions | Defines the GIS criteria for determining and reporting percent complete during the life of a project. | Project Control | |
| Performance Test Request | Document requesting performance test services from the test team. | Develop & Test | |
| PMP Checklist (R) | Used to indicate what required activities have been completed on a project. It is also used to indicate when a required element has been considered but found not necessary for a project. Also indicates what documents must be provided to the maintenance and support team and in which project folder each document should be filed. | Analyze Project Control |
|
| Program Summary Report | Used by program managers to report program status at the monthly GIS project reviews. | ||
| Project Acceptance Signoff (R) | Formal document signed by the sponsor and requestor indicating they accept the project's product. It also serves as official agreement that the project may be closed. | Post-Deploy | |
| Project Change Request (R) | Formal process for requesting changes to the project scope. Project changes include new requirements/deliverables as well as changes to the schedule. For example, the agreed upon deploy date has been set but some new business requirement arises and the date needs to be moved in sooner. | Project Control | |
| Spreadsheet used by project requestors, sponsors and GIS business development contacts to identify and document the project's score against the project selection critera. This information is used to assist the GIS PST in project approval and prioritization decisions. | Project Initiation | ||
| Document completed by a project requestor to begin the project initiation process. | Project Initiation | ||
| Project Solution Approach (Examples Only) |
Documents the high-level approach the project team will use to deliver the product. This includes development method (e.g. iterative, waterfall, etc.) and multiple phases/generations. In addition, it also includes identification of the tools to be used (such as a specific SAP module or a web page, etc.). | Analyze | |
| Requirements Checklist | Provides a list of items to consider when gathering requirements. | Analyze | |
| Requirements: Guidelines Excel Template Word Template |
Documents the detailed customer requirements which are then converted to technical specifications. It also documents the user acceptance criteria - how the team and stakeholders will know that a requirement was met. | Analyze | |
| Resource Requirements (R) | Documents resources required for a project (by skill set and eventually by name), how many hours they will be needed, and when they will be needed in the project life cycle. This is also used for capacity planning. | Analyze Project Control |
|
| Review Presentation | Provides a format to be used in project reviews (internal and external). | Analyze Design Deploy Project Control |
|
| Risk Mitigation Plan | Documents project risks, the likelihood the event will occur, the impact if the event does occur and plans for mitigating the risk. | Analyze Project Control |
|
| Schedule | Baseline project schedule which includes all required project activities (based on the GIS PMP). Every project will need to revise the schedule to include additional activities necessary to build the project's product. | Analyze Project Control |
|
| Scope Statement (R) | Includes the project justification, a description of the product, the project deliverables and the project objectives. | Analyze | |
| Weekly project report including status of key risks and issues, project control metrics, key milestones; changes to scope, budget, staffing and effort; highlights and lowlights. Also used to present project status at the monthly project review meetings. | Analyze Project Control |
||
| Technical Implementation Plan | Specific technical activities required to prepare for moving the product to the production environment. | Develop & Test Deploy |
Application Example |
| Test Approach | Document used for planning test approach, testers, test durations, use cases, etc. This includes all types of testing. | Analyze | |
| Training Plan | Document used for planning training. Includes the type of training, who needs to be trained, who will perform the training, when the training needs to occur, etc | Design | |
| Unit Test Plan | Specific document used to plan the unit test. Includes unit test scenarios, who will perform the test and how the results will be recorded and tracked through closure. | Develop & Test | |
| WORP Process | Document which contains information that assists the EDS Help Desk in routing Remedy tickets to the right queue. | Develop & Test Deploy |
Last Update: March 3, 2004
This site is owned by Susan McCarthy. Content on this site is current for one year from the last update.