Difference between revisions of "CSPS Digital Academy/CSPS Digital Accelerator/Master Schedule"
Jump to navigation
Jump to search
| Line 304: | Line 304: | ||
|- | |- | ||
|Monday | |Monday | ||
| − | + | | colspan="2" |'''''Note the holidays:''' Family Day (ON, BC, AB, SK, NB)'' | |
| − | + | ||
| − | + | ''Islander Day (PE)'' | |
| − | + | ||
| + | ''Louis Riel Day (MB)'' | ||
| + | |||
| + | ''Heritage Day (NS)'' | ||
| + | | | ||
| + | | | ||
|- | |- | ||
|Tuesday | |Tuesday | ||
| − | + | | | |
| − | + | |By Design: How to Use Visuals and Narratives to Build Better Decks (C250) | |
| − | + | | | |
| − | + | |Product team only | |
|- | |- | ||
|Wednesday | |Wednesday | ||
| − | + | | | |
| − | + | |By Design: How to Use Visuals and Narratives to Build Better Decks (C250) | |
| − | + | | | |
| − | + | |Product team only | |
|- | |- | ||
|Thursday | |Thursday | ||
| − | + | | | |
| − | + | |By Design: How to Use Visuals and Narratives to Build Better Decks (C250) | |
| − | + | | | |
| − | + | |Product team only | |
|- | |- | ||
|Friday | |Friday | ||
| − | + | | | |
| − | + | |'''''Note the holiday:''' Heritage Day (YK)'' | |
| − | + | | | |
| − | + | | | |
|} | |} | ||
'''Teams will also make time for:''' | '''Teams will also make time for:''' | ||
Revision as of 16:22, 18 November 2021
CSPS Digital Accelerator Master Schedule (DRAFT)
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:
- 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:
- 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:
- User research (about 3 hours) - Product team required, executives optional
- User synthesis (about 2 hours) - Product team required, executives optional
- 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:
- Team work to improve prototype (about 3 hours) - Product team only (required)
- 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 | ||
| Wednesday | By Design: How to Use Visuals and Narratives to Build Better Decks (C250) | Product team only | ||
| Thursday | By Design: How to Use Visuals and Narratives to Build Better Decks (C250) | Product team only | ||
| Friday | Note the holiday: Heritage Day (YK) | |||
Teams will also make time for:
- Prototyping (about 5 hours) - Product team only (required)
- 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:
- Demo day pitch review (about 2 hours) - Product team and executives required
- Prototyping (about 5 hours) - Product team only (required)
- 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:
- Demo day pitch review (about 2 hours) - Product team and executives required
- Prototyping (about 5 hours) - Product team only (required)
- 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:
- Prototyping (about 2.5 hours) - Product team only (required)
- Demo day pitch review (about 2 hours) - Product team and executives required
- 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 |
