Received: from [139.222.1.2] by messenger (ArGoSoft Mail Server Freeware, Version 1.8 (1.8.6.4)); Wed, 19 Jan 2005 15:27:51 +0000 Message-ID: <007701c4fe3b$9d845ec0$0201de8b@participant1> From: "participant1" To: References: <01c4fe36$Blat.v2.2.2$b629baf6@messenger> Subject: Re: Please summarise the last meeting Date: Wed, 19 Jan 2005 15:29:05 -0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0074_01C4FE3B.9C714110" 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_0074_01C4FE3B.9C714110 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 2:54 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 This was our third meeting to date. The team feel comfortable with = eachother, and don't hesitate to mention if they are unhappy with a = particular point. The meeting was very usefull in clearing up all of the = ideas we'd had floating about. We made a lot of important decisions. =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)We will use a kinetic charger for our product 2) We will use the standard chip on the market - TA11835 3) We want to incorporate a standby function 4)The case material will be rubber 5)The buttons will be a combination of LCD and rubber according to the = design 6)We will use bright, funky designs for the casing 7)we will try to incorporate voice recognition software into our = design 8) the rubber buttons we will use will be anti Repetitive Strain = Injury =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. =20 we are worried about the costs involved with our design =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_0074_01C4FE3B.9C714110 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 2:54=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.

 

 

 This=20 was our third meeting to date. The team feel comfortable with = eachother, and=20 don't hesitate to mention if they are unhappy with a particular point. = The=20 meeting was very usefull in clearing up all of the ideas we'd had = floating=20 about. We made a lot of important decisions.

 

 

 

 

 

 

 

[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)We=20 will use a kinetic charger for our product

2)=20 We will use the standard chip on the market - TA11835

3)=20 We want to incorporate a standby function

4)The=20 case material will be rubber

5)The=20 buttons will be a combination of LCD and rubber according to the=20 design

6)We=20 will use bright, funky designs for the casing

7)we=20 will try to incorporate voice recognition software into our=20 design

8)=20 the rubber buttons we will use will be anti Repetitive Strain=20 Injury

 

 

 

 

 

 

 

 

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

 

 we=20 are worried about the costs involved with our design

 

 

 

 

 

 

 

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

------=_NextPart_000_0074_01C4FE3B.9C714110--