Previous Lecture | lect09 | Next Lecture |
lect09, Mon 04/20
Monday Section: First Retrospective
Homework
- Due Dates for H04 and H05 have been moved out (and corrected on Gradescope / course website)
- Makes room for new Assignment: A Feedback form for today’s retro.
- Please complete ASAP so that feedback is meaningful (as soon as possible after retro completed.)
- Would prefer to have all of these by midnight tonight.
- At the latest, before lecture tomorrow.
- Link is in Slack
lab00 update
- Extending ontime deadline for lab00 to Tuesday midnight
- “late” (with no penalty) to Thursday midnight.
- The deadline is more for you than for us.
- We are in no hurry to grade it.
- BUT, you need these skills/capabilities to get started
- And if there are problems, we need to debug as a class
- “Debug as a class” means that there are roles for
- the individual
- the team
- the course staff (TA Scott, and LAs Andrew, Bryan, Cole, Kristin, Victor)
- the instructor
- https://ucsb-cs48.github.io/s20/lab/lab00/
Today: Retrospective
- We’ll put you in breakout groups.
- When you are finished, just leave.
- No need to come back to main room, unless you have questions
- Staff will be dropping in to observe.
Deliverable
-
Add to your team’s repo, under
team
directoryteam/RETROS.md
-
Add a section:
# Retro 04/20/20 * Led by: name-goes-here * Present: name1, name2, ... , nameN * Absent: name1, name2, ... ## Action item * a goal: identify something the team wants to get better at * a change: identify one thing that the team will change about how it works together * a measurement: identify at least one way to measure whether the change helped the team acheive the goal, or move closer to it.
-
After the Retro
All Team members: Fill out survey (see Slack for link)
Retro leader: add Section to
team/RETROS.md
## Retro Assessment * A brief description of what retro outline or process you used. * A brief assessment of how it went. * What advice would you give to the next person leading a retro based on what you learned today?