Received: from [139.222.1.3] by messenger (ArGoSoft Mail Server Freeware, Version 1.8 (1.8.6.4)); Fri, 4 Feb 2005 15:10:32 +0000 Message-ID: <001001c50acb$c83b5e60$0301de8b@participant2> From: "participant2" To: References: <01c50aca$Blat.v2.2.2$c2d42322@messenger> Subject: Re: Please summarise the last meeting Date: Fri, 4 Feb 2005 15:11:18 -0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000D_01C50ACB.C7562E80" 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_000D_01C50ACB.C7562E80 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: participant2@ami=20 Sent: Friday, February 04, 2005 3:04 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. We discussed compontent design, and options for each part of the = whole, as well as possibilities and usefulness of all bits of the user = interface and some resent trends in fashion and what people want.We = concentrated quite a lot on the key ideas of fashion and simplicity and = how to make those ideas work in our final design. =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. kinetic battery* simple chip* push buttons latex curved case* =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. is scroll wheel good or not? keeping price down* how to make sure it functions correctly* =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. ------=_NextPart_000_000D_01C50ACB.C7562E80 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, February 04, 2005 = 3:04=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.

 We=20 discussed compontent design, and options for each part of the whole, = as well=20 as possibilities and usefulness of all bits of the user interface and = some=20 resent trends in fashion and what people want.We concentrated quite a = lot on=20 the key ideas of fashion and simplicity and how to make those ideas = work in=20 our final design.

 

 

 

 

 

 

 

 

 

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

 kinetic=20 battery*

simple=20 chip*

push=20 buttons

latex=20 curved case*

 

 

 

 

 

 

 

 

[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.
 is=20 scroll wheel good or not?

keeping=20 price down*

how=20 to make sure it functions correctly*

 

 

 

 

 

 

 

 

 

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

------=_NextPart_000_000D_01C50ACB.C7562E80--