Difference between revisions of "CSPS Digital Academy/CSPS Digital Accelerator/Master Schedule"
Jump to navigation
Jump to search
m (updated schedule) |
|||
(32 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
[[FR:Académie_du_numérique/Accélérateur_du_numérique_EFPC/Calendrier_principal]] | [[FR:Académie_du_numérique/Accélérateur_du_numérique_EFPC/Calendrier_principal]] | ||
− | = CSPS Digital Accelerator | + | = CSPS Digital Accelerator - Full Schedule = |
− | |||
− | |||
== Week 1 (Jan 10) == | == Week 1 (Jan 10) == | ||
{| class="wikitable" | {| class="wikitable" | ||
Line 12: | Line 10: | ||
|- | |- | ||
| rowspan="2" |Monday | | rowspan="2" |Monday | ||
− | | | + | |10:30 –11:30am EST |
|Welcome to the Accelerator | |Welcome to the Accelerator | ||
− | |1 | + | |1 hour |
|Product team required | |Product team required | ||
Executives required | Executives required | ||
|- | |- | ||
− | | | + | |1:30 - 3pm EST |
|Introduction to Miro | |Introduction to Miro | ||
− | |1 | + | |1.5 hours |
|Product team required | |Product team required | ||
− | Executives | + | Executives recommended |
|- | |- | ||
| rowspan="2" |Tuesday | | rowspan="2" |Tuesday | ||
− | | | + | |1 - 4pm EST |
|Team Building | |Team Building | ||
− | | | + | |3 hours |
|Product team required | |Product team required | ||
Executives required | Executives required | ||
|- | |- | ||
− | | | + | |10:30am - 12pm EST |
|Human-Centered Design | |Human-Centered Design | ||
− | | | + | |1.5 hours |
− | | | + | |Product team required |
+ | |||
+ | Executives required | ||
|- | |- | ||
|Wednesday | |Wednesday | ||
− | | | + | |10am - 12pm EST |
|Problem framing 1: Exploring the Problem Space | |Problem framing 1: Exploring the Problem Space | ||
|2 hours | |2 hours | ||
|Product team required | |Product team required | ||
− | Executives | + | Executives recommended |
|- | |- | ||
|Thursday | |Thursday | ||
Line 49: | Line 49: | ||
! | ! | ||
|- | |- | ||
− | + | |Friday | |
− | | | + | |2 - 2:45pm EST |
|End of week check-in | |End of week check-in | ||
|45 minutes | |45 minutes | ||
|Product team required | |Product team required | ||
Executives required | Executives required | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|} | |} | ||
'''Teams will also make time for:''' | '''Teams will also make time for:''' | ||
Line 76: | Line 70: | ||
|- | |- | ||
|Monday | |Monday | ||
− | | | + | |10am - 12pm EST |
|Problem framing 2: Identifying users | |Problem framing 2: Identifying users | ||
|2 hours | |2 hours | ||
− | |Product team required | + | |Product team only (required) |
− | |||
|- | |- | ||
|Tuesday | |Tuesday | ||
− | | | + | |10am - 12pm EST |
|Doing user research | |Doing user research | ||
|2 hours | |2 hours | ||
Line 89: | Line 82: | ||
|- | |- | ||
|Wednesday | |Wednesday | ||
− | | | + | |3 - 4 pm EST |
− | |Leading with Agility | + | |Leading with Agility - stage setting |
− | | | + | |1 hour |
|Executives only (required) | |Executives only (required) | ||
|- | |- | ||
Line 100: | Line 93: | ||
! | ! | ||
|- | |- | ||
− | |Friday | + | | rowspan="2" |Friday |
− | | | + | |12 - 1pm EST |
+ | |Lunch and Learn - with Liz McKeown | ||
+ | |1 hour | ||
+ | |Product team optional | ||
+ | Executives optional | ||
+ | |- | ||
+ | |2 - 2:45pm EST | ||
|End of week check-in | |End of week check-in | ||
|45 minutes | |45 minutes | ||
Line 121: | Line 120: | ||
|- | |- | ||
|Monday | |Monday | ||
− | | | + | |1 - 3pm EST |
|Agile 101 | |Agile 101 | ||
|2 hours | |2 hours | ||
|Product team required | |Product team required | ||
− | Executives | + | Executives recommended |
|- | |- | ||
|Tuesday | |Tuesday | ||
Line 134: | Line 133: | ||
|- | |- | ||
|Wednesday | |Wednesday | ||
− | | | + | |1 - 3pm EST |
|Problem framing 3: Problem scope and output | |Problem framing 3: Problem scope and output | ||
|2 hours | |2 hours | ||
Line 146: | Line 145: | ||
|- | |- | ||
|Friday | |Friday | ||
− | | | + | |1 - 2:30pm EST |
|Show and tell | |Show and tell | ||
− | | | + | |1.5 hours |
|Product team required | |Product team required | ||
Executives required | Executives required | ||
Line 155: | Line 154: | ||
# User research (about 3 hours) - Product team required, executives optional | # User research (about 3 hours) - Product team required, executives optional | ||
− | # User synthesis (about 2 hours) - Product team | + | # User synthesis (about 2 hours) - Product team required, executives optional |
# Feedback for product teams (about 1 hour) - Product team and executives required | # Feedback for product teams (about 1 hour) - Product team and executives required | ||
+ | # Team retrospective (about 30 min - 1 hour) - Product team only | ||
== Week 4 (Jan 31) == | == Week 4 (Jan 31) == | ||
Line 168: | Line 168: | ||
|- | |- | ||
|Monday | |Monday | ||
− | | | + | |10am - 12pm EST |
− | |Generating | + | |Generating how-might-we ideas |
|2 hours | |2 hours | ||
|Product team only (required) | |Product team only (required) | ||
Line 179: | Line 179: | ||
! | ! | ||
|- | |- | ||
− | | rowspan="2" |Wednesday | + | | rowspan="2" |Wednesday |
− | | | + | |10am - 12pm EST |
− | | | + | |Scoping and selecting ideas |
|2 hours | |2 hours | ||
+ | |Product team only (required) | ||
+ | |- | ||
+ | |1 - 4:30pm EST | ||
+ | |Leading with Agility workshop | ||
+ | |3.5 hours | ||
|Executives only (required) | |Executives only (required) | ||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
|Thursday | |Thursday | ||
− | | | + | |10am - 12pm EST |
− | | | + | |Turning an idea into a concept |
|2 hours | |2 hours | ||
|Product team only (required) | |Product team only (required) | ||
|- | |- | ||
|Friday | |Friday | ||
− | | | + | |2 - 2:45pm EST |
|End of week check-in | |End of week check-in | ||
|45 minutes | |45 minutes | ||
Line 203: | Line 203: | ||
Executives required | Executives required | ||
|} | |} | ||
− | |||
− | |||
− | |||
== Week 5 (Feb 7) == | == Week 5 (Feb 7) == | ||
Line 217: | Line 214: | ||
|- | |- | ||
|Monday | |Monday | ||
− | | | + | |1 - 3pm EST |
|Prototyping tools and techniques | |Prototyping tools and techniques | ||
− | | | + | |2 hours |
|Product team only (required) | |Product team only (required) | ||
|- | |- | ||
Line 235: | Line 232: | ||
|- | |- | ||
|Thursday | |Thursday | ||
− | | | + | |1 - 3pm EST |
|Lo-fi prototype output | |Lo-fi prototype output | ||
|2 hours | |2 hours | ||
Line 241: | Line 238: | ||
|- | |- | ||
|Friday | |Friday | ||
− | | | + | |1 - 2:30pm EST |
|Show and Tell | |Show and Tell | ||
− | | | + | |1.5 hours |
|Product team required | |Product team required | ||
Executives required | Executives required | ||
Line 249: | Line 246: | ||
'''Teams will also make time for:''' | '''Teams will also make time for:''' | ||
− | # | + | # Team retrospective (about 30 min - 1 hour) - Product team only |
== Week 6 (Feb 14) == | == Week 6 (Feb 14) == | ||
Line 261: | Line 258: | ||
|- | |- | ||
|Monday | |Monday | ||
− | + | |1 - 3pm EST | |
− | + | |Product management | |
− | + | |2 hours | |
− | + | |Product team required (only) | |
|- | |- | ||
|Tuesday | |Tuesday | ||
Line 273: | Line 270: | ||
|- | |- | ||
| rowspan="2" |Wednesday | | rowspan="2" |Wednesday | ||
− | | | + | |1 - 3pm EST |
|Backlogs and Roadmaps | |Backlogs and Roadmaps | ||
|2 hours | |2 hours | ||
− | |Product team required | + | |Product team required |
− | |||
|- | |- | ||
− | | | + | |3 - 4:30pm EST |
− | | | + | |Executive meetup |
− | | | + | |1.5 hours |
− | |Executives only | + | |Executives only |
|- | |- | ||
|Thursday | |Thursday | ||
− | + | |1 - 2:30pm EST | |
− | + | |Post-design retrospective | |
− | + | |1.5 hours | |
− | + | |Product team required (only) | |
|- | |- | ||
|Friday | |Friday | ||
− | + | |2 - 2:45pm EST | |
− | + | |End of week check-in | |
− | + | |45 min | |
− | + | |Product team required | |
+ | |||
+ | Executives required | ||
|} | |} | ||
'''Teams will also make time for:''' | '''Teams will also make time for:''' | ||
− | |||
# Team work to improve prototype (about 3 hours) - Product team only (required) | # Team work to improve prototype (about 3 hours) - Product team only (required) | ||
# User testing (about 5 hours) - Product team required, executives optional | # User testing (about 5 hours) - Product team required, executives optional | ||
Line 312: | Line 309: | ||
|- | |- | ||
|Monday | |Monday | ||
− | + | | colspan="4" |'''''Note the holidays:''' Family Day (ON, BC, AB, SK, NB)'' | |
− | + | ||
− | + | ''Islander Day (PE)'' | |
− | + | ||
+ | ''Louis Riel Day (MB)'' | ||
+ | |||
+ | ''Heritage Day (NS)'' | ||
|- | |- | ||
|Tuesday | |Tuesday | ||
− | + | |1 - 3pm EST | |
− | + | |By Design (C250) | |
− | + | |2 hours | |
− | + | |Product team only (1-2 per team) | |
|- | |- | ||
|Wednesday | |Wednesday | ||
− | + | |1 - 3pm EST | |
− | + | |By Design (C250) | |
− | + | |2 hours | |
− | + | |Product team only (1-2 per team) | |
|- | |- | ||
|Thursday | |Thursday | ||
− | + | |1 - 3pm EST | |
− | + | |By Design (C250) | |
− | + | |2 hours | |
− | + | |Product team only (1-2 per team) | |
+ | |- | ||
+ | | rowspan="2" |Friday | ||
+ | | colspan="4" |'''''Note the holiday:''' Heritage Day (YK)'' | ||
|- | |- | ||
− | | | + | |2 - 2:45pm EST |
− | + | |End of week check-in | |
− | + | |45 min | |
− | + | |Product team required | |
− | + | Executives required | |
|} | |} | ||
'''Teams will also make time for:''' | '''Teams will also make time for:''' | ||
Line 368: | Line 371: | ||
|- | |- | ||
|Wednesday | |Wednesday | ||
− | | | + | |1 - 4:30pm EST |
− | |Leading with Agility | + | |Leading with Agility workshop |
− | | | + | |3.5 hours |
|Executives only (required) | |Executives only (required) | ||
|- | |- | ||
Line 380: | Line 383: | ||
|- | |- | ||
|Friday | |Friday | ||
− | | | + | |1 - 2:30pm EST |
|Show and tell | |Show and tell | ||
− | | | + | |1.5 hours |
|Product team required | |Product team required | ||
Executives required | Executives required | ||
Line 390: | Line 393: | ||
# Demo day pitch review (about 2 hours) - Product team and executives required | # Demo day pitch review (about 2 hours) - Product team and executives required | ||
# Prototyping (about 5 hours) - Product team only (required) | # Prototyping (about 5 hours) - Product team only (required) | ||
− | # User testing and synthesis (about 3 hours) - Product team | + | # User testing and synthesis (about 3 hours) - Product team required, executives optional |
+ | # Team retrospective (about 30 min - 1 hour) - Product team only | ||
== Week 9 (Mar 7) == | == Week 9 (Mar 7) == | ||
Line 403: | Line 407: | ||
|Monday | |Monday | ||
| | | | ||
− | | | + | | |
− | | | + | | |
− | | | + | | |
|- | |- | ||
|Tuesday | |Tuesday | ||
− | ! | + | !1:30 - 2:30pm EST |
− | ! | + | !Demo presentation coaching |
− | ! | + | !1 hour |
− | + | |Product team required | |
|- | |- | ||
|Wednesday | |Wednesday | ||
Line 426: | Line 430: | ||
|- | |- | ||
|Friday | |Friday | ||
− | | | + | |1 - 4pm EST |
− | |Show and tell round 1 ( | + | |Show and tell round 1 (4 teams) |
|3 hours | |3 hours | ||
|Product team required | |Product team required | ||
Line 449: | Line 453: | ||
|Monday | |Monday | ||
| | | | ||
− | | | + | | |
− | | | + | | |
− | | | + | | |
|- | |- | ||
|Tuesday | |Tuesday | ||
Line 461: | Line 465: | ||
|Wednesday | |Wednesday | ||
| | | | ||
− | | | + | | |
− | | | + | | |
− | | | + | | |
− | |||
|- | |- | ||
|Thursday | |Thursday | ||
Line 473: | Line 476: | ||
|- | |- | ||
|Friday | |Friday | ||
− | | | + | |1 - 4pm EST |
− | |Show and tell round 2 ( | + | |Show and tell round 2 (4 different teams) |
|3 hours | |3 hours | ||
|Product team required | |Product team required | ||
Line 483: | Line 486: | ||
# Prototyping (about 2.5 hours) - Product team only (required) | # Prototyping (about 2.5 hours) - Product team only (required) | ||
# Demo day pitch review (about 2 hours) - Product team and executives required | # Demo day pitch review (about 2 hours) - Product team and executives required | ||
− | # User testing and synthesis (about 2 hours) - Product team | + | # User testing and synthesis (about 2 hours) - Product team required, executives optional |
== Week 11 - Final week! (Mar 21) == | == Week 11 - Final week! (Mar 21) == | ||
Line 507: | Line 510: | ||
|- | |- | ||
|Wednesday | |Wednesday | ||
− | | | + | |1pm – 3:30pm EST |
− | |Attend Demo | + | |Attend Demo Day! |
− | | | + | |2.5 hours |
|Product team required | |Product team required | ||
Executives required | Executives required | ||
|- | |- | ||
|Thursday | |Thursday | ||
− | | | + | |1 - 3pm EST |
|Post-accelerator retro | |Post-accelerator retro | ||
|2 hours | |2 hours |
Latest revision as of 15:10, 1 March 2022
CSPS Digital Accelerator - Full Schedule
Week 1 (Jan 10)
Day of the Week | Time | Topic | Length | Participants |
---|---|---|---|---|
Monday | 10:30 –11:30am EST | Welcome to the Accelerator | 1 hour | Product team required
Executives required |
1:30 - 3pm EST | Introduction to Miro | 1.5 hours | Product team required
Executives recommended | |
Tuesday | 1 - 4pm EST | Team Building | 3 hours | Product team required
Executives required |
10:30am - 12pm EST | Human-Centered Design | 1.5 hours | Product team required
Executives required | |
Wednesday | 10am - 12pm EST | Problem framing 1: Exploring the Problem Space | 2 hours | Product team required
Executives recommended |
Thursday | ||||
Friday | 2 - 2:45pm EST | End of week check-in | 45 minutes | Product team required
Executives required |
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 | 10am - 12pm EST | Problem framing 2: Identifying users | 2 hours | Product team only (required) |
Tuesday | 10am - 12pm EST | Doing user research | 2 hours | Product team only (required) |
Wednesday | 3 - 4 pm EST | Leading with Agility - stage setting | 1 hour | Executives only (required) |
Thursday | ||||
Friday | 12 - 1pm EST | Lunch and Learn - with Liz McKeown | 1 hour | Product team optional
Executives optional |
2 - 2:45pm EST | 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 | 1 - 3pm EST | Agile 101 | 2 hours | Product team required
Executives recommended |
Tuesday | ||||
Wednesday | 1 - 3pm EST | Problem framing 3: Problem scope and output | 2 hours | Product team only (required) |
Thursday | ||||
Friday | 1 - 2:30pm EST | Show and tell | 1.5 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
- Team retrospective (about 30 min - 1 hour) - Product team only
Week 4 (Jan 31)
Day of the Week | Time | Topic | Length | Participants |
---|---|---|---|---|
Monday | 10am - 12pm EST | Generating how-might-we ideas | 2 hours | Product team only (required) |
Tuesday | ||||
Wednesday | 10am - 12pm EST | Scoping and selecting ideas | 2 hours | Product team only (required) |
1 - 4:30pm EST | Leading with Agility workshop | 3.5 hours | Executives only (required) | |
Thursday | 10am - 12pm EST | Turning an idea into a concept | 2 hours | Product team only (required) |
Friday | 2 - 2:45pm EST | 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 | 1 - 3pm EST | Prototyping tools and techniques | 2 hours | Product team only (required) |
Tuesday | ||||
Wednesday | ||||
Thursday | 1 - 3pm EST | Lo-fi prototype output | 2 hours | Product team only (required) |
Friday | 1 - 2:30pm EST | Show and Tell | 1.5 hours | Product team required
Executives required |
Teams will also make time for:
- Team retrospective (about 30 min - 1 hour) - Product team only
Week 6 (Feb 14)
Day of the Week | Time | Topic | Length | Participants |
---|---|---|---|---|
Monday | 1 - 3pm EST | Product management | 2 hours | Product team required (only) |
Tuesday | ||||
Wednesday | 1 - 3pm EST | Backlogs and Roadmaps | 2 hours | Product team required |
3 - 4:30pm EST | Executive meetup | 1.5 hours | Executives only | |
Thursday | 1 - 2:30pm EST | Post-design retrospective | 1.5 hours | Product team required (only) |
Friday | 2 - 2:45pm EST | End of week check-in | 45 min | Product team required
Executives required |
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 | 1 - 3pm EST | By Design (C250) | 2 hours | Product team only (1-2 per team) |
Wednesday | 1 - 3pm EST | By Design (C250) | 2 hours | Product team only (1-2 per team) |
Thursday | 1 - 3pm EST | By Design (C250) | 2 hours | Product team only (1-2 per team) |
Friday | Note the holiday: Heritage Day (YK) | |||
2 - 2:45pm EST | End of week check-in | 45 min | Product team required
Executives required |
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 | 1 - 4:30pm EST | Leading with Agility workshop | 3.5 hours | Executives only (required) |
Thursday | ||||
Friday | 1 - 2:30pm EST | Show and tell | 1.5 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
- Team retrospective (about 30 min - 1 hour) - Product team only
Week 9 (Mar 7)
Day of the Week | Time | Topic | Length | Participants |
---|---|---|---|---|
Monday | ||||
Tuesday | 1:30 - 2:30pm EST | Demo presentation coaching | 1 hour | Product team required |
Wednesday | ||||
Thursday | ||||
Friday | 1 - 4pm EST | Show and tell round 1 (4 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 | ||||
Tuesday | ||||
Wednesday | ||||
Thursday | ||||
Friday | 1 - 4pm EST | Show and tell round 2 (4 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 | 1pm – 3:30pm EST | Attend Demo Day! | 2.5 hours | Product team required
Executives required |
Thursday | 1 - 3pm EST | Post-accelerator retro | 2 hours | Product team required
Executives required |
Friday |