Resumee
Here's my resumee from the view of the project manager ...
Resumee (by Christian Haudum, team manager)
Difficulties
There didn't really mediatechnological difficulties during the workout phase. The only thing
that came up with little problems was the usage of Firefox addons for the export of
Microformats.There are 2 common tools for Firefox to detect Microformats on a website:
Operator (https://addons.mozilla.org/en-US/firefox/addon/4106) and Tails Export
(https://addons.mozilla.org/en-US/firefox/addon/2240). I didn't get managed to format the
markup so that the Microformats could be read and exported correctly by both of them. So I
decided to use the Syntax which was supported by Tails Export, because it can also be used by
a web based Microformats exporter at Technorati.
What did I learn within the semester project?
Because I already got in touch with Microformats before the project I knew some basics and
was able to understand the functionality of the markup system. The project now opened up a
deeper view into the standards behind it. In addition to it I could also softly improve my skills in
MySQL databases and Apache servers.
Group work
We were 4 people in the group:Pim Odekerken, Len Canoot, Markus Jalonen and me. In the
beginning we split up in to parts.On the one hand the programmers (Markus, Christian) and on
the other hand the designers (Pim, Len). The programmers' goal was to set up the database, to
write the scripts and to provide the framework of the website with that the designers could
create the graphical interface of the system.
As a additional part of communication we also set up a blog (https://microformatics.twoday.net/)
as well as a social bookmark page (http://del.icio.us/microformatics). This should give everyone
on the group an overview about what the others are currently working on. The idea was to share
the experiences and ideas that came up during the project.
But things didn't run well. After two unsuccessful approaches making a meeting (the first short
after Easter,the second two weeks later) – nobody attended the meeting – I decided not to
wait for the others' work but going on my own way.The blog and the social bookmarks weren't
use by the others, too. It was not the first time that I experienced such a behaviour in group
work at Vorarlberg University of Applied Sciences. The problem is, that you as a project
manager don't have any possibilities to force someone to participate in the project if someone
doesn't want to. Not until the end I was told, that the reason, why I lost support from my team
members, was that the difference of the knowledge within the topic of our project was too big.
Unfortunately the insight came too late, and so the project suffered enormously only because
of a lack of communication. Summarising, in the end I did all the programming and the basis for
the designers which came up with a layout that fulfills just its really basic needs.
as pdf file: resumee (pdf, 32 KB)
Resumee (by Christian Haudum, team manager)
Difficulties
There didn't really mediatechnological difficulties during the workout phase. The only thing
that came up with little problems was the usage of Firefox addons for the export of
Microformats.There are 2 common tools for Firefox to detect Microformats on a website:
Operator (https://addons.mozilla.org/en-US/firefox/addon/4106) and Tails Export
(https://addons.mozilla.org/en-US/firefox/addon/2240). I didn't get managed to format the
markup so that the Microformats could be read and exported correctly by both of them. So I
decided to use the Syntax which was supported by Tails Export, because it can also be used by
a web based Microformats exporter at Technorati.
What did I learn within the semester project?
Because I already got in touch with Microformats before the project I knew some basics and
was able to understand the functionality of the markup system. The project now opened up a
deeper view into the standards behind it. In addition to it I could also softly improve my skills in
MySQL databases and Apache servers.
Group work
We were 4 people in the group:Pim Odekerken, Len Canoot, Markus Jalonen and me. In the
beginning we split up in to parts.On the one hand the programmers (Markus, Christian) and on
the other hand the designers (Pim, Len). The programmers' goal was to set up the database, to
write the scripts and to provide the framework of the website with that the designers could
create the graphical interface of the system.
As a additional part of communication we also set up a blog (https://microformatics.twoday.net/)
as well as a social bookmark page (http://del.icio.us/microformatics). This should give everyone
on the group an overview about what the others are currently working on. The idea was to share
the experiences and ideas that came up during the project.
But things didn't run well. After two unsuccessful approaches making a meeting (the first short
after Easter,the second two weeks later) – nobody attended the meeting – I decided not to
wait for the others' work but going on my own way.The blog and the social bookmarks weren't
use by the others, too. It was not the first time that I experienced such a behaviour in group
work at Vorarlberg University of Applied Sciences. The problem is, that you as a project
manager don't have any possibilities to force someone to participate in the project if someone
doesn't want to. Not until the end I was told, that the reason, why I lost support from my team
members, was that the difference of the knowledge within the topic of our project was too big.
Unfortunately the insight came too late, and so the project suffered enormously only because
of a lack of communication. Summarising, in the end I did all the programming and the basis for
the designers which came up with a layout that fulfills just its really basic needs.
as pdf file: resumee (pdf, 32 KB)
Microformatics - 28. Jun, 21:28
