Team Members

Danish team

Tobias Elleboe Cordsen (contact person)

• Email: teco@itu.dk

Laura Pantis

• ITU: lapa@itu.dk

Anita Bejan

• ITU: cabe@itu.dk

Agata Przybyszewska (supervisor)

Chinese team

Xue Bai (contact person)

• Skype id: baixue.pku
• MSN: baixue.pku@hotmail.com
• Email: baixue.pku@gmail.com
  

Cheng Li

• Skype id: licheng0131
• MSN: licheng_0131@hotmail.com
• Email: licheng0131@gmail.com
  

Kezheng Yi

• Skype id: goodykz
• Email: kezhengyi@pku.edu.cn
  

Lu Wang

• Skype id: wanglu19870917
• MSN: wanglu19870917@hotmail.com
• Email: wanglu19870917@163.com
  

Qihui Li

• Skype id: pkukason
• MSN: pkukason@gmail.com
• Email: pkukason@gmail.com
  

Lin Huiping (Supervisor)

Processes and tools

• The process is going to be in accordance and within the frame of the Agile Manifesto.
• We are going to use Assembla, which supports this agile method by providing facilities for scrum meetings, a ticket system, a wiki, and message board.
• Team communication will be through Skype, messenger and email.
• For code reviews we plan on using Skype's screen sharing function.
• Documents/files will either be kept at the Assembla wiki or files section or submitted to SVN.
• When the ticket responsible team member is done with the ticket he or she will reassign it to another (uninvolved) team member for verification before the ticket gets closed as fixed.

Principles of interaction

• Ilness and delays must be informed to the group members as quickly as possible. This can be done by email or skype.
• All suggestions and thoughts must be taken seriously and considered by the group as a whole. We will decide upon suggestions by vote if an agreement can't be found. All members are expected to speak english during the meetings.
• Every group member is expected to be present during the meetings and respect the the agreements made in the group. During peak workload times, each group member should prepared for an increased workload. Furthermore each group member is supposed to do their individual assignments before the deadline set by the group.

Conflict Mitigation Plan

Every Friday each team will do a session (approximately 30 minutes) where they gather any issues the feel are present in the collaboration. A rule of thumb is that no issue is to little and that everything should be gather. It is not a discussion about the issues, but more of a brainstorm to bring up any issues any team member might feel is present. When all the issues have been listed each team member will then give each issue a number between 1 and "the number of issues", where the lower  the number the higher the importance. After every team member has rated all the issues the numbers are then added together, which denotes the team's severity ranking of the issues. The next part is to come up with possible solutions to each of the issues. Starting with the issue with the highest severity. After both issues and possible solutions have been identified everything will be written on collaboration issues during Friday. During the next meeting we will discuss the issues raised and solutions to them.

Team focus

Danish team

Project formulation for the project:

By developing a piece of software for the context aware system, in collaboration with peeking University, we will try to identify the challenges that may be of such a collaboration across borders. We will do this by working in an agile software development context, more specifically, our frame of reference will be the agile manifesto. The aim will be to identify the challenges of working agile and to the extent it is possible adapt the current development method to overcome these. All this is based on the philosophy that a good development method precedes good software.

Our main focus will be the process. This includes close team work, frequent meetings to avoid misunderstandings and keep the project on track.

Success criteria

Good process and good collaboration

• Keep track of number of issues raised each week, solved, and how many are reoccuring.
• Meet the deadlines we set. How many times are we pushing the deadlines?
• Usable product in accordance with playtest, though we probably won't be able to playtest it.
• The process should be the same for all and it should be followed.
• That the defined process we are following is in correspondance with the agile manifesto.

Chinese team

Our main focus will be the software product and the fully-formed documentations. This includes the well-running software, the SRS, the documents of design and architecture and some documents which may be added in the following process.

Success criteria

Good product, fully-formed documents and good collaboration

• Meeting the deadlines we set.
• Usable product in accordance with playtest, which has nearly all (80 percent or above) the high-priority funcitons listed in the SRS, though we probably won't be able to playtest the product.
• A set of accomplished documents, such as SRS, documents about design and architecture (which could be finished in two or three iterations).
• The win-win collaboration between Danish team and Chinese team based on the Global Team Contract.The relation between 2 teams not only partners but friends.

Common ground of expectations

These are the minimum requirements and exepectations for the common part that we agree on and will expect from each other.

Each team has a focus, the Danish being the process, the Chinese being documentation and product. Each team will invest the most time in their focus, but agrees to help out the other team achieving their focus.