Project
Assessment 1: Project Definition and Scope
|
Week 3 |
|
|
Group/individual: |
Individual |
|
Word count/Time provided: |
10% |
|
Weighting: |
1500 words |
|
Unit Learning Outcomes: |
ULO1, ULO2 |
Assessment 1 Detail
Assessment 1: Project Definition and Scope
The report defines the problem, describing the background and context, and detailing the scope of the project to be undertaken.
Assessment 1 Marking Criteria and Rubric
The assessment will be marked out of 10 and will be weighted 10% of the total unit mark. The marking criteria and rubric are shown on the following page.
Assessment 1 Marking Criteria and Rubric
|
Marking Criteria |
Not Satisfactory (0-49% of the criterion mark) |
Satisfactory (50-64% of the criterion mark) |
Good (65-74% of the criterion mark) |
Very Good (75-84% of the criterion mark) |
Excellent (85-100% of the criterion mark) |
|
Criterion -1 (1 mark) Does the business case is established for the project proposal, and the project scope described . |
Business case is not established for the project proposal, and the project scope is not described |
Business case is established for the project proposal, and the project scope generally described |
Business case is established for the project proposal, and the project scope described |
Business case is established for the project proposal, and the project scope clearly described |
Business case is established for the project proposal, and the project scope clearly and specifically described . |
|
Criterion-2 (1 mark) Does project charter identifies your goal and sets out the work commitments expected of you |
Project charter is not identifies your goal and sets out the work commitments expected of you |
Project charter is generally identifies your goal and sets out the work commitments expected of you |
Project charter is identifies your goal and sets out the work commitments expected of you |
Project charter is clearly identifies your goal and sets out the work commitments expected of you |
Project charter is clearly and specifically identifies your goal and sets out the work commitments expected of you |
|
Criterion-4 (8 marks) Does the Vision document demonstrate the ability of spelling out the core idea and the business case justifying the development effort. |
Business case is not addressed and captures the business value of the proposed system. All stakeholders is not identified. Business needs is not expressed. Functional and Non-functional requirements are related to business needs and identified.
|
Business case is addressed and vaguely captures the business value of the proposed system. Some stakeholders identified. Business needs generally expressed. Some Functional and Non-functional requirements are related to business needs and identified.
|
Business case is addressed and captures the business value of the proposed system. All stakeholders identified. Business needs expressed. Functional and Non-functional requirements are related to business needs and identified.
|
Business case is clearly addressed and captures the business value of the proposed system. All stakeholders clearly identified. Business needs clearly expressed. Functional and Non-functional requirements are related to business needs and clearly and specifically identified.
|
Business case is clearly and specifically addressed and captures the business value of the proposed system. All stakeholders clearly and specifically identified. Business needs clearly and specifically expressed. Functional and Non-functional requirements are related to business needs and clearly and specifically identified. |