Received: from [139.222.1.2] by messenger (ArGoSoft Mail Server Freeware, Version 1.8 (1.8.6.4)); Fri, 28 Jan 2005 11:36:31 +0000 Message-ID: <001901c5052d$cea56460$0201de8b@participant1> From: "participant1" To: References: <01c5052c$Blat.v2.2.2$496bef7c@messenger> Subject: Re: Please summarise the last meeting Date: Fri, 28 Jan 2005 11:37:53 -0000 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0016_01C5052D.CDB89360" 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_0016_01C5052D.CDB89360 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 = department head, Please find below the meeting summary as requested. Jen. =20 [ABSTRACT] Write one paragraph of coherent text to summarize the = meeting as a whole from your role's perspective. =20 The meeting functioned as an introduction to the team and the = project. After an initial brief of the project, team members introduced = themselves and their roles. The project finances were outlined, and then = initial ideas for the product were briefly discussed. =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. =20 No decisions were made as this was an introductory meeting. The initial ideas which were suggested by the marketing expert were = agreed by the group - that we should go for a sleek look which fits with = other products marketed by this company. This may involve having few or = no buttons on the remote as many of these are rarely used anyway. =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 The main problem was the time constraint, combined with the fact that = I had only just read through the presentation once and didn't fully = understand it. =20 =20 =20 =20 =20 =20 =20 [ACTIONS] Name the next steps that each member will take until the = next meeting. Write fragmented notes. Actions to be taken: ID: the working design UID: the technical functions design ME: the user requirements specification =20 ------=_NextPart_000_0016_01C5052D.CDB89360 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 department head,
Please find below the meeting summary = as=20 requested.
Jen.

 

[ABSTRACT]   Write one paragraph = of=20 coherent text to summarize the meeting as a whole from your = role=92s=20 perspective.

 

 The=20 meeting functioned as an introduction to the team and the project. = After an=20 initial brief of the project, team members introduced themselves and = their=20 roles. The project finances were outlined, and then initial ideas for = the=20 product were briefly discussed.

 

 

 

 

 

 

 

 

[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 decisions were made as this was an introductory = meeting.

The=20 initial ideas which were suggested by the marketing expert were = agreed by=20 the group - that we should go for a sleek look which fits with other = products=20 marketed by this company. This may involve having few or no buttons on = the=20 remote as many of these are rarely used anyway.

 

 

 

 

 

 

 

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

 

 The=20 main problem was the time constraint, combined with the fact that I = had only=20 just read through the presentation once and didn't fully understand=20 it.

 

 

 

 

 

 

 

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

 

Actions=20 to be taken:

ID: the=20 working design

UID: the=20 technical functions design

ME: the=20 user requirements specification =20

------=_NextPart_000_0016_01C5052D.CDB89360--