- No Consistent Delivery of day to day student experience
- No Consistent Delivery of Advisee/Advisor Relations
- Instructor Stress / Burnout
- Non equitable dispersement of responsibilities amongst staff
WTL == Weekly Technical Lead
PL == Phase Admin / Cultural Lead
-
Phase Admin / Cultural Lead
- 1 Instructor
- 3 week stint
- MAX 2 Phases in a row, then rotate into WTL or Staff Developer
- MAX 1 PDG/week
- Phase Administrator
- Sets Phase Culture
- Daily Stand-up Leader
- Daily Office hours M-TH (replacing advisor role)
- Typically filled by SR Instructor
- Works with WTL to fill in any gaps
- Provides consistent student interactions over the course of a phase
- Intended to be a low stress overseer of the phase
- Ultimate responsibility for phase. If WTL is out will have to pick up the slack
- Responsible for delivering Velocity tracking data around entire phase on Friday of the week.
-
Weekly Technical Lead
- 1 Instructor
- 1 week stint
- Allows for plugin/plugout dynamic
- Delivers technical content for the week ( Lectures / Breakouts / Code Review )
- MAX 1 PDG/week where Phase Admin has scheduling priority.
- JR Instructor ideally to fill this role during onboarding, perhaps in conjunction with a more SR Instructor
- Only week 1 in P3
- Responsible for delivering any relevant Velocity tracking data on Friday of the week.
-
Staff Developer
- When 6+ staff in rotation
- && When not PL || WTL
- Can be PDG off site || Non-PDG on site
- Build out features for current projects
- Select from one of several ongoing projects
- Submit code for peer review
- Week 2 Friday of previous phase
- Assign Phase Leads for following phase
- Assign Weekly Technical Leads for following phase
- Phase 1
- Week 1
- Week 2
- Week 3
- Phase 2
- Week 1
- Week 2
- Week 3
- Phase 3
- Week 1
- Calculate PDG allotment for phase
- Signup for PDG in waves where applicable
- Fridays are Lead free days. Get them started in the morning then checkout
- Remove Solo Optional Wednesdays - Replace with Solo Optional After Hours