Received: from [139.222.1.2] by messenger (ArGoSoft Mail Server Freeware, Version 1.8 (1.8.6.4)); Wed, 16 Feb 2005 12:37:06 +0000 Message-ID: <004201c51424$7474b170$0201de8b@participant1> From: "participant1" To: References: <01c5141a$Blat.v2.2.2$27b9dec8@messenger> Subject: Re: Please summarise the last meeting - meeting 2 Date: Wed, 16 Feb 2005 12:38:44 -0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_003F_01C51424.7398A950" 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_003F_01C51424.7398A950 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: participant1@ami=20 Sent: Wednesday, February 16, 2005 11:25 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. =20 The meeting began with the project manager opening the meeting, and = discussed the agenda. Then each team member presented their findings, = which came as a result of a period of independent work. Discussions = took place regarding the design of the remote control. The new product = requirements were introduced by the project manager, and then more = discussion occurred. The meeting closed with an overview of the next = few hours. =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. =20 determined target group - all ages, little to no tech. experience *determined fuctions - change channel, raise or lower volume, mute, = turn on off, light up at night, perhaps have voice recognition. , have = company logo and color, have menu access =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. =20 Have raised more issues and not made definitive decisions (i.e. power = source - batteries or charger?, speech recognition?) =20 =20 =20 =20 =20 =20 =20 [ACTIONS] Name the next steps that each member will take until the = next meeting. Write fragmented notes. PM - type up minutes other team members - research ------=_NextPart_000_003F_01C51424.7398A950 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: Wednesday, February 16, = 2005 11:25=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 meeting began with the project manager opening the meeting, and = discussed=20 the agenda.  Then each team member presented their findings, = which=20 came as a result of a period of independent work.  Discussions = took place=20 regarding the design of the remote control. The new product = requirements were=20 introduced by the project manager, and then  more discussion=20 occurred.  The meeting closed with an overview of the next few=20 hours.

 

 

 

 

 

 

 

 

[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.

 

 determined=20 target group - all ages, little to no tech. = experience

*determined=20 fuctions - change channel, raise or lower volume, mute, turn on off, = light up=20 at night, perhaps have voice recognition. , have company logo and = color,=20 have menu access

 

 

 

 

 

 

 

[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.

 

 Have=20 raised more issues and not made definitive decisions (i.e. power = source -=20 batteries or charger?, speech recognition?)

 

 

 

 

 

 

 

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

 

PM -=20 type up minutes

other=20 team members - = research

------=_NextPart_000_003F_01C51424.7398A950--