Documente Academic
Documente Profesional
Documente Cultură
Page 1
10/15/2013
PROFILE
PREPARED BY: DATE:
Page 2
Revised: 10/15/2013
MUST :
WANT :
RISK EVALUATION
MUST REQUIREMENTS
Please write all your MUST requirements in the first column. Score each requirement on a scale of 1 to 10. With 10 having the highest priority and 1 having the lowest priority. (1) Determine the level of importance for each requirement. (2) Then evaluate each score by the priority it has for your project. If you encounter two requirements which have equal importance and priority, then perform a risk evaluation. Ascertain the level of impact if this requirement was not met by the project and assign a risk evaluation score based on the same 1-10 scale.
MUST REQUIREMENTS 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. Page 4 Revised: 10/15/2013 PRIORITY SCORE RISK EVALUATION
Page 5
Revised: 10/15/2013
WANT REQUIREMENTS
Please write all your WANT requirements in the first column. Score each requirement on a scale of 1 to 10. With 10 having the highest priority and 1 having the lowest priority. (1) Determine the level of importance for each requirement. (2) Then evaluate each score by the priority it has for your project. If you encounter two requirements which have equal importance and priority, then perform a risk evaluation. Ascertain the level of impact if this requirement was not met by the project and assign a risk evaluation score based on the same 1-10 scale.
WANT REQUIREMENT 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. PRIORITY SCORE RISK EVALUATION
Page 6
Revised: 10/15/2013
PROJECT PLAN
PREPARED BY: DATE:
I.
A.
Objectives
System Objectives
B.
Infrastructure Objectives
II.
Project Scope
Page 7
Revised: 10/15/2013
B.
B.
Project Risks
Page 8
Revised: 10/15/2013
PROJECT PLAN
PROJECT PLAN: DATE:
VI.
A.
Budget
Estimated Resources
B.
C.
Page 9
Revised: 10/15/2013
D.
Facility Requirements
VII. Schedule
A. Phases of Work
B.
C.
Page 10
Revised: 10/15/2013
B.
C. OBJECTIVES
The project is to be completed no later than ____________. The budget is limited to no more than __________. The project will reduce expenditures by at least ______%. We expect that no more than _______ complaints will occur throughout the project from customers as we interrupt their day-to-day work.
D. BUSINESS CASE
Why is the project being done? This project is being completed in order to prevent ___________________. We expect that improved customer satisfaction will increase revenue to the company in the _____ year due to a decrease in ____________. We hope that the project will generate ideas on improving customer satisfaction while fixing this problem.
E.
PRODUCT DESCRIPTION/DELIVERABLES
What are the specific deliverables wanted and what will be the end result of the project? 1. A report that outlines what can be changed, how much each change will cost and the expected decrease in time it takes to ________ resulting from each change. The report will be presented to these departments: ____________, ______________, and _____________. 2. A list of interactions with our customers necessary to complete the changes. 3. A work breakdown structure, due within _____ weeks, that outlines the plan for accomplishing the project and a list of potential risks expected completing the project.
Page 11
Revised: 10/15/2013
PROJECT CHARTER
PREPARED BY: DATE:
Project Title:
A. PROJECT DESCRIPTION
B.
C.
PROJECT OBJECTIVES
D.
BUSINESS CASE
E.
PRODUCT DESCRIPTION/DELIVERABLES
F.
SENIOR MANAGEMENT:
Page 12
Revised: 10/15/2013
PROJECT PLAN
SCHEDULE
Description:
Project Schedule:
Activity Start Date Completion Date Status
Page 13
Revised: 10/15/2013
Page 14
Revised: 10/15/2013
Page 15
Revised: 10/15/2013
Test Case No
Test Conditions
Test Procedures
Expected Results
Page 16
Revised: 10/15/2013
Definition Section
I. Statement of Opportunity
II.
Scope of Requirements A. High Level Requirements B. Affected/Unaffected Products, Services, or Operations Solution Criteria A. Summary of Solution Criteria B. Detailed Evaluation Recommendation
III.
VI.
Page 17
Revised: 10/15/2013
II.
A.
Requirements Scope
High Level Requirements
Reqmt No.
Requirement Statement
[Statement must be clearly defined, complete, and verifiable]
Validation Method
[Description of what must occur to demonstrate that the requirement has been met]
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Page 18
Revised: 10/15/2013
B.
Affected/Unaffected Products, Services, Operations, and Organizations A/U * Description (If Affected (A)
Category Functions/Processes:
User Departments:
Subsystems:
Page 19
Revised: 10/15/2013
III.
Solution Criteria
Solution:
Description:
Advantages:
Disadvantages:
Page 20
Revised: 10/15/2013
VI.
Recommendation
[Describe in detail the preferred solution for meeting the customer's requirements including a preliminary estimate for cost, resources, and schedule.]
Page 21
Revised: 10/15/2013
Reviewer 2
Reviewer 3
Reviewer 4
Reviewer 5
Page 22
Revised: 10/15/2013
Comments/Recommendations
I.
II.
III.
IV.
V.
Page 23
Revised: 10/15/2013