GSD2010

1. Introduction

2.  Share media materials about team members between different teams

3. Self-introduction by each team member (16 min, each one 2 min) and Q&A between different teams (14 min)

4.  Discuss thoughts on the project and touch on ideas.

5. Decide time and agenda for next meeting

 1. Process and collaboration tool

2. Common ground

3. Ideas for project

Summary of Discussion:

⒈  Talked about  the process and collaboration tools. 

⒉  Established the common ground. 

⒊  Discussed the ideas of project.  

Summary of Decision:

⒈  Collaboration tool: Use Assembla that has all the required features for collaboration. 

⒉ Process: Use Scrum as the method for agile development. 

⒊Programming language: Java. 

The same common ground: Focus on process and running software.

Tasks of the next week:

⒈Keep brainstorming about ideas, and come up with a concrete idea next week 

⒉Study the process methods(agile process, Scrum) 

⒊ Study collaboration tool: Assembla. 

⒋Study Blip Node.

 1. Finalize brainstorming session - vote for scenes

2. Tasks for next week

• Idea for project: we all agreed on scene 12, implement a green game for our campus.
• Process: we have some problems with figuring out a common process:

1.  We have to check with our teacher what our iterations are about.
2.  We need an agile process
3.  You want a waterfall model with everything thourougly documented.
4.  Discuss this through email on Monday.
5.  Write down all requirements and figure out which ones we will implement first.

• Agenda for next meeting

Summary of Discussion:

⒈  Talked about  the feasibility of agile process and difficulties faced with in each team.

⒉  Voted for scenes and decided the scene of project.

⒊  Tasks for next week.

Summary of Decision:

⒈  We basically come to an agreement about the 2-iteration process, many details of which will be decided on Tuesday after Danish team ask their supervisor.

⒉  After voting, we finally decided the scene of 12, which will culture people the awareness of environmental protection by ascending or descending points in a green game.

⒊ This week, we will come up with the specific thinking by e-mail and Assembla.

Tasks for next week:

⒈Confirm use cases and concrete requirements in each iteration.

⒉Discuss the ideas of the scene via Assembla.

1. Follow up from last time (process and project requirements)

2. Elaborate the Green Game

3. Schedule for the iteration

4. Establish next meeting

Summary of Discussion:

⒈  Follow up on some stuff from last meeting

⒉  Decide the schedule of the first iteration.

⒊  Meeting time of next week.

Summary of Decision:

⒈  We all come to an agreement about the agile process ,and we will finish a set of documents together, and permit a little change.

⒉ After talked the specific ideas of green game, we finally decided Chinese team is going to write a draft of requirement document by Friday, and Demark team revise it before the next meeting.

⒊ Due to the holiday, we will change our meeting time on 7^th April.

⒋We decide the schedule of first iteration: We will have to finish the design and architecture by the 12^th in order to have time to finish some implementation by the 19^thwhen the Denmark teams have to hand in.

Tasks of the next week:

⒈DK team will write game idea on Assembla and everybody adds stuff until Tuesdays. Chinese team will formulate draft requirements and send DK them by Friday, and they will revise it.

⒉Have a good holiday.

1. Discuss the software requirements

2. Discuss ideas the design and architecture

1. Discussion of the SRS document:

 - rules of the game need to be added (we will post on assembla all the ideas and the Chinese Team will formalize them as Appendix in the SRS document)

2. Discussion around the design

- what the design and architecture document

- design document will be done in 2 iterations (for first iteration we will do the web interface part using REST and for sencond we will add message sending using RMI)

- Danish Team will provide draft document by Monday (12/04)

3. Establish next meeting (Monday - 12/04 or Tuesday 13/04) - send email for follow up

 1 Rules of Game

Chinese team will add the rules of game as the appendix of SRS.

2 Design documentation

Danish Team will write design and architecture document at the same time.The draft will  be finished by Monday.

3 Next meeting time: It maybe hold on Monday.we will send Email to confirm.

  1. Potential collaboration issues

    2. Success criteria for the project

    3. Discuss the design and architecture - special focus on this

    4. Discuss game rules

1. Discussion on potential collaboration issues: our idea for such process would be that each side (DK and China) writes the collaboration issues they've identified on assembla. This should be done each Friday. In this way. The next time we meet we'll be able to discuss possible solutions to the raised issues.
Writing them on assembla we'll also be able to track reoccuring issues.

2. After we formuate and agree on success criterias for our project we should come up with some way of measuring them, in order to be able verify if we've actually met our "high-level" success criteria. (Example: we could say as a general idea that the success criteria is to meet the deadlines that we set and implement what we plan (this can be measured with no of closed tckets).)

3. By tomorrow, 13.04 the design document should be ready and then we will discuss how and what will we implement for the first iteration. We will communicate through email tomorrow.

4. We have agreed on several issues concerning the game rules.

 1 Discussion of the design and architecture.Danish team have finished the class diagrams, and will still add other items.so we will talk the details later.

2 Potential collaboration issues:Each side (DK and China) will writes the collaboration issues they've identified on assembla. This should be done each Friday. In this way. The next time we meet we'll be able to discuss possible solutions to the raised issues.

3 Talk about the success criteria for the project.Each side has different focuses.

4 We have agreed on the points rules finially after disscuessed some issues.

5 Next meeting:it will decided through Email.

1. Database schema

2. Clarify any uncertainties about the design and architecture.

