| Previous Lecture | lect22 | Next Lecture |
lect22, Tue 05/19
Tuesday Lecture:
Today:
- Reminder about lab05
- Assign lab06
- Discuss lab07
- Reminder about lab08 (2nd iteration demo)
- Add to LEADERSHIP.md file
- Breakout Groups:
- Standup
- Add lab05 and lab06 work (Deploy Instructions) as an issue on Kanban board, and assign it.
- Work as team sees fit.
| Week | Monday | Tuesday | Wednesday | Thursday | Friday |
|---|---|---|---|---|---|
| 7 | 5/11 Retro 2 | 5/12 Sprint Planning | 5/14: Storybook | ||
| 8 | 5/18 Assign lab05 (ops) | 5/19 Assign Storybook / Linting (lab06) | 5/20 Assign Testing (lab07) | 5/21 Demos (lab08) | |
| 9 | No class (Memorial Day) | 5/26 Retro 3 Sprint Planning lab05 due Start lab09 (Ops review) |
5/28 | ||
| 10 | 6/01 Ops review due (lab09) | 6/02 | 6/04 | ||
| Finals | 6/10 5pm final presentations | 6/11 3:30pm final presentations |
MAKE GOOD USE OF YOUR TIME TOGETHER
Real world teams have 40 hours a week during which they can meet/work.
You all have 200 minutes each week. That’s all. 3⅓ hours. 91% less time.
It’s great to see:
- folks sharing their screen, discussing things energetically.
- folks demoing features to one another
- folks reviewing PRs
It is concerning to see:
- No one sharing their screen
- No one talking
Some things to keep in mind if you find you are at a loss:
- If you need to work in pairs/trios, we have extra break out rooms we can put you in.
- It you have PRs that haven’t been code reviewed, consider reviewing them as a team
- review the code
- review the features (i.e. run the code on QA)