Jump to: navigation, search

Difference between revisions of "StoryBoard/Brussels Sprint"

 
(5 intermediate revisions by 2 users not shown)
Line 21: Line 21:
  
 
* Cody Somerville
 
* Cody Somerville
 +
**arrives Wednesday evening, departs Monday morning
 
* Colette Alexander
 
* Colette Alexander
 
**arrives Wed 10am, Departs Sat 9 AM
 
**arrives Wed 10am, Departs Sat 9 AM
Line 72: Line 73:
 
| 10:45 || COFFEE || {caffeine}  ||   
 
| 10:45 || COFFEE || {caffeine}  ||   
 
|-
 
|-
| 11:00 || Product: key metrics || List of key measurements (will fold into plan for executing measurements  || Colette
+
| 11:00 || Product: key metrics || List of key measurements (will fold into plan for executing measurements) || Colette
 
|-
 
|-
 
| 11:15|| Product: process/how we work || List of places to accomplish: task tracking, daily work communication, meeting communication, status updates (urgent/regular), storing documents || Colette
 
| 11:15|| Product: process/how we work || List of places to accomplish: task tracking, daily work communication, meeting communication, status updates (urgent/regular), storing documents || Colette
Line 88: Line 89:
 
| 12:45 || Lunch  
 
| 12:45 || Lunch  
 
|-
 
|-
| 13:00 || Example || Example || Example
+
| 13:00 || Main technical needs || Based on current state: list all work to be done, categorized by workstreams  ||  
 
|-
 
|-
| 13:15 || Example || Example || Example
+
| 13:15 || prioritize main code needs for rest of schedule, recognizing task interdependencies || prioritized list to tackle/work on ||
 
|-
 
|-
| 13:30 || Example || Example || Example
+
| 13:30 || Priority 1: (probably the data model) || ? ||
 
|-
 
|-
 
| 13:45 || Example || Example || Example
 
| 13:45 || Example || Example || Example
Line 140: Line 141:
 
| 09:15 || Example || Example || Example
 
| 09:15 || Example || Example || Example
 
|-
 
|-
| 09:30 || Team Values  ||  || Colette
+
| 09:30 ||   ||  ||
 
|-
 
|-
 
| 09:45 || Example || Example || Example  
 
| 09:45 || Example || Example || Example  
Line 150: Line 151:
 
| 10:30 || Example || Example || Example
 
| 10:30 || Example || Example || Example
 
|-
 
|-
| 10:45 || COFFEE || {caffeine} || Example
+
| 10:45 || COFFEE || {caffeine} ||
 
|-
 
|-
 
| 11:00 || Example || Example || Example
 
| 11:00 || Example || Example || Example
Line 209: Line 210:
 
|-
 
|-
 
|}
 
|}
 +
 +
 +
== Outcome ==
 +
* https://etherpad.openstack.org/p/StoryboardMeetup
 +
* https://etherpad.openstack.org/p/StoryboardAuth

Latest revision as of 13:42, 9 February 2014

When

  • Sprint will happen for 2 days: Thursday and Friday January 30-31 (just before FOSDEM).
  • We should start at 9:00am and end at 6:00pm (office space is available from 8:30am to 6:30pm).

Where

  • We'll meet in a meeting room sponsored by the OpenStack Foundation in the Multiburo office rental space
  • Address: Louise Tower (Floor 12), Avenue Louise 149, Brussels
  • Tel: +32(0)2 535 75 11
  • Public transportation: Tram 93/94 just in front of office space (Defacqz station), Tram 81/83 and Bus 54 at 150m (Bailli station), Metro at 900m (Louise station)
  • There will be coffee in the room (a Nespresso machine should sit there all day).
  • As a backup location, in case the Multiburo deal falls out, HP offered to host us in their Diegem offices near Brussels Airport.

Practical information

  • Most people are expected to book hotels near the meeting space in this area: http://goo.gl/maps/UD5nc
  • We'll use public transportation in Brussels, so consider buying a rechargeable MOBIB Basic card with 10+2 journeys on it (should be 17 €), or a disposable JUMP 10 journeys magnetic card (13.50 €)
  • FOSDEM happens 10:30am-7pm on Saturday, 9am-6pm on Sunday. No registration necessary. Lots of people. Messy buildings. No marketing talks. No sponsored talks. You love it or hate it.
  • Friday starting at 6pm (and finishing laaate) there is the famous FOSDEM Beer Event. Warning quote: "Unlike some other beers, Belgian beer is not just coloured water".

