[co2015tickets] Re: Group Presentation

  • From: "Chris" <chris@xxxxxxxxxxxxxxx>
  • To: <co2015tickets@xxxxxxxxxxxxx>
  • Date: Sat, 9 May 2009 14:18:39 +0100

I can do the reengineering and technology, but won't be able to work on the
slides as I'm writing my management assignment over the weekend for Monday.

Chris

-----Original Message-----
From: co2015tickets-bounce@xxxxxxxxxxxxx
[mailto:co2015tickets-bounce@xxxxxxxxxxxxx] On Behalf Of Brazel, D.
Sent: 08 May 2009 23:28
To: co2015tickets@xxxxxxxxxxxxx
Subject: [co2015tickets] Group Presentation

Hi all,

All that is now left to do on the group project is the presentation at 9:30
on Wednesday (13/05). It is important that everyone is there and says
something, as stated in Reiko's email.

With regards to the structure and order of who says what of our
presentation, my thoughts are as below. Please let me what you think of
this:

Intro (1 person):
          What will be covered in presentation
          How delighted and excited we were by the project and its concept

Re-engineering (Pair A):
          Problems with existing code
          Benefits of Re-engineering
          Highlight as big decision made by group

Technology, infrastructure and architecture of our system (Pair A):
          Reasons for choosing and benefits of
          Any slight criticisms of

What our system is great at (emphasis on!) (Pair B):
          Improvements to functionality that existed on old system
          Why our implementation of new requirements kicks ass!
          Why we added any functionality that wasn't a specified
requirement, and why it is really great that we did

The weaknesses of our system (Pair B):
          Requirements not met
          Non-prefect implementation of any features
          General interface negatives

Our vision for the future if we were to continue project ourselves (1
Person):
          Obviously complete reimplementation of lost functionality
          Improvements we would envisage making and great ideas we've
thought of

Conclusion (1 person):
          Emphasise one or two reasons why our system is brilliant and why
he should 'buy' it
          Say what a joy it has been working together and on such an
exciting and intriguing project, and that we only wish we could have had
more time to take it further. (Said without sounding like a creep!)


With regards as to who says what, the key is to be able to talk
knowledgeably and enthusiastically therefore if the is a part that anyone
particularly wants to speak about then say so by the end of tomorrow.  If no
one is that bothered then I will just divide up the presentation myself.

I think then that everyone should prepare powerpoint slides and what they
are going to say on their section. The slides should then be emailed to me
early evening Monday so that I can put them together into one presentation
which looks good and is consistent; that is unless anyone else want to do
this, otherwise then I am happy to.

This deadline for finishing the slides would then allow us to meet on
Tuesday with a largely finished sideshow. I would suggest we meet at about
2:00pm to rehearse and clarify what we are going to say. I think this is
vital as preparation is crucial for a good presentation in my experience.
Does anybody have an issue with this meeting time.

Lastly, when we've finished practicing I reckon we should go to the Red
Fearn for a pint to celebrate the hard work we've put in throughout the
project and celebrate that after all this time it's nearly finished!

What is everyone's suggestions and comments on all of this?

Regards,
David.

Other related posts:

  1. Home
  2. co2015tickets
  3. Archive
  4. 05-2009