Meeting Minutes

Marine Observation Database
Team 4
Meeting Minutes

Author(s): Andrew Paton
Reviewed By: Andrew Paton, Chuong Lam

Table of Contents
1. Meeting 1, 12th August 2008. 3
1.1 Meeting Opened – 9.45AM... 3
1.2 Progress Report.. 3
1.3 General Business. 3
1.4 Actions to be Taken.. 3
1.5 Next Meeting – Wednesday 13th August, 2:30PM... 3
1.6 Meeting Adjourned – 10.30AM... 3

2. Meeting 2, 13th August 2008. 4
2.1 Meeting Opened – 2.30PM... 4
2.2 Progress Report.. 4
2.3 General Business. 4
2.4 Actions to be Taken.. 4
2.5 Next Meeting – Monday 18th August, 1.00PM... 4
2.6 Meeting Adjourned – 4.00PM... 4

3. Meeting 3, 18th August 2008. 5
3.1 Meeting Opened – 1.00PM... 5
3.2 Progress Report.. 5
3.3 General Business. 5
3.4 Actions to be Taken.. 5
3.5 Next Meeting – Tuesday 19th August, 3.30PM... 5
3.6 Meeting Adjourned – 2.30PM... 5

1. Meeting 1, 12th August 2008

1.1 Meeting Opened – 9.45AM
The meeting was initiated as part of the Software Team Project unit tutorial.
All team members are in attendance – Kevin, Andrew, Chinh, Chuong, Hai, Vivi.
It has been decided that this will be a regular weekly occurrence for the duration of the project.

1.2 Progress Report
· All material under Blackboard links for the project has been reviewed.
· It was our first meeting in which we introduced ourselves.
· Decided the times in which our team will meet up each week.
· Gather members and client details.
· Informed our team members in what we need to do for our next meeting.

1.3 General Business
· Member's self-introductions, strengths and weaknesses
· Set up multiple communication channels
· distribute tasks to members

1.4 Actions to be Taken
· Prepare your own member skill assessment document, like how you do in your CVs.
· Research, get familiar with software management plans, software development models and work break down structure.
· Contact convenor and our client, which I already did. The convenor has replied and said we should contact our client ASAP. The client suggested to meet at a time which I couldn't make it. I have drafted an email and is going to suggest some other time slots.

1.5 Next Meeting – Wednesday 13th August, 2:30PM
Gather information including:
- Client detail
- Member detail
- Subject convenor detail
- Brief requirement from client
- All legal related documents
- Setup up communication channels including:
- cell phone
- email
- MSN
- Online tool (Blogger)
- Prepare software management plan
- Prepare member skill assessment document
- Analysing and choosing software development model
- Build work breakdown structure for project management
- Build brief work breakdown structure for software development
- Build detailed WBS for software development and follow that structure.

1.6 Meeting Adjourned – 10.30AM

2. Meeting 2, 13th August 2008

2.1 Meeting Opened – 2.30PM
The meeting was initiated as our weekly meeting which we will have every week.
The team members in attendance were Kevin, Andrew, Chuong, Hai, Vivi, Chinh was unable to attend the meeting.

2.2 Progress Report
· Member's self-introductions, discuss strengths and weaknesses
· Set up multiple communication channels
· Distribute tasks to members

2.3 General Business
· Hold meetings often (Mon 13.00, Tue 15.30 we meet Anthony, Wed 14.30 we meet at the tutorial)
· Give warnings to those who don't contribute

2.4 Actions to be Taken
· Prepare your own part of the member skill assessment document, like how you do in your CVs, and post it up here.
· Research, get familiar with software management plans, software development models and work break down structure.
· Write your Personal Log.
· Prepare questions to ask the client.
· Contact convenor and our client, which I already did. The convenor has replied and said we should contact our client ASAP. The client suggested to meet at a time which I couldn't make it (Thur 10.00, he wanted us to meet him at his office in South Yarra. 2-3 of us can go.).

2.5 Next Meeting – Monday 18th August, 1.00PM
· We will decide role for everyone base on the skill assessment document
· Decide the software development model we should use (might be changed according to customer)
· Make questionnaire document for getting requirement
· Prepare all legal related documents.
· Build a brief WBS for project management and software development.
· Decide who will meet the client during the week.

2.6 Meeting Adjourned – 4.00PM

3. Meeting 3, 18th August 2008

3.1 Meeting Opened – 1.00PM
The meeting was initiated as our weekly meeting which we will have every week.
All team members are in attendance – Kevin, Andrew, Chinh, Chuong, Hai, Vivi.

3.2 Progress Report
· We decided on the roles for each team member to do.
· Discussed the questions in which we should ask the client at the interview.
· Complied some questions to ask Buzz about the issues we weren’t sure with.
· Discussed the best time to setup for the interview with client and then emailed him.
· Also further decide what software tool we are going to use for our project.

3.3 General Business
· It was our third meeting for the project and now we are slowing developing the project and gathering all the information together to complete the project.
· Looks like we will be having our first interview with the client this Thursday 21st August and Kevin, John and Myself will be attending the interview.
· We have sorted team responsibilities and requirements needed to have a successful project.

3.4 Actions to be Taken
· Kevin will email the client to confirm time and date for interview and type up questions to ask buzz about our project for Tuesday meeting.
· Hai will finalize our team responsibilities for each other and type it out in a word format.
· John will type up questions to ask the client at the interview
· Vivi will do further research on software and management tools to use.
· Gu to compile his skills assessment
· Andrew to print off the legal form for everyone to sign. Also to compile the minutes up together in a formal style.

3.5 Next Meeting – Tuesday 19th August, 3.30PM
· Finalize questions for interview
· Have the software model ready
· Decide task in meeting with client
· Build brief WBS for the project management
· Build brief WBS for software development

3.6 Meeting Adjourned – 2.30PM