Attendees

(Please add your arrival/departure times)

  • Cody Somerville
    • arrives Wednesday evening, departs Monday morning
  • Colette Alexander
    • arrives Wed 10am, Departs Sat 9 AM
  • Ilya Shakhat
    • arrives Wed 4pm, departs Sun 10am
  • Jaromir Coufal
  • Jim Blair
  • Michael Krotscheck
  • Monty Taylor
  • Nikita Konovalov (visa pending)
    • arrives Wed afternoon, departs Mon morning
  • Ruslan Kamaldinov (ruhe on irc) (visa pending)
    • arrives Wed afternoon, departs Mon morning
  • Sergey Lukjanov (visa pending)
    • arrives Wed afternoon, departs Mon morning
  • Thierry Carrez
    • Arrives Wed 5pm, Departs Sunday 5pm (train)

Content

The goal of the sprint is to get to know each other and discuss/define the fundamentals of Storyboard, so that we can then proceed on delivering a first version dogfoodable by the infra team (and/or more) with continuous delivery from that point on.

Proposed workgroups

  • Features: high-level concepts, customers: start from ttx's needs (launchpad equivalent) and see if we can do to serve more people's need
    • Thierry, Colette, Sergey
  • Code: technical details, base architecture, technology choices, UI choices: make hard calls on what we should use, start coding it
    • Michael, Ilya, Nikita
  • Infrastructure: CI/CD, integrate with openstack infra to achieve CI/CD in record time
    • Jim, Ruslan

Draft Schedule

  • Thursday
Time Subject Outputs? Facilitator
09:00 Intros/Coffee {caffeine}/{friendship}
09:15 "
09:30 Team Values Colette
09:45 " team values statement
10:00 Product: major problems/solutions Colette
10:15 " Success statements
10:30 Product: customer segments prioritized list of customer segments Colette
10:45 COFFEE {caffeine}
11:00 Product: key metrics List of key measurements (will fold into plan for executing measurements) Colette
11:15 Product: process/how we work List of places to accomplish: task tracking, daily work communication, meeting communication, status updates (urgent/regular), storing documents Colette
11:30 " Schedule + practices artifacts for each iteration?
11:45 Overview: current state of StoryBoard Currently possible user stories Mike
12:00 Lunch
12:15 Lunch
12:30 Lunch
12:45 Lunch
13:00 Main technical needs Based on current state: list all work to be done, categorized by workstreams
13:15 prioritize main code needs for rest of schedule, recognizing task interdependencies prioritized list to tackle/work on
13:30 Priority 1: (probably the data model)  ?
13:45 Example Example Example
14:00 Example Example Example
14:15 Example Example Example
14:30 Example Example Example
14:45 Example Example Example
15:00 Example Example Example
15:15 Example Example Example
15:30 Example Example Example
15:45 Example Example Example
16:00 Example Example Example
16:15 Example Example Example
16:30 Example Example Example
16:45 Example Example Example
17:00 Example Example Example
17:15 Example Example Example
17:30 Example Example Example
17:45 Example Example Example
  • Friday
Time Subject Outputs? Facilitator
09:00 Coffee {caffeine}
09:15 Example Example Example
09:30
09:45 Example Example Example
10:00 Example Example Example
10:15 Example Example Example
10:30 Example Example Example
10:45 COFFEE {caffeine}
11:00 Example Example Example
11:15 Example Example Example
11:30 Example Example Example
11:45 Example Example Example
12:00 Lunch
12:15 Lunch
12:30 Lunch
12:45 Lunch
13:00 Example Example Example
13:15 Example Example Example
13:30 Example Example Example
13:45 Example Example Example
14:00 Example Example Example
14:15 Example Example Example
14:30 Example Example Example
14:45 Example Example Example
15:00 Example Example Example
15:15 Example Example Example
15:30 Example Example Example
15:45 Example Example Example
16:00 Example Example Example
16:15 Example Example Example
16:30 Example Example Example
16:45 Example Example Example
17:00 Example Example Example
17:15 Example Example Example
17:30 Example Example Example
17:45 Example Example Example


Outcome