Main points for the marking guide are as follows
- Project Scope (10marks)
- what is to be done by the team and what is not to be done as part of the project
- A high level description of the problem to be addressed by this project. Of there is no real client, then provide an arguement justifying the project purpose (business case for a potential fictional client) (10 marks)
- Team contract
- Clearly state the time commitment expected of each team member (to total 150 hours each student over the semester). Clearly state the roles and responsibilities of each team member. Define roles for the team and allocations to each role. (10 marks)
- Project Plan (20 marks)
- Detailed work breakdown structure in Microsoft Project (or equivalent), identifying major milestones, allocating resources (people) to tasks, including regular meetings. This is expected to remain a 'live' document throughout the project.
- Team Communication Plan (10 marks)
- Where and when meetings are held, contact details for all members, processes for communication, processes for updates to electronic repository and other project tracking processes.
- Quality Assurance statement (5 marks)
- Describe the team processes that will be adopted for QA
- Risk Management Plan (5 marks)
- Identify who is responsible for identifying and monitoring the risk. Define the reporting process for risks
- Configuration Management Plan (5 marks)
- including methodologies and tools to be used. (e.g. tools adopted - configuration management, backups, email archives, web page management)
- Team Standards (5 marks)
- documentation and coding
- Overall Document Quality (20 marks)
- completeness, presentation, organisation and content, version control, table of contents, referencing, relevance to this particular project
No comments:
Post a Comment