Received: from [139.222.1.5] by messenger (ArGoSoft Mail Server Freeware, Version 1.8 (1.8.6.4)); Wed, 16 Feb 2005 14:54:50 +0000 Message-ID: <002f01c51437$ee1d46a0$0501de8b@participant4> From: "participant4" To: References: <01c51424$Blat.v2.2.2$7e275614@messenger> Subject: Re: Please summarise the last meeting- meeting 3 Date: Wed, 16 Feb 2005 14:58:08 -0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_002C_01C51437.ED42C520" 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_002C_01C51437.ED42C520 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: participant4@ami=20 Sent: Wednesday, February 16, 2005 12:39 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 The group worked together extremely well this time to come up with = the potential model. We reached many decisions about the final design = that had been floating around the past few meetings and everybody seemed = to be happy with the end decision. The UID and ID are off to make a = model out of clay for the final product, and we look forward to what = they come up with. =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. Energy will be battery based *Soft latex interchangeable plates with hard plastic base *IPODS ARE HOT RIGHT NOW, have similar characteristics to such = technology fancy vs functional. fancy more important phrase activated locator for lost remotes *side buttons for volume/channel. large circular buttons for numbers = on top. blue buttons, illuminate yellow =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. *type of battery to be used : lithium, AA, AAA? color of base? perhaps gunmetal grey? decision of interchangeable covers for remote...fruit/vegetables this = season? *where to place logo on remote =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. UID: user-interface design ID: look and feel design Both will be constructing model from clay ME: product evaluation ------=_NextPart_000_002C_01C51437.ED42C520 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 12:39=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.

 

 

 The=20 group worked together extremely well this time to come up with = the=20 potential model.  We reached many decisions about the final = design that=20 had been floating around the past few meetings and everybody seemed to = be=20 happy with the end decision.  The UID and ID are off to make a = model out=20 of clay for the final product, and we look forward to what they come = up=20 with.

 

 

 

 

 

 

 

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

Energy=20 will be battery based

*Soft=20 latex interchangeable plates with hard plastic = base

 *IPODS=20 ARE HOT RIGHT NOW, have similar characteristics to such=20 technology

fancy=20 vs functional. fancy more important

phrase=20 activated locator for lost remotes

*side=20 buttons for volume/channel.  large circular buttons for numbers = on=20 top.  blue buttons, illuminate yellow

 

 

 

 

 

 

 

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

 *type=20 of battery to be used : lithium, AA, AAA?

 color=20 of base? perhaps gunmetal grey?

 decision=20 of interchangeable covers for remote...fruit/vegetables this=20 season?

 *where=20 to place logo on remote

 

 

 

 

 

 

 

 

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

 

UID:=20 user-interface design

ID: look=20 and feel design

Both=20 will be constructing model from clay

ME:=20 product evaluation

------=_NextPart_000_002C_01C51437.ED42C520--