Reference no: EM132549450 , Length: 2 pages

Mid-project Progress Review

Aim
The aim of the Mid-project Progress Review is to verify the current status of your project. It allows the academic panel to assess your progress, the quality of your project artefacts created to date, the learning gained up to this point and to identify gaps to be filled. It also allows you, and the academic team, to identify any issues in your project that need to be addressed to reduce the potential for failure. The status review and interview combined contributes 10% to your overall project grade.

Preparation for the review and participation in the review process provides another opportunity to assess six of your learning outcomes:
Demonstrate a professional attitude.
Communicate effectively with clients and sponsors.
Communicate effectively in both written and verbal presentations and in group situations.
Effectively manage, monitor and control the activities involved in a development project.
Determine an appropriate process and accompanying set of deliverables for their project.
Show the ability to document appropriately the deliverables for their project - software specifications, project plans, source code, technical reports, white papers, literature reviews, or academic articles for publication.

Timing
A Status Report is due in Week 13. Please email a copy to your mentor and moderator. Follow the instructions on Blackboard to submit a copy.

Preparation and Status Report
In preparation for the review your team must produce a status report and present your products and a current portfolio of evidence of the work you individually and collectively have completed to date and the processes you have followed.

The Status Report should assess and describe the current status of your project, where you are in your proposed timeline, identify your products, and highlight the issues. It should also present a summary of the work contributed by each team member, a breakdown of activities contributing to their total individual hours and the learning that each can evidence from the first half of the R&D Project. While the report as whole should be produced by the team the individual work committed and learning components should be contributed by each individual member.

The report should be written in a brief and formal style. Below provides a suggested structure for your report:
Title page with team name, date, version, team and supervisor names
An Executive Summary
A brief project description
An overview of project objectives, scope, approach, major milestones and deliverables
A response to how the proposal conditions or recommendations have been addressed
New variations from the original proposal with a rationale for them
Summary of current project status, including work completed and work yet to be done, and issues that exist in your project or team
Recommendations for improving the project team's performance
Summary of individual member contributions and learning achieved so far in the R&D Project
The Status Report should be submitted to your mentor and moderator in the manner identified on Blackboard by the specified due date.

Review Portfolio
Share the evidence of your portfolio in a digital form to your mentor and moderator.
The collated portfolio will have any products or documents produced to this point and should also be available for inspection.
Personal logbooks or diaries for each team member.
The marking team will look at your documentation for your progress and products. They will use the assessment criteria for the Final Portfolio assessment to structure their questions. The panel will expect to see a minimum of 110 hours of work evidence per student covering:
Research and Upskilling
(Architecture, tools, or platform reports, usability reports, investigations, and feasibility assessments)
Planning and Control
(Evidence of sound and effective planning and control processes, including minutes that detail rationale for project decisions.)
Communication and Teamwork
(Evidence of sound and effective communication and collaboration with team members, supervisor, client, stakeholders.)
Development and Quality Assurance
(Quality and completeness of all a) development activities and outputs; b) quality assurance activities and outcomes; and c) quality and completeness of final products) Keep work-in-progress version of your portfolio to demonstrate changes and updates.

Results of the Mid-project Progress Review

There are three most likely outcomes of this review:
Your project will be permitted to continue with or without conditions o This is the normal and anticipated situation
It may be recommended that individuals or your entire team be withdrawn from your project
This is undesirable, but may be the best solution if the project shows a general failure to
make headway, or circumstances surrounding the project warrant withdrawal
In this event team members may receive a DNC or D for Part 1 of their R&D Project.
It may be recommended that we confer with your client over the state of your project
In this situation there may be some problem with the client relationship, availability, or expectations from the team or university. Your supervisor should help lead these discussions.

Attachment:- Project-Progress-Review-Requirement.rar