Mid project progress review preparation - hamstar/Braincase GitHub Wiki

Todo List

  • Reflective Reports
  • Update Project Proposal
  • Project Progress Review Summary

Reflective Report

Each student needs to deliver a reflective report of 2 pages showing its individual progress at the end of the first semester. It should answer three simple questions:

  1. What have you done?
  2. What is different to your original plan and why?
  3. What did you learn and what do you plan?

Well, thats really five questions.

From the Project Guide

At a chosen point(s) in your project, normally at the mid way point, or at any other point at which your supervisor deems appropriate, you should conduct a project progress review, involving your whole team, your supervisor, and the project coordinator. Appendix J provides indicative timings for these reviews. Please work with your supervisor to ensure that this meeting is scheduled.

Prior to the review you should collect your deliverables from the project to date as evidence of your progress in a draft portfolio, together with your diary, any progress reports or other materials which could build towards your final portfolio evidencing your work. Refer appendix F for ideas of what you might include in an early edition of your portfolio, which you should be building cumulatively as you go. Ensure that you have supporting evidence of your individual work against each of the assessment criteria. The review will include an inspection of your draft portfolio and general feedback on its adequacy by your supervisor.

**To be well prepared for this review you would ideally prepare a written summary report a few pages long as follows: **

  • Produce a written summary of between two and five pages in length: which states the progress of your project, broadly covering the topics outlined in Appendix D2
  • Use Appendix D2 as a form of supporting checklist for your progress review meeting
  • Be prepared to answer questions related to these topics, and make sure the work-in-progress version of your portfolio contains material which might support your answers.

This written summary can help you reflect on your project, what you are doing well and what issues need to be addressed as the project develops. This written summary can be included in your final portfolio, and should help you in thinking about your final reflective report.

The forms for this review are provided in Appendices D, D1 and D2. There are three most likely outcomes of this review:

  • Your project will be permitted to continue with or without conditions
  • This is the normal and hoped for situation
  • It may be recommended that your project be cancelled
  • This is clearly undesirable, but may be the best solution if the project shows a general failure to make headway, or circumstances surrounding the project warrant its cancellation.
  • In this event team members may be reassigned to other projects, with the option of extending the duration of their studies, or may be required to accelerate their contribution to complete within the timeline of the other project team. These decisions will be made by the project coordinator in consultation with your supervisor.
  • However there can be no guaranteed outcome for students in this situation, and each case will need to be individually negotiated.
  • It may be recommended that you confer with your client over the state of your project
  • In this situation there may be some problem with the client relationship, availability, expectation from the team, etc. which the team will need to resolve with the client. Your supervisor should help lead these discussions.

Suggestions for inclusion in Project Review Summary

General Project Description

  • Overview of project objectives
  • Major milestones
  • Planned end products
  • How original proposal/learning agreement conditions or recommendations have been addressed
  • Variations from original proposal/learning agreement

Project Environment

  • Physical resources
  • Hardware
  • Software

Project Organization

  • Organization chart
  • Role descriptions
  • Key position understudies/backup plans

Client/user Organization

  • Organization chart
  • Interfaces
  • Reorganization plans (if any)
  • Information exchange procedures
  • Approval procedures

Project Control

  • Internal progress reporting
  • Estimating and planning
  • Checkpoints
  • Periodic reviews

Technical Approach

  • Scope (functions included and functions excluded)
  • Technology Platform (hardware & software)
  • Design Methodology
  • Standards & conventions

Project Plans

  • Work plan
  • Staffing plan
  • Change control/configuration management plan
  • Status reporting plan
  • Project review plan
  • Training plan
  • Documentation plan
  • Approval/sign-off plan
  • Quality Plan
  • Test plans
  • Installation plan

Status

  • Current project status

Problems

  • Unresolved since project approval or last review
  • Real or potential
  • Priority

Project Manager’s/Team Recommendations

  • Within project team capability
  • Requiring external support