Received: from [139.222.1.4] by messenger (ArGoSoft Mail Server Freeware, Version 1.8 (1.8.6.4)); Fri, 4 Feb 2005 11:44:31 +0000 Message-ID: <003901c50aaf$1513f070$0401de8b@participant3> From: "participant3" To: References: <01c50aad$Blat.v2.2.2$48df0ec8@messenger> Subject: Re: Please summarise the last meeting Date: Fri, 4 Feb 2005 11:45:52 -0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0036_01C50AAF.14226480" 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_0036_01C50AAF.14226480 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 eDear Sir, here is the summary you requested. Regards, Iain. (User Interface Design) ----- Original Message -----=20 From: HeadOfDept@ami=20 To: participant3@ami=20 Sent: Friday, February 04, 2005 11:33 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. A 'kick off' meeting was held at 11 a.m. on 4th February 2005. The = meeting aimed to start a new project with the aim of designing a new = television remote control. After some introductions, an outline of the = new project and the design process involved was given by the project = manager. General ideas were discussed, including the problems often = encountered with existing remote controls. [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. No firm decisions made as this was more a brainstorming session. We = have suggested that we will try to address some of the problems with = existing TV remotes to improve on their design. =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. No specific problems. =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. Rose (Project Manager): Alima (Industrial Design): working design. Iain (User interface): technical functions design. Jesse (Marketing): User requirements. ------=_NextPart_000_0036_01C50AAF.14226480 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
Dear Sir,
here is the summary you = requested.
 
Regards,
Iain.
(User Interface Design)
----- Original Message -----
From:=20 HeadOfDept@ami
Sent: Friday, February 04, 2005 = 11:33=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.

 

A=20 'kick off' meeting was held at 11 a.m. on 4th February 2005. The = meeting aimed=20 to start a new project with the aim of designing a new television = remote=20 control. After some introductions, an outline of the new project and = the=20 design process involved was given by the project manager. General = ideas were=20 discussed, including the problems often encountered with existing = remote=20 controls.

 

 

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

 No=20 firm decisions made as this was more a brainstorming session. We have=20 suggested that we will try to address some of the problems with = existing TV=20 remotes to improve on their design.

  

 

 

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

 No=20 specific problems.

 

 

 

 

 

 

 

 

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

 

Rose = (Project=20 Manager):

Alima = (Industrial=20 Design): working design.

Iain (User = interface): technical functions design.

Jesse = (Marketing):=20 User requirements.

 

 

------=_NextPart_000_0036_01C50AAF.14226480--