Low Risk Project Form
Project managers can use this form once a project is evaluated as low risk, using the project level indicators, project scorecard, and in consultation with the projects sponsor. This allows rapid development and deployment of information technology solutions for low risk projects by requiring less documentation, oversight, and approvals than that required of more complex projects.
Download this form in (MSWord | pdf) format.
IT Project Low Risk Project Form |
---|
Project Title: __________________ Project Number: __________ Project Leader/Manager: _______ Anticipated Project Start Date: _______ Sponsor: _____________________ Date Prepared: _______ |
Initiation: |
Write a short vision for your project. Write a brief project justification. What problems are solved? Define the projects major goals. What are the projects key deliverables? Identify the core team members and major stakeholders. Describe potential enhancements to personal safety and data security for the university, as a result of doing this project. What are the projects resource requirements? Attach a breakdown of the projects preliminary budget.
Have the project team and stakeholders agreed on the above project initiation items? (Yes | No) |
Planning: |
Describe the projects functional requirements including a description of the projects scope. If special skills are needed to accomplish this project, what are they? What communication methods are going to be used and how will it flow? Identify the projects known risks, and how you plan to mitigate them? Identify information technology security needs.
Identify and arrange responsibility for production ownership, maintenance, and support. Explain and elaborate on potential enhancements to personal safety and data security. Enter or attach a simple work plan with work assignments, time line, and cost estimates. |
Approvals: (of project requirements and scope) Duplicate or delete signature blocks as needed. Requested by: (e.g., project manager)
Requested by: (e.g., project leader)
Approved by: (e.g., functional manager)
Approved by: (e.g., project sponsor)
|
Executing: |
What are your quality assurance procedures? Write a brief description of each status review. |
Monitoring & Controlling: |
Specify what parts of the execution are not corresponding to the work plan. What corrective action(s) are being taken to those processes not working according to the work plan? Are the corrective action(s) working? If no, explain and rework the last two steps. Is the current work plan adequate to complete the project? If no, explain then adjust and approve a revised work plan. Complete a final review of project security.
|
Closing: |
Are the users and stakeholders satisfied? If no, explain. List the project lessons learned.
Is there closure to the project? All loose ends complete? If no, explain. |
Acceptance: (Request for acknowledgement from the sponsor that the project is completed to the sponsors' satisfaction.) Duplicate or delete signature blocks as needed. Requested by: (e.g., project manager)
Requested by: (e.g., project leader)
Approved by: (e.g., customer)
Approved by: (e.g., project sponsor)
|
Download this form in (MSWord) format.