|
This Meeting
- Talked about what the team can do to improve our directory structure, such as README files for each existence project directories.
- Going through Project Plan - estimation of the project's progress have to be conservative.
- Anthony suggested a table of descriptions for tasks, to go with the Project Plan, e.g. ID -> Description. Here, Jo will be able to describe each tasks present in the Project Plan in more detailed -> evidence of team's progress on project.
- Clarified the differences between Review Meetings and Progress Meetings.
- Clarification of Design Notebook - really important to explain each decision made within the team for the Project, not just scribbles and sketches.
- The possibility of doing Java research with other team.
- Talked about minutes template.
- Clarification of Audit - the Auditors will try to find evidence of process as outlined in the team's SQAP.
- Decided that it will be good to have a task called "Other tasks", for detailed plans -> this can be described in more detailed in the table of descriptions for tasks.
- Talked about what a good project plan is - must point out all the possible and relevant tasks to the project -> what you think a marker should know.
- Jo to update and fix the Project Plan.
- Jo to talk to other team's PM (Project Manager) about the possibility of a joined research.
- Jo to report to team members about the meeting.
- Jo to start arranging formal meetings with Anthony.
- Jo to start taking minutes from meetings with Supervisor.
Next Meeting
Sometimes next week (to be advised). Jo will arrange.
|