Projects/Promo/Booth and Marketing Sprint 2009/howto: Difference between revisions

From KDE TechBase
mNo edit summary
 
(2 intermediate revisions by the same user not shown)
Line 10: Line 10:
*will room be open on Monday?
*will room be open on Monday?


=Friday=
==Friday==
===09:00===
===09:00===


Line 23: Line 23:
*Will ask for feedback on meeting. Use note paper.
*Will ask for feedback on meeting. Use note paper.
*Monday finalizing stuff, meeting room will be open.
*Monday finalizing stuff, meeting room will be open.
*Fregl will fill in everyone on social stuff friday and saturday night


Now I will write down email addresses from everyone for later reference.
Now I will write down email addresses from everyone for later reference.
Line 42: Line 43:
*start first teams
*start first teams


===14:00-14:30===
===14:00-15:00===
*lunch
*lunch


Line 51: Line 52:
*dinner, end of day
*dinner, end of day


=Saturday=
==Saturday==
===10:00===
===10:00===
*start
*start
Line 58: Line 59:
*break.
*break.


===14:00-14:30===
===14:00-15:00===
*lunch
*lunch


Line 67: Line 68:
*dinner, end of day
*dinner, end of day


=Sunday=
==Sunday==
===10:00===
===10:00===
*start
*start
Line 74: Line 75:
*break.
*break.


===14:00-14:30===
===14:00-15:00===
*lunch
*lunch



Latest revision as of 19:02, 18 October 2009

How to do the meeting. This is my personal brainstorm, please ignore.

Preparation

  • pen and paper for each
  • coffee/thee/cookies for breaks

Open questions

  • more/less/other breaks?
  • is lunch/dinner time OK?
  • will room be open on Monday?

Friday

09:00

Welcome. laptop lids closed plz. Goal: get work done. Lots of work, so tight schedule and good planning:

  • We have to work in teams (too many ppl). Each centered around a topic, with a team leader who keeps progress. Use Google docs (better ideas?).
  • Then create deliverables, time estimate and list of participants for each topic.
  • We take a break while scheduling the topics
  • Then teams start
  • Lunch at 14:00 (30 min) dinner at 1900.
  • Tomorrow start at 10 so we have time for fun AND sleep. But again work until 1900. Sunday same but after dinner back here for wrapup.
  • wrapup: presentation of results from each team (1-2 min/topic MAX). Team leaders share notes with person writing dot story.
  • Will ask for feedback on meeting. Use note paper.
  • Monday finalizing stuff, meeting room will be open.
  • Fregl will fill in everyone on social stuff friday and saturday night

Now I will write down email addresses from everyone for later reference.

09:20

  • Brainstorm on topics. I put down list from wiki & everyone adds.
  • For each topic, we pick team leader. Try to even things, not too many topics.
  • Team leader fires up Google docs, creates document for topic.

09:40

  • For each topic we create list of deliverables and estimate time needed. Noted in google doc by team leader.
  • Everyone tells what topics they want to attend. Team leaders add this to google docs.
  • Is also noted down by ???? for scheduling.

10:30-11:00

  • break. Scheduling by ????

11:00

  • start first teams

14:00-15:00

  • lunch

18:00-19:00

  • time for blogging & wrapping up for the day

19:00-20:30

  • dinner, end of day

Saturday

10:00

  • start

11:30-12:00

  • break.

14:00-15:00

  • lunch

18:00-19:00

  • time for blogging & wrapping up for the day

19:00-xx:xx

  • dinner, end of day

Sunday

10:00

  • start

11:30-12:00

  • break.

14:00-15:00

  • lunch

18:00-19:00

  • time for blogging & wrapping up for the day

19:00-20:30

  • dinner

20:30

  • Topic presentations
  • Wrapup. Please feedback on meeting.