Received: from [139.222.1.2] by messenger (ArGoSoft Mail Server Freeware, Version 1.8 (1.8.6.4)); Wed, 26 Jan 2005 12:37:35 +0000 Message-ID: <003b01c503a4$01c75e10$0201de8b@participant1> From: "participant1" To: References: <01c503a2$Blat.v2.2.2$e569ef7c@messenger> Subject: Re: Please summarise the last meeting Date: Wed, 26 Jan 2005 12:38:57 -0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0038_01C503A4.00EB55F0" 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_0038_01C503A4.00EB55F0 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, January 26, 2005 12:31 PM 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 =20 =20 presentations went well and followed time constraint well=20 =20 good discussion and balance of opinions =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. design features * as group overode my choice tech limitations =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. some small amounts of confusion / repetition * need to keep order = better =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. me minutes / report raj research features helen initial designs=20 arlo technical specs ------=_NextPart_000_0038_01C503A4.00EB55F0 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, January 26, = 2005 12:31=20 PM
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.

 

 

 

 presentations=20 went well and followed time constraint well

 

 good=20 discussion and balance of opinions

 

 

 

 

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

 design

features=20 * as group overode my choice

tech=20 limitations

 

 

 

 

 

 

 

 

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

 some=20 small amounts of confusion / repetition * need to keep order=20 better

 

 

 

 

 

 

 

 

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

 

 

 

me=20 minutes / report

raj=20 research features

helen = initial=20 designs

arlo = technical=20 specs

 

 

 

 

------=_NextPart_000_0038_01C503A4.00EB55F0--