part 3 MIS
MIS 201
Information System Management
Note: Delete this page from final document
Note: Text in this style should be deleted from final document, as this text contains instructions for filling out the document
(Insert Organization Name Here)
(Insert Project Name Here)
A. General Information
Information to be provided in this section is general in nature and provides the necessary information about the organization of the project and project participants.
|
Project ID/Acronym: |
Date: | ||
|
Responsible Dept: |
Modification Date: |
|
|
|
Prepared by: |
Authorized by: |
Points of Contact
This should be the list of individuals that will be involved with the project during the Execution Phase.
|
Position |
Name |
Phone |
|
|
Project Manager |
|
|
|
|
Senior Management Sponsor |
|
|
|
|
Senior Technical Sponsor |
|
|
|
|
Procurement Contact |
|
|
|
|
Customers: |
|
|
|
|
Other Stakeholders: |
|
|
|
B. Executive Summary
Information in the project summary areas was started during the project concept phase and should be included here. Information includes the project name, original estimates, plan revision numbers, points of contact, etc.
Business Need/Problem - Identify business need/problem that needs to be solved.
Statement of Work - This statement should be short and to the point. It should not contain language or terminology that might not be understood.
Project Objectives - Provide a brief, concise list of what the project is to accomplish.
Project Approach - Describe the strategy to deliver the project. For example, it may describe a phased strategy, contracting approach, reference to implementation, etc. Subsections may be created to present the strategy.
C. Detailed Project Scope Statement
Describe in detail what will be the included as part of the overall project.
Project Results/Completion Criteria
Methodologies to be Used
Content of the Project: Deliverables
Exclusions
D. Resource Planning
After establishing the human resources required for the project, develop a staffing plan that shows the personnel (both internal and external) and their estimated effort hours that will be required on the project on a weekly basis. Note: this information can be generated via a PM tool such as MS Project as a byproduct of the project schedule.
|
Staffing Names |
Week1 |
Week2 |
Week3 |
Week4 |
Week5 |
Week6 |
Week7 |
Week8 |
Week9 |
|
|
|
|
|
|
|
|
|||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
E. Budget Planning
List the budget estimate, by task, that is estimated to complete this project. Include personnel, contractor, equipment, and other associated costs required to complete all project deliverables. Note: much of this information can be generated via a PM too such as MS Project as a byproduct of the project schedule. (Totals must be updated manually - Click Update Fields button on PMM Toolbar.)
F. Communication Planning
List the different project stakeholder categories (Project Sponsor, Information Officer, Customer, Team Member). Describe how they will receive project information (email, project status meetings, sponsor meetings, etc.) and give the frequency in which they will receive this information (daily, weekly, bi-weekly, etc.).
|
Target Audience |
Target Message / |
Method |
Frequency |
Duration |
|
|
Type |
Name |
Agenda |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
G. Quality Planning
Project / product quality is of paramount importance. This section should detail how quality is being addressed.
Deliverable Acceptance Criteria
Describe Acceptance Criteria for deliverables as they are turned over to the customer.
Applicable QA Activities
Define applicable Quality Assurance activities for the project including test and acceptance processes and documentation.
H. Risk Planning
Describe any potential risks that may impact the schedule, cost, or quality of the project or resulting projet deliverables. For high impact / high probability risks, detailed mitigation plans should be provided (as an attachment, if necessary).
|
# |
Risk Description |
Impact |
Prob |
Weight |
Owner |
Mitigation Plans |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
I. Signatures
The signatures of the people below relay an understanding in the purpose and content of this document by those signing it. By signing this document you agree to this as the formal Project Plan.
|
Name/Title |
Signature |
Date |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|