Too much tasks was planed to this lesson. Half of them were skipped. But that’s OK. The learning process was not affected and skipped tasks can be part of next lesson.
Skipped tasks:
1. Editing of the students’ profiles in del.icio.us – stays for next lesson.
2. Students’ networks creation in del.icio.us – the network was already built by students.
3. Exercise of definition of project problems – it is deleted from del.icio.us and will presented again for next lesson.
The tagging mistake is corrected. Still 3 students out of 13 don’t add tags or input separated words as one tag. Del.icio.us counts them as separated tags. Separator of tags is space.
Teams
The formulation of project team was taking place IRL. This process was a bit clumsy but still very interesting. It appeared that one of the elected project managers (X) was missing, and students started to fight against here. Probably X was afraid to visit the class.
What was the problem?
Students claimed that X was lobbing them to give their votes to here. It was previously none that other student (Y) wanted to become a project manager of same project (school end party). On Election Day Y was missing and students elected X to school end party manager and Y was elected to school start party project manager. Now they decided that this is wrong and X can’t be the project manager. They agreed that Y is the manager of school end party.
So the school start party project was with out project manager. I decided that student who collected second amount of votes will become a project manager. Two students shared second place, but one of them (W) was missing. One of them (Z) started to form the team. During the selection of team members appeared that most of the selected students did not wanted to work with him. Z is a boy, but most of the students are girls. Maybe this was the problem. But I did not let them to form the team only from bois. Z decided not to be the project manager. The school start party project manager was still needed.
Finally we went back to W who was missing. I asked, is there in the class any friend of W? V said that she’s a friend of W. I asked, is V ready to form the team for here? She agreed and the formulation of teams started.
Bloody soap opera! 
)
The process of team formulation:
1. At first the project manager (V), who collected the smallest amount of votes selected member to here team. She was first because I wanted the less popular (maybe also weakest) project manager to have strongest coworker.
2. Secondly the project manager (Y) who collected second amount of votes selected a team member from class students.
3. Thirdly the most popular project manager was making here chouse.
This process continued until all students were separated in to three groups. I was making the notes in to my computer who is selected in to what team and who is still free. In the end there was a bit inconvenient moment – nobody wanted to select last students. I decided that last two will join with summer party team because it’s the most difficult project and it needs more staff. It’s good to be a teacher and act like a God. )
From other hand it would be nice to present my notes about team formulation on screen. In this way students can see who is selected and who is left. From other hand maybe it would be embarrassing to them who are left to the end.
Document creation in docs.google.com
Some of students already had Google Docs account. Probably they have gmail account. Some of them didn’t finish the account registration. The account confirmation was sent to them by e-mail. In this e-mail there is a link where user must click to confirm the account creation. Some of the students were not able to read that e-mail because they did not remember the password of e-mail web client. This password is usually stored in user computer and at home they login automatically. I asked them to register Google Docs account at home. I’m not sure that they will.
The process of creation of document:
1. Each team collected together next to one computer (3 different groups).
2. They selected CIO who started the document (3 different CIO).
3. Based on my suggestions CIO typed the title of document.
4. CIO created the list of team members. Other students helped here to do that (they memorized the names of missing students).
5. CIO saved the document and shared it with team members (team members typed in there e-mail addresses).
6. Team members went back to there PCs and opened the shared document. They selected here names and typed in the rolls or responsibilities that they would like to have in this project.
7. CIO published the document.
8. CIO tagged this document on here del.icio.us page.
9. All members copied this bookmark to there personal del.icio.us page.
There were some technical problems because some of the students were enable to activate Google account. They continued the work with CIO. One of teams had management problems. They did not know how to share responsibilities. I explained that they can change the rolls later.
Software development idea: It would be nice to have complete list of course materials. Then students can see, what will happen on next lesson. Today I don’t have this list because I create materials on the run. On the other hand it’s very convenient, that del.icio.us starting page shows the content of today’s lesson. Maybe it is good to have two different interfaces – the course view and the lesson view. Now the course view is in LeMill and lesson view on del.icio.us. It would be also nice when the first task of lesson is in the top of del.icio.us page. Currently the chronological ascending and descending sorting is not enough.
Conclusion: The class was busy and they seamed to like the Google Docks (I asked). Nobody was complaining: “Why new software again?”
Overall rate to lesson 5-