1. Some decisions concerning tables:

We decided to have 2 databases for the points.

The Points table should have as fields: usreId, date, noOfPositiveElevatorPoints, noOfNegativeElevatorPoints, noOfPositiveStairsPoints, noOfNegativeStairsPoints, totalNoOfPoints. The GroupPoints table, and update it when a member of thet group gets more points.

2. Still in doubt about using REST or RMI.

 1 Discuess the problem of database Design.Finally, we decided to add 2 tables for the points including The Points table and  The GroupPoints table which  will update when a member of that group gets more points..

2 Talk about the usage of REST,we haven't decided it yet.It will decide at tomorrow.

Another meeting at 23:00 GMT+8:

Continued talking about the REST,Denish team give us an example of REST, we will learn it and ask our supervisor to decide whether use it or not.

3 Next Meeting: It will confirm by Xue, she will email to all of us.

1. REST vs RMI

1. We decied we will use REST for now.

 Summary of Discussion:

 1. Decided to use REST for the 2 iterations in the system development.

2. Discussed about the division of labor initially and excplicited the different focuses of each team. 

3. Decided the time and agenda for the next meeting.

Summary of Decision:

1. Decided to use REST for the 2 iterations in the system development.

2. Decided that each would discuss about specific division of labor before the next meeting and we would discuss about this in the next meeting.

3. The time for the next meeting is 19:00 GMT+8 on 17th April.The agenda for the next meeting is : to discuss about the division of labor; to discuss about the success  criteria of the development and the collaboration issues of the development.

1. Succes criteria and collaboration issues. (max 1 hour)

2. Division of work (20 minutes)

3. Team contract

  1. When discussing success criteria, we realised that we don't have the same focus, although when we first talked about it, we reached an agreement. We have established a common focus that can be found in the Global Team Contract.

Both teams should put up on assembla their potential collaboration issues, rank them and suggest possible solutions. This should be done on a weekly basis before Friday, and the solutions and progress should be discussed during the meetings on Saturdays.

Both teams should formulate their success criteria and a method to rank them. This should also be put up on assembla.

2. An implementation plan/division of labour should be set by both teams and put up on assembla. It will be disscussed during the next meeting.

 1  Discuss solutions to the issues each side have identified.We found that we have different focuses.But,in fact, we both focus are not conflict.Usable product is must.

Our team will put up solutions of potential collaration on assembla before Monday.We also should formulate our success criteria and a method to rank them. This should also be put up on assembla.

2 About plan of labour: Both sides will put their ideal division of labour to assembla, we will discuess during the next meeting, it will save time.

3 Next meeting: it will held in 19:00 GMT+8.

Agenda:1 Continue discussing the collaboration issues.

2 Decide the division of labour.

1. Continue the talk on collaboration issues

2. Global team contract

3. Division of work

We discussed mitigation strategies for the problems each team had posted on Assembla.

During the meeting we covered the Chinese team’s issues 1-5 and quickly ran over their issues 6 and 7 (with the exception of the issue “The work efficiency：maybe our work efficiency is not high”, since the person who had written it was not present and everybody had difficulty understanding it). The following is the Chinese issues that are similar to the Danish (CN-DK): 1-2, 2-1, 3-3, 5-7, 6-6, and 7-5. We more or less agreed with the solutions the Chinese had suggested for their issues, with the exception of issue #5 where the Danish solution was chosen. The following will touch on the issues where detail is required in order to fully understand the agree strategy of the issue. Issue #6-7 is believed to be solved.

Additional ellaboration for some of the issues discussed.

1) The procedure will be that if we feel that the other team might not have fully understood what we meant. We try and write it more detailed on assembla’s message board, so everybody have a chance to look at it and reply. This way we do not have to necessarily arrange a new meeting to clarify or ask for clarification.

3) Agreed on putting a timetable on assembla, where each team member would add their schedule. This would be done the day after the meeting.

4) The Chinese will get a copy of the report or an excerpt when it is done to get a better understanding of the process.

5) The items for the agenda written in the minutes will be pasted into a post on the assembla message board. New items will be added a reply to this.

Next meeting Thursday the 22/4 14:30(DK).

Agenda: Talk about the sprint.

 1 Discuessed the solutions of some collaboration issues that have reached consensus:

(1)When one side come up with a new idea,it will be writen more detailed on message board of  assembla, so  as to everybody have a chance to look at it and reply.

(2)We will make a time table on assembla to solve the problem of different time  .

(3) The agenda items we have writen in the minutes should also will make a link to the message board. Then if a team member has an item that he/she would like discussed on the next meeting it should be added by replying to the message. The reply should contain the item name and an explanation of the item.

2 Division of work:The whole project will be devided into 2 sprint.we made a small implemenation plan for each sprint.we listed the tasks that we think are necessary.the idea is to have a plan for each sprint and document it a bit and after we have the tasks everyone is free to choose what better suits him/her.

Next meeting: 22,04 Thrusday 20:30 GMT+8

Agenda:Talk about the content of sprint, see if it is feasible or not and assign responsibles for tasks.

• Discussion about the sprint document and tasks.

Discussed the first sprint. We have assigned ourselves to tickets and the Chinese would assign themselves to the rest later.

No new meeting was discussed.

No new agenda was discuseed.

 We discussed the first sprint and finished the division of labor.The deadline of first sprint will be at 30th,April.

No new meeting was discuessed.