Received: from [139.222.1.2] by messenger (ArGoSoft Mail Server Freeware, Version 1.8 (1.8.6.4)); Wed, 19 Jan 2005 12:50:48 +0000 Message-ID: <004301c4fe25$ace65dc0$0201de8b@participant1> From: "participant1" To: References: <01c4fe23$Blat.v2.2.2$da93f3ba@messenger> Subject: Re: Please summarise the last meeting Date: Wed, 19 Jan 2005 12:52:02 -0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0040_01C4FE25.AC0A55A0" 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_0040_01C4FE25.AC0A55A0 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 19, 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: o 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 This was our second meeting, where we tried to make as many decisions = as possible as to the design of our product. Each of the members of the group presented their individual findings = as a power point presentation, and there was general discussion at the = end of the sessions. =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. 1) The shape should be unique to us - shell design was mentioned 2) alarm to signify where the remote is if it gets lost 3) rechargable batteries, with a port that it can be placed in, to act = as the 'hub' 4) To aim our design at young proffesionals, trendy, fasionable 5) possibility of touch buttons 6) No programming function, just 'video plus' instead. =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. Design hasn't been agreed on yet =20 want to make the handset trendy, but not too small - repetetive = strain injury* =20 =20 [ACTIONS] Name the next steps that each member will take until the = next meeting. Write fragmented notes. UI designer will look further into the shape and buttons of our = control ID will look into touch buttons and rechargable battery packs Marketing will focus on insruction manual and looking into what people = expect from their control. ------=_NextPart_000_0040_01C4FE25.AC0A55A0 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 19, = 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:

 o

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

 

 This=20 was our second meeting, where we tried to make as many decisions as = possible=20 as to the design of our product.

Each=20 of the members of the group presented their individual findings as a = power=20 point presentation, and there was general discussion at the end of the = sessions.

 

 

 

 

 

 

 

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

 1)=20 The shape should be unique to us - shell design was = mentioned

 

2)=20 alarm to signify where the remote is if it gets lost

 

3)=20 rechargable batteries, with a port that it can be placed in, to act as = the=20 'hub'

 

4)=20 To aim our design at young proffesionals, trendy, = fasionable

 

5)=20 possibility of touch buttons

 

6)=20 No programming function, just 'video plus' instead.

 

 

 

  

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

 Design=20 hasn't been agreed on yet

 

 want=20 to make the handset trendy, but not too small - repetetive strain=20 injury*

 

 

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

 

UI=20 designer will look further into the shape and buttons of our=20 control

 

ID=20 will look into touch buttons and rechargable battery = packs

 

Marketing=20 will focus on insruction manual and looking into what people expect = from their=20 control.

------=_NextPart_000_0040_01C4FE25.AC0A55A0--