Corleone Diaries 04/10/2009 Project Assessment

On the 30th September we the Corleone team (Wayne, Ashley and Michael) had our first stage (User Requirements) assessed at a project meeting. The assessment team consisted of Derek Peacock (Overall Head), John (Software Assurance Manager) Luke (Software Quality Assurance) and members of other teams as peer assessors. The assessment itself consisted on grading our deliverable requirement user tasks from poor through to very good. From the resulting assesssment, if there were too many deliverable failures the team would have to go through a second project assessmnet meeting, if however there were only minor or cosmetic changes needed, then it would be passed on the team showing that the said changes had been made. The result of our project meeting was that we had our project passed pending us putting several minor cosmetic faults right and resubmitting the project, this we did as a team and the following day we resubmitted our project and had it passed, we are now moving on to stage 2.

Looking back and reflecting on the Project Assessment Meeting, which I thought was really good, as it gave positive and constructive feedback in what I also felt would be the scenario in a proper games producing company. It also made me think on how we could cut down on the amount of minor and cosmetic errors we had made (could have been major) and I believe in future before a Project Assessment, we should as a team go through each task systematically with a critical but constructive eye, with the two non task persons quizzing and checking the person who has done a particular task and his work. This I believe would cut dramatically the amount of minor errors and pick up any major errors, all of which cost time and money in a real situation further down the line.