The course log - diary format documentation of our project work and the process we go trough. Has to be updated with our project progress at least on a weekly basis.

17.05.10

Finalizing the report.

15.05.10

Meeting to establish what needs to be changed in the final report. Some articles provided by Ruth were considered and read.

12.05.10

JSP pages finished. All open tickets from milestone 2 should be closed.

10.05.10

Proposal for getting and processing data from BLIP server sent to the Chinese team. Feedback expected.

08.05.10

Some JSP pages implemented.

06.05.10

Meeting with the Chinese Team. They were concerned regarding the BLIP part that was missing. We realized that there was more work necessary for this part. We agreed that the Danish team will provide first suggestions and we will discuss them.

03.05.10

Implemented actions and provided explanations on how they should be used

28.04.10

Discussions regarding the view with the Chinese Team

27.04.10

Meeting with Chinese team to clarify blocking issues and misunderstandings.

25.04.10

ControllerServlet, PerformedActions and ActionSetter implemented.

24.04.10

Created reference project and committed to SVN. 

22.04.10

Discussed for almost three hours the division of the first sprint. We have assigned ourselves to tickets and the Chinese would assign themselves to the rest.

20.04.10

Meeting with the Chinese and finalizing first hand-in

19.04.10

Elaborate on collaboration issues.

18.04.10

Discussion about process and how to apply it. Document it in report.

17.04.10

Work for completing first assignment.

Meeting with the Chinese team. Agenda and minutes in corresponding section

16.04.10

Agenda for today:

1. Meet the chinese @ 14:00.
2. Establish our success criteria
3. Collaboration issues.
4. State of the documentation
5. (Report structure)
6. Hand-in for Monday, what are we missing?
7. The process, where are we? Focus on it, enforce it.
8. Division of labour.

1. We met the chinese at 14 to discuss about RMI vs. REST. We agreed on focusing on the REST interface.

2. We discussed what success criteria we might have for the project and wrote our version on assembla, https://www.assembla.com/flows/show/bf-J72svyr37f9eJe5aVNr. We are waiting for the Chinese to add theirs, so we are aware of theirs and they of ours and so we can begin doing weekly evaluations if the success criterias have been met.

3. We discussed collaboration issues and have added them to assembla here, collaboration issues. We are waiting for the Chinese to add theirs.

4. The documents that both we and the Chinese have been working are done, that is the SRS, rules of the game, database stuff and architecture stuff.

15.04.10

Meeting with the Chinese Team. Minutes available.

12.04.10

Meeting with the Chinese group to discuss collaboration issues and success criteria and design and architecture document. Minutes available on Wiki.

11.04.10

Finished the design and architecture document.

10.04.10

We meet to discuss the design and architecture. We agreed that we will do a MVC application and that we will focus on the web interface and we will use REST for the first and second iteration.

07.04.10

Meeting with the Chinese Team for discussing the SRS document. Minutes in the Agenda and Minutes section.

03.04.10

We received the requiremets docment from the Chinese Team

27.03.10

We discussed the different agile methods and narrowed down to feature driven development and scrum. This will be discussed with our Chinese fellows. Considering that this is an offshore collaboration, in order to increase the communication we will have a special focus on documents, even though we might contradict a bit with the agile guidelines "people should be over documents". This will increase the visibility of what we have to do. We suggest to develop the documents together with our Chinese team mates. These documents will be requirements (user stories translated into requirements), design and architecture and  testing document.

Further discussions about success criteria and the needed steps to be done for the first Global Iteration were discussed. We will send the Chinese team the worksheet for this iteration.

Minutes for this meeting:

• - Follow up from last time
    the chinese agree on working agile
    (Project requirements from DK/China side) the chinese are expected to hand-in demo and some documents.
  Follow up from last time:
  •  The Chinese agree on working agile
  •  Project requirements from DK/China side: 
    • The Chinese Team is expected to hand-in demo and some documents.
    • The Danish Team is expected to hand-in a report containing a reflection of the whole process and necessary documents for this and a piece of software.
• Elaborate on the Green Game:
  • Discussion about how the game should work. The output of this should be:
    • Danish Team will write game idea on assembla and everybody can add further comments to it until Tuesday.
    • Chinese Team will formulate draft requirements and send us by Friday.
    • Danish Team will revise the document in order to have the final document by next meeting.
    • All documents should be published on assembla as well
• Discussion about schedule for first iteration:
  • Draft requirements document should be ready by 2nd of April and revised by 7th of April. (This big lag between them is due to vacation)
  • Draft design and architecture document should be ready by the 12th of April. (During next meeting we will discuss architecture and design and the Danish Team will try to have a draft document by next meeting)
  • Implementation until 19th of April
• Next meeting Wednesday, 7th of April, 3 pm Beijing(China) - 8 am Copenhagen(Denmark)
• Agenda for next meeting:
  • Potential collaboration issues
  • Success criteria for the project
  • Discuss the design and architecture - special focus on this

20.03.10

Minutes for this meeting:

• 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

19.03.10

We finalized the project description for the course base. We got eclipse and tomcat running on Linux. We brainstormed about the scenarios for our project. We discussed the process that we will used and compared waterfall model with agile. We decided to discuss it with the Chinese teammates also. We believe that the course is organized in a way that we will have iterations and we will need to add new functionalities to our software. At the end of each sprint we will have a functional delivery and we will add functionality on top of that. We would like to have documentation and focus delivering a good product. Disscuss the agenda for tomorrow for the meeting with our Chinese friends.

17.03.10

