Difference between revisions of "CSPS Digital Academy/CSPS Digital Accelerator/Master Schedule"

From wiki
Jump to navigation Jump to search
Line 318: Line 318:
 
|By Design: How to Use Visuals and Narratives to Build Better Decks (C250)
 
|By Design: How to Use Visuals and Narratives to Build Better Decks (C250)
 
|
 
|
|Product team only
+
|Product team only (1-2 per team)
 
|-
 
|-
 
|Wednesday
 
|Wednesday
Line 324: Line 324:
 
|By Design: How to Use Visuals and Narratives to Build Better Decks (C250)
 
|By Design: How to Use Visuals and Narratives to Build Better Decks (C250)
 
|
 
|
|Product team only
+
|Product team only (1-2 per team)
 
|-
 
|-
 
|Thursday
 
|Thursday
Line 330: Line 330:
 
|By Design: How to Use Visuals and Narratives to Build Better Decks (C250)
 
|By Design: How to Use Visuals and Narratives to Build Better Decks (C250)
 
|
 
|
|Product team only
+
|Product team only (1-2 per team)
 
|-
 
|-
 
|Friday
 
|Friday

Revision as of 15:26, 18 November 2021

CSPS Digital Accelerator Master Schedule (DRAFT)

CSPS Digital Accelerator.png











Week 1 (Jan 10)

Day of the Week Time Topic Length Participants
Monday Welcome to the Accelerator 1.5 hours Product team required

Executives required

Introduction to Miro 1 hour Product team required

Executives optional

Tuesday Team Building 2.5 hours Product team required

Executives required

Human-Centered Design 3 hours
Wednesday Problem framing 1: Exploring the Problem Space 2 hours Product team required

Executives optional

Thursday
Friday End of week check-in 45 minutes Product team required

Executives required

Lunch and Learn - with Liz McKeown 1 hour Product team optional

Executives optional

Teams will also make time for:

  1. Team work (about 2 hours) - Product team only (required)

Week 2 (Jan 17)

Day of the Week Time Topic Length Participants
Monday Problem framing 2: Identifying users 2 hours Product team only (required)
Tuesday Doing user research 2 hours Product team only (required)
Wednesday Leading with Agility - stage setting 1 hour Executives only (required)
Thursday
Friday End of week check-in 45 minutes Product team required

Executives required

Teams will also make time for:

  1. Team work (about 3 hours) - Product team only (required)

Week 3 (Jan 24)

Day of the Week Time Topic Length Participants
Monday Agile 101 2 hours Product team required

Executives optional

Tuesday
Wednesday Problem framing 3: Problem scope and output 2 hours Product team only (required)
Thursday
Friday Show and tell 2 hours Product team required

Executives required

Teams will also make time for:

  1. User research (about 3 hours) - Product team required, executives optional
  2. User synthesis (about 2 hours) - Product team required, executives optional
  3. Feedback for product teams (about 1 hour) - Product team and executives required

Week 4 (Jan 31)

Day of the Week Time Topic Length Participants
Monday Generating solution ideas / How-Might-We 2 hours Product team only (required)
Tuesday
Wednesday Leading with Agility workshop 3 hours Executives only (required)
Scoping solution ideas for prototyping 2 hours Product team only (required)
Thursday Selecting solution ideas 2 hours Product team only (required)
Friday End of week check-in 45 minutes Product team required

Executives required

Week 5 (Feb 7)

Day of the Week Time Topic Length Participants
Monday Prototyping tools and techniques 1 hour Product team only (required)
Tuesday
Wednesday
Thursday Lo-fi prototype output 2 hours Product team only (required)
Friday Show and Tell 2 hours Product team required

Executives required

Week 6 (Feb 14)

Day of the Week Time Topic Length Participants
Monday
Tuesday
Wednesday Backlogs and Roadmaps 2 hours Product team required\

Executives optional

Executive meetup 1.5 hours Executives only (optional)
Thursday
Friday

Teams will also make time for:

  1. Team work to improve prototype (about 3 hours) - Product team only (required)
  2. User testing (about 5 hours) - Product team required, executives optional

Week 7 (Feb 21)

Day of the Week Time Topic Length Participants
Monday Note the holidays: Family Day (ON, BC, AB, SK, NB)

Islander Day (PE)

Louis Riel Day (MB)

Heritage Day (NS)

Tuesday By Design: How to Use Visuals and Narratives to Build Better Decks (C250) Product team only (1-2 per team)
Wednesday By Design: How to Use Visuals and Narratives to Build Better Decks (C250) Product team only (1-2 per team)
Thursday By Design: How to Use Visuals and Narratives to Build Better Decks (C250) Product team only (1-2 per team)
Friday Note the holiday: Heritage Day (YK)

Teams will also make time for:

  1. Prototyping (about 5 hours) - Product team only (required)
  2. User testing and synthesis (about 3 hours) - Product team required, executives optional

Week 8 (Feb 28)

Day of the Week Time Topic Length Participants
Monday
Tuesday
Wednesday Leading with Agility workshop 3 hours Executives only (required)
Thursday
Friday Show and tell 2 hours Product team required

Executives required

Teams will also make time for:

  1. Demo day pitch review (about 2 hours) - Product team and executives required
  2. Prototyping (about 5 hours) - Product team only (required)
  3. User testing and synthesis (about 3 hours) - Product team required, executives optional

Week 9 (Mar 7)

Day of the Week Time Topic Length Participants
Monday Demo day pitch coaching 45 minutes per team Product team required
Tuesday
Wednesday
Thursday
Friday Show and tell round 1 (5 teams) 3 hours Product team required

Executives required

Teams will also make time for:

  1. Demo day pitch review (about 2 hours) - Product team and executives required
  2. Prototyping (about 5 hours) - Product team only (required)
  3. User testing and synthesis (about 3 hours) - Product team and executives required

Week 10 (Mar 14)

Day of the Week Time Topic Length Participants
Monday Demo day pitch coaching 30 minutes per team Product team required
Tuesday
Wednesday Demo day dry run 1 hour Product team required

Executives optional

Thursday
Friday Show and tell round 2 (5 different teams) 3 hours Product team required

Executives required

Teams will also make time for:

  1. Prototyping (about 2.5 hours) - Product team only (required)
  2. Demo day pitch review (about 2 hours) - Product team and executives required
  3. User testing and synthesis (about 2 hours) - Product team required, executives optional

Week 11 - Final week! (Mar 21)

Day of the Week Time Topic Length Participants
Monday
Tuesday
Wednesday Attend Demo day! 3 hours Product team required

Executives required

Thursday Post-accelerator retro 2 hours Product team required

Executives required

Friday