Project Meeting 2 - Thursday 8th December 2011

Issues identified in previous meeting (including personal development goals)

Based on the issues that I identified at the end of the last meeting between myself and Vicky Rushin-Chape, I received the following pieces of feedback:

• The type of methodologies that can be used to assist with developing the project solution
• The approximate length of the project report
• Whether or not the code for all web-pages should be included in the appendices
• The date for when the next scheduled meeting will be held

Feedback received in previous meeting

Alongside the topics stated above, I also received some very important feedback relating to my Project Specification within this meeting. Vicky stated the specification I had submitted was suitable, and covered enough depth and detail to be “approved”. Approval means that I can now start creating the physical project solution, and I intend to start writing my report shortly.

I also received positive feedback relating to my first Project Diary entry – Vicky commented that the topics I discussed were suitable to make this diary entry sheet sufficient. There were a few changes that Vicky asked me to make, related to the spelling of her surname.

I intend to make the required changes to my Project Specification and Diary entry sheet over the Christmas break, and then re-upload the specification to the SCM Projects website.

This meeting was a relatively short gathering, however I did learn that during my next client meeting, all other students supervised by Vicky Rushin-Chape will be attending.

Issue	Feedback Received
Which type of methodology should be used, is the SWM method suitable, or is this too basic for a final year project?	Any type of methodology can be used, as long as it is appropriate, suitable for an I.T. based project, and is defined in the Project Specification.
What is the typical length of a web-related project report?	The length of the report doesn’t have a specific word limit, although it should be more than 4000 words. Based on previous report examples, approximately 14000-20000 words (including appendix sources) is feasible.
Should all code be included as appendixes at the end of the document, or only specific web-pages?	This question wasn’t identified – I will raise this question in the next meeting.
When will the next meeting be held?	The next meeting will be held on 5th January 2012.

Action taken on feedback

Based on the feedback I received, I will implement the following actions prior to my next meeting with the supervisor on Thursday 5^th January:

• Make the required changes to the Project Specification and Project Diary entry sheet. o Then re-upload the Project Specification to the SCM Projects website.
• Complete my second Project Diary entry sheet, and e-mail the document to my supervisor.
• Commence writing the Introduction section for the project report.
• Continue researching PHP, by reading Paul Hudson’s “Practical PHP” e-book.
• Complete feedback sessions with members of Thornaby Indoor Bowls Club to discover the features and topics they would like to see displayed within the proposed website.

Matters to discuss

In the next meeting between myself and Vicky Rushin-Chape, I intend to discuss the following matters:

• · Should all code be included as appendixes at the end of the document, or only specific web-pages?
• · Is it possible to change the methodology at this stage in the project?

References Consulted

No references were consulted throughout this meeting.