Received: from [139.222.1.3] by messenger (ArGoSoft Mail Server Freeware, Version 1.8 (1.8.6.4)); Fri, 4 Feb 2005 11:41:56 +0000 Message-ID: <002501c50aae$a406e630$0301de8b@participant2> From: "participant2" To: References: <01c50aad$Blat.v2.2.2$48e3d37c@messenger> Subject: Re: Please summarise the last meeting Date: Fri, 4 Feb 2005 11:42:42 -0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0020_01C50AAE.A31B9BD0" 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_0020_01C50AAE.A31B9BD0 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 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. =20 In this first meeting we discussed project goals, aims, finances, and = the things to get done befroe next meeting. We also took some time to = become acquainted with the team members and the tools that we will be = using. To finish off the meeting we did some preliminary brainstorming = on what the main features of our product design should be, based on = previous personal experience with television remote controls. For the = next meeting I am to focus on the working design of the project, while = others tackle other issues. =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. project aims * selling price profit goals project scope production price aims key decision seems to be that we are looking for product with ease of = use, in a variety of contexts and ways. =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. Main issue - what do we mean by ease of use -what does that entail in this scenario?? * What is our product meant to do? =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. I will concentrate on working design,=20 Iain on tech design Jessie on user requirements ------=_NextPart_000_0020_01C50AAE.A31B9BD0 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 = 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.

 

 In=20 this first meeting we discussed project goals, aims, finances, and the = things=20 to get done befroe next meeting. We also took some time to become = acquainted=20 with the team members and the tools that we will be using. To finish = off the=20 meeting we did some preliminary brainstorming on what the main = features of our=20 product design should be, based on previous personal experience with=20 television remote controls. For the next meeting I am to focus on the = working=20 design of the project, while others tackle other = issues.

 

 

 

 

 

 

 

 

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

 project=20 aims *

selling=20 price

profit=20 goals

project=20 scope

production=20 price aims

 

key=20 decision seems to be that we are looking for product with ease of use, = in a=20 variety of contexts and ways.

 

 

 

 

 

 

 

 

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

 Main=20 issue - what do we mean by ease of use

   =20 -what does that entail in this scenario?? *

What=20 is our product meant to do?

 

 

 

 

 

 

 

 

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

 

I=20 will concentrate on working design,

Iain=20 on tech design

Jessie=20 on user requirements

------=_NextPart_000_0020_01C50AAE.A31B9BD0--