[team33] Re: Very important: Project Roles

  • From: Fredrik Stenberg <frest167@xxxxxxxxxxxxxx>
  • To: team33@xxxxxxxxxxxxx
  • Date: Sun, 10 Oct 2004 23:36:42 +0200

hmm what happened to that mail..???

hi so no one else is interested in the knowledge manager role? 
I cant say Im thrilled but I will be knowledge manager if no one 
 else wants to
 So mail quickly if you do want to be knowledge manager

/Fredrik
> 
> ----- Original Message -----
> From: Alexei Kounine <aleko379@xxxxxxxxxxxxxx>
> Date: Tuesday, October 5, 2004 10:51 pm
> Subject: [team33] Very important: Project Roles
> 
> > Hej guys!
> > Now you can (and must) send all the emails using this contact list.
> > Now i want to talk to you again about roles.
> > I think that what we did until now is ok, but could be better. The
> > problem is 
> > the roles that i've assigned. They are not precise enough, and 
> > this is
> > why 
> > everybody comes to the meetings without getting anything from it.
> > Now i will give you a list of very precised roles considering 
> what you
> > told me 
> > you wanted to do, and what you already did:
> > 
> > -the main problem is now the Knowledge manager. He's the one who 
> > is supposed to write 
> > something about every meeting that we had, and will have to 
> report 
> > problems and 
> > good things about everything that we do in quite a precise way. All
> > this will be hold in one document, that he will take care. Every 
> > week he will have
> > to ask the other guys from the group about their impressions, 
> and 
> > their working
> > methods, and the problems they encountered. This doesn't mean 
> > that he has to be
> > at all meetings: if he cannot come, he will ask someone who has 
> > been to the
> > meeting to write a meeting report and send it to him. As Anton 
> (he 
> > was supposed
> > to have that role) hasn't been to the meetings this week, i 
> think 
> > that someone has
> > to take that role. I think that Frederik will be good at doing 
> at 
> > it. So Frederik,
> > please start taking care of it right away, unless you really 
> hate 
> > that role. This
> > role is important, and has to be done seriously. If you have 
> problems> remembering the first meetings, tell me and i will give 
> the 
> > details to you.
> > 
> > -as already said before, Markus will be the architect of the 
> project.> He will take care of the coding part. He will also 
> communicate with
> > the knowledge manager, and tell him about the problems he 
> encountered> with this. Rama  will be his main assistant and 
> Martin will be another
> > potential coder (he will have another role, see further). I 
> think that
> > a team of 2 or 3
> > people is enough for the code itself. I (Alexei) will also
> > help, especially with the communication with the other groups. 
> Markus> will also be responsible for the design report (3rd
> > deadline). He can start it right now, by trying to do an EER diagram
> > of the database. He will be responsible for setting the meetings 
> about> the design part. There is a need for us all to consider the 
> different> solutions we have: there are tools that we can use, 
> such as hibernate
> > (may be not necessary), what kind of database we will use (there 
> > is a
> > possibility of using the java database instead of mysql, so that we
> > don't need a distant database like mysql, and can put everything in
> > the same package for testing link to open source java 
> > dbs:http://java-source.net/open-source/database-engines, and the 
> most> adviced: http://hsqldb.sourceforge.net/)? and many
> > other questions. So Markus
> > will take care of the organisation of all this.
> > 
> > - As nobody wanted to take care of the first deadline, i took the
> > responsability, even i think that i already did a lot in other
> > domains. I will still take care of the requirement specification
> > report, with the help of Rama, and others who can help me. I will
> > focus on my project leader role after that deadline: i will take 
> care> of the main meetings, talk to project leaders, and try to do 
> my best
> > to coordonate everybody, using the tools that i will describe to you
> > on thursday: Webcalendar (already used), svn and the mailing list.
> > 
> > - Yusuf will be our link to the customer. He will have to talk with
> >  him, send him mails, try to get as much information as possible
> >  about the requirements. Everyone in the team should be able to send
> >  an email to Yusuf, and he will take care of asking the customer
> >  or/and meet him. He will also have to arrange regular meetings with
> >  him to talk about the project's improvement. This role is not very
> >  big, therefore i think that Yusuf can also help me with the first
> >  deadline, and maybe others later, depending on the quantity of work
> >  each one does.
> > 
> > - Joachim and Anton will be the test leaders. They  will take
> >  care of creating testing programs, and discuss the tests with the
> >  team.They will have to arrange meetings, with people they want 
> > to see:
> >  Architect, project leader, knowledge manager, to whom they will
> >  have to give regular reports, and other guys from our group. 
> > They can
> >  already think about how they want to organise the tests, and talk
> >  to test managers from other groups, since there will be
> >  global-group tests, in addition to our component tests. They can
> >  also start talking about Yusuf about what features the customer
> >  wants as main priorities, and to their best to create tests which
> >  are as close as possible to what the customer wanted. Remember that
> >  the main purpose of testing is to show to the customer that our
> >  system works, and follows the given requirementsThey will be
> >  in charge of the test report, which is the 4th deadline.
> > 
> > - Jonas and Martin will be responsible for the second deadline: 
> > the project
> >  plan. For me this report is not really clear, that's why i can't
> >  really give them some precise tasks to do. They will have to
> >  organise meetings about this deadline, write the report, and 
> > talk to
> >  other people from the group to retrieve the information they need
> >  for the report.
> > 
> > This is what i thought about. Please tell me if someone feels
> > disappointed with his role. We will probably discuss this again next
> > time we'll meet.
> > Now i think that everybody has a precise idea of how the work is
> > shared. Ask me and the others for any questions.
> > I remind you that the deadlines are short, and that you should start
> > thinking about how you will organize your work.
> > If your working group (if you're 2 being assigned to the same 
> > task) is
> > not working well, or if you need more people, keep in mind that some
> > people have less to do, so don't hesitate to contact them, and make
> > them work with you (the roles cannot be shared perfectly equaly!).
> > 
> > Also i remember that a meeting is organised on thursday at 13 
> pm, so
> > that i tell you about the main tools that we have to start using 
> right> now. Please be there, and if you cannot ask me or someone 
> from the
> > team to explain it to you later, but be fast, we have to start using
> > svn right now. It's very important!
> > And also be there for the meeting with andreas on thursday at 15 pm.
> > This is essentially for Rama, Yusuf and me, who will do the
> > requirement specification report. But others like the Architects and
> > the knowledge manager should come as well.
> > 
> > Don't forget to use kou.homeip.net, so that everyone knows who will
> > come, and we don't have to wait for ages for someone who never 
> comes.> 
> > Thank you very much for reading that long email, but i think it's
> > necessary to be fixed on that.
> > 
> > See ya on thursday
> > 
> > /Alex
> > 
> > 
> > 
> 


Other related posts: