---
# System prepended metadata

title: Sprint Retro

---

# Sprint Retro

## Stop 


### Personal

- Razi: Using the wrong tool for the job because it's more comfortable to use that tool
- Liz: Recording videos ad-hoc
- Liss: Hyperfocusing on small-scale stuff
- Gene: Holding on to projects, considering projects to be "unfinished" instead of prototypes
- Kellyn: 
- R0an: Sometimes "on-rails" walkthroughs are difficult to follow for novelty-seeking adhd type
- Cam: just diving into coding things without specifying what exactly I'm trying to change

### Group

- Applying too much time pressure during walkthroughs 
- Putting walkthroughs "on rails"
- Ignoring Chat


## Continue

Personal
- Gene: Scoping! Being explicit and paring down the number of things comitted to
- Liss: Scope, asking for feedback and direction was helpful
- Aro: Asking for/receiving a summary of what is going to happen and what the end goals will be and what will be needed before we begin has been helpful


Group
- Prompt Engineering: Slowing down to make sure everyone got through was really helpful for the class
- Prompt Engineering: Planned out classes are helpful
- Prompt Engineering: Pre-work, and pre-readings are helpful
- Prompt Engineering: Engagement questions during lecture
- Prompt Engineering: Poll for questions / misunderstandings


## Start

Personal

- Razi: 
- Liz: Record videos in batches
- Liss: Focus on the big picture, so you can do the right thing
- Gene: Focus on the up-to-date thing, leave prototypes behind
- Kellyn: Find a focus, define personal values
- Roan: Push code to github, publish on medium and other platforms for discovery, publish work! Hit the post button!
- Cam: Spend 60% of the time understanding and making a plan
- Cam: Use pomodoros
- Cam: Describe commits better!
- Liss: Pomodoros too

Group

- Always push code to github by the end of any mob programming session
- On Walkthroughs: Do larger chunks with more time, rather than small chunks, small time, add more customization moments
- On Walkthroughs, coordinate with the coders beforehand and get them to familiarize themselves with the content so they can assist the non-coders
- Check chat more often