We proposed our Chinese team members how to do the brain storming session. We discussed about how many iteration should the brainstorming have. Because we already have done brainstorming separately (one within the Chinese team and one within Danish team) and consulted them, we agrred to do one iteration together with our collegues. We agreed on using Assembla message board for doing this. We created separate threads for every idea or scene.

Here is the email that we sent out for the Chinese team:

Hi Xue,

We got an assignment from our teachers that we have to finish by the
end of the week. We hope we can complete it together with you. As you
can see we have attached the worksheet and it's about brainstorming.
You can also find it online here,
https://blog.itu.dk/KF12-F2010/files/2010/03/worksheet-brainstorm.pdf.

The proposed brainstorming session should consist of 2-3 iterations
and with each iteration consisting of the following three phases:
Phase1 - Yes, and
Phase2 - Sort and Vote
Phase3 - Prototype

Because both you and us have already used time on brainstorming we
would like to shorten the iterations down to one iteration together.

In order to achieve this, we thought we could use the message board in
Assembla. We would really like to collaborate a lot during this phase,
and in this way, everyone could post their individual ideas.

We propose the following deadline for the different phases, so we'll
be able to have a final list and a discussion by the coming Saturday.
Phase1 - Yes, and (deadline Friday)
  We have added your ideas to the message board as separate threads
and every new idea should have it's own thread. Until Friday night you
can add ideas to the message board or expand on already proposed ideas
by writing comments keeping in mind that they should all be
constructive in this phase - see also the attachment.
Phase2 - Sort and Vote (deadline Saturday before our meeting)
  Saturday before we meet every team member should look through all
the ideas and write comments (it can be things that are unclear, pros
and cons etc.). Each member should give out three votes to the ideas
he/she likes the best. This is done by adding a comment containing the
word "vote". Before our meeting Saturday we will count the votes and
have a list with the top three ideas ready.
Phase3 - Prototype (deadline Saturday during our meeting)
  When we meet Saturday we would like to have a discussion about the
outcome of the voting hopefully focusing on the three ideas which got
the most votes.

If this is in any way a problem or you have questions or other things
you would like to propose feel free to voice them.

Another suggestion is that we think it would be a good idea to CC
everybody so we don't have to forward it to the different team members
and thereby lessons the burden on us.

Have a nice day,
Laura, Anita and Tobias

13.03.10

Meeting with our Chinese friends. We established we want to use the following:

• Programming language: Java
• Process: Agile Software Development
• Collaboration tools: look into Assembla
• Scrum meetings?
• Common ground: same common ground: focus on process and running software

10.03.10

We answered the questions that we wanted to ask the Chinese, to be prepared. We also, performed a brainstorming session about what green means and what could make our campus greener.

We talked about our problem formulation.

Established some points for the agenda for next week.

05.03.10

We found out what the problem was with the example using the simulator. We finished the report for the first assignment and delivered it. We established first contact with the Chinese team.

04.03.10

Jens had time and used a lot of it in trying to help us getting it to work. In the end we came closer, but had to leave it at that since time wasn't on our side. We decided with Jens that we should talk to Francesco the next day in order for him to help us out. We began writing our findings for this first interation into the report.

03.03.10

We worked on getting the RMI example that should have been available on the pit.lab.itu.dk page, but which wasn't, working af we recieved it from Jens. We got it to work locally, but had trouble deploying it on the itu server. We were unsure of whether it connected to the blip server or not, so we wanted to look into the simulator so we could begin triggering events. As we began looking at the tutorial and the provided example we didn't feel it was very clear exactly what was required in order to integrate our RMI example with the simulator. We didn't get it to work and email Jens for assistance in the hope that he had time the next day.

We configured Hudson for automatic build on every SVN commit for our REST example.

02.03.10

We did web service example in Java using the REST interface.

Time was also used on setting up Eclipse with Tomcat.

We were still struggling with the remaining tasks 8-15 in assignement 1. The servers had been done during the weekend and in general things had been set up late and information that is needed is arriving still. This makes difficult to accomplish the remaining tasks and the feeling is that of confusion about what exactly to do and how to do it. We have been told that ITU would provide each team with a virtual server, but we are currently confused about if this is actually the case, since it seems we all log-on to the same server. Adding and running tomcat and hudson is also proving difficult. Tomcat is complaining about a control port not being available.

We deployed Hudson on the server for continuous integration.

26.02.10

Today we set up an assembla space. Even though a subversion repository were provided by ITU we decided for this first assignment to try and use the repository from assembla, since it integrates with the rest of the assembla suit than if we point to an external repository.

We began the course log and began work on the team contract. Both were added to the wiki on assembla.

We got an automated build set up using Ant.

Some tasks in the assignment 1 either seemed unclear or finding required information was difficult. We had solved the tasks from 1-6 in assignment 1.

19.02.10

We went over each of the areas of invesitgation assigned from last time, found here https://docs.google.com/Doc?docid=0AdJke12c_AgdZGNudHdjdGZfNzZkZ3JyaHJnOA&hl=en_GB.

We decided that assembla seemed like a good tool, but that we should consider if it met the following reuqirements:

• Find out what setup we use for assembla (the diff. pre-configurations).
• How to manage minutes.
• How to manage scheduling and tasks (tickets).
• How does the chat works.
• Can we use an external subversion repo.?

12.02.10

Today we had our first meeting were we decided upon which areas we had to look into in order to prepare for the upcoming collaboration with the Chinese students. We created as list of areas of investigation and distributed most of them among the team members as home work for the next meeting. The list can be seen here, https://docs.google.com/Doc?docid=0AdJke12c_AgdZGNudHdjdGZfNzZkZ3JyaHJnOA&hl=en_GB.