Received: from [139.222.1.4] by messenger (ArGoSoft Mail Server Freeware, Version 1.8 (1.8.6.4)); Fri, 28 Jan 2005 11:45:47 +0000 Message-ID: <001901c5052f$148e2970$0401de8b@participant3> From: "participant3" To: References: <01c5052c$Blat.v2.2.2$49698d22@messenger> Subject: Re: Please summarise the last meeting Date: Fri, 28 Jan 2005 11:46:57 -0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0015_01C5052F.11E92120" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 This is a multi-part message in MIME format. ------=_NextPart_000_0015_01C5052F.11E92120 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable For the documentation of the design project, you and all of your = colleages are asked to fill out a short questionnaire after e ----- Original Message -----=20 From: HeadOfDept@ami=20 To: participant3@ami=20 Sent: Friday, January 28, 2005 11:27 AM Subject: Please summarise the last meeting Dear Colleague, =20 Would you be so kind to report to me on the past meeting? Please hit = the reply button and fill in the questions below, then click send. = Please keep in mind that your notes are part of the project = documentation - among other things, they will be used by myself and = other staff to stay informed about the state of the project. It is = therefore essential that your notes - though kept short - are of high = quality. In particular: =20 a.. Do not use any abbreviations.=20 b.. Write notes that are understandable for somebody who was not = present during the meeting=20 =20 The head of your department =20 =20 [ABSTRACT] Write one paragraph of coherent text to summarize the = meeting as a whole from your role's perspective. The meating met its aim in that the people at the project had a = chance to meet each other, and get to know each other to some extent. As = for the product, I personally was hoping to leave the meeting with a = clearer idea about what we wanted to achieve. Probably this is going to = be in the agenda of one of the next meetings. However, we specified the = following three goals about the project, namely that we want it to be = original, trendy and user friendly. The meeting did not satisfactorily = explain my responsibilities in the project, but this might also be fine, = considering that we are in the very initial stage of the project. =20 =20 =20 =20 =20 =20 =20 =20 =20 [DECISIONS] Name all decisions that were made during the meeting. = Mark those decisions that you consider of high importance for your role = with a *. Write fragmented notes. - product has to be original, user friendly and trendy * - a note on originality - cannot compromise user friendlyness = - in major points has to conform to standards set by previous remote = controls - three satges in product development: functional design, conceptual = design, detailed design - production cost not to exceed EUR 12.50 - selling price EUR 25 =20 =20 =20 =20 =20 =20 =20 =20 =20 [PROBLEMS/ISSUES] Name the problems or difficulties that occurred = during the meeting. Mark those that you consider of high importance for = your role with a *. Write fragmented notes. No major difficulties occurred this time. Maybe the fact that our role specifications are still not entirely = clear. * =20 =20 =20 =20 =20 =20 =20 =20 =20 [ACTIONS] Name the next steps that each member will take until the = next meeting. Write fragmented notes. - Think about the responsibilities assigned to them, or that they = think they are responsible for. - Interface designer - what functions should the remote control have? - Industrial designer - maybe what we might need in the production = process - e.g. materials, resources, machines. - Prepare the agenda of the next meeting, and new goals to be set - Marketing manager - some market research ------=_NextPart_000_0015_01C5052F.11E92120 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable For the = documentation of the design project, you and all of your colleages are = asked to fill out a short questionnaire after e
 
----- Original Message -----
From:=20 HeadOfDept@ami
Sent: Friday, January 28, 2005 = 11:27=20 AM
Subject: Please summarise the = last=20 meeting

Dear=20 Colleague,

 

Would you be so = kind to=20 report to me on the past meeting? Please hit the reply button and fill = in the=20 questions below, then click send. Please keep in mind that your notes = are part=20 of the project documentation =96 among other things, they will be used = by myself and other staff to stay informed about the = state of=20 the project. It is therefore essential that your notes =96 though kept = short -=20 are of high quality. In particular:

 

  • Do not=20 use any abbreviations.=20
  • Write=20 notes that are understandable for somebody who was not = present during=20 the meeting

 

The head of your=20 department

 

 

[ABSTRACT]   Write one paragraph = of=20 coherent text to summarize the meeting as a whole from your = role=92s=20 perspective.

 The=20 meating met its aim in that the people at the project had a chance to = meet=20 each other, and get to know each other to some extent. As for the = product, I=20 personally was hoping to leave the meeting with a clearer idea about = what we=20 wanted to achieve. Probably this is going to be in the agenda of one = of the=20 next meetings. However, we specified the following three goals about = the=20 project, namely that we want it to be original, trendy and user = friendly. The=20 meeting did not satisfactorily explain my responsibilities in the = project, but=20 this might also be fine, considering that we are in the very initial = stage of=20 the project.

 

 

 

 

 

 

 

 

 

[DECISIONS]   Name all decisions = that were=20 made during the meeting. Mark those decisions that you consider of = high=20 importance for your role with a *. Write fragmented notes.-=20 product has to be original, user friendly and trendy *

   =20     - a note on originality - cannot compromise user=20 friendlyness - in major points has to conform to standards set by = previous=20 remote controls

-=20 three satges in product development: functional design, conceptual = design,=20 detailed design

-=20 production cost not to exceed EUR 12.50

-=20 selling price EUR 25

 

 

 

 

 

 

 

 

 

 

[PROBLEMS/ISSUES] Name=20 the problems or difficulties that occurred during the meeting. Mark = those that=20 you consider of high importance for your role with a *. Write = fragmented=20 notes.
No=20 major difficulties occurred this time.

Maybe=20 the fact that our role specifications are still not entirely = clear. *

 

 

 

 

 

 

 

 

 

[ACTIONS]  Name the next steps that = each=20 member will take until the next meeting. Write fragmented=20 notes.

-=20 Think about the responsibilities assigned to them, or that they think = they are=20 responsible for.

-=20 Interface designer - what functions should the remote control=20 have?

-=20 Industrial designer - maybe what we might need in the production = process -=20 e.g. materials, resources, machines.

-=20 Prepare the agenda of the next meeting, and new goals to be=20 set

-=20 Marketing manager - some market=20 research

------=_NextPart_000_0015_01C5052F.11E92120--