# SGCs
**BEEing my best self** 💁


---

## Important to Jack
### Stop
- Obsessing about project completion
- Rejecting ideas before trying them
- Long stand ups
- Reiterating self / others ad nauseum

### Go
- Prioritising listening and patience
- Planning - making time to design and agree steps before
- Mind map of user flow and file architecture (Miro?) for README
- Compliments as well as criticisms
- More balance in pair programming
- Bring joyful energy into future teams
- User manual feedback

### Continue
- Using project board & Miro
- Big picture perspective - optimism and reflection
- Open mindedness to others' ways of thinking
- Great planning
- Clear, distinct issues
- Building cool things
- Jumping into rooms/checking in and **asking questions**
- Being honest and flexible with each other :+1:
- More GIFs, pics and demo time than writing on slides
- Relaxed environment but still productive
- Self-learning midfully

---

## Rollover from weeks 1-7
### Stop
- [ ] Copy and paste

### Go
- [ ] Review Estimates -> Actual
- [ ] Encourage opportunities to fail
- [ ] Simple CSS asap, e.g. basic styling based on HTML template
- [ ] Maybe 3min-ish group movement
- [ ] Maybe having set in breaks?
- [ ] Also reminding each other to drink water and not look at the screen 20/20/20
- [ ] COVID19 project (work on something together outside course)
- [ ] More tools we learn about e.g. debug module and CI

### Continue
- [ ] Celebrating victories

---

## WK1

### 1a Stop
- [x] Obsessing about project completion
- [x] Rushing & solo programming

### 1b Go
- [x] Planning - making time to design and agree steps before starting to code
- [x] Let's agree what constitutes an issue and our process for raising and resolving them, including the role of labels
- [x] **Prioritising listening and patience**
- [x] Swap every 1h30 incl 5 mins for group reflection & getting up to speed
- [x] Commenting code
- [x] Compliments as well as criticisms
- [x] 15 mins before lunch to assess progress and level of support

### 1c Continue
- [x] Using project board
- [x] **Open mindedness to others' ways of thinking**
- [x] **Being mindful of interrupting (chewing gum method and sociocracy fingers)**
- [x] Thoughtfully reviewing pull requests

---

## WK2

### 2a Stop
- [x] Jumping in when others want to talk
- [x] **Reiterating self / others ad nauseum**
- [x] Rejecting ideas before trying them
- [x] Long stand ups
- [x] Don't get detailed - if required set a separate 'ceremony'

### 2b Go
- [x] **Try Jitsi for video conferencing**
- [x] Make sure everyone gets a chance to be heard (incl volume)
- [x] Breathe before responding
- [ ] **Encourage opportunities to fail**
- [x] More balance in pair programming
- [x] **More commits at every relevant point**
- [x] Scrum master keeps us on time

### 2c Continue
- [x] Great planning
- [x] Clear, distinct issues
- [x] Hangouts - talking one at time
- [x] Building cool things
- [x] **Big picture perspective - optimism and reflection**
- [x] Considering remote needs
- [x] Swapping pairs
- [x] Using Live Share mindfully (not coding when someone else is driving)
- [x] **Regular stand ups**
- [x] Complimenting each other and other teams

---

## WK3
### 3a Stop
- [x] Planning and getting started look a long time - work on shortening it?
- [x] There could be tools for this e.g. James' whiteboard, also
- [x] Jack: losing sight of the big picture

### 3b Go
- [x] **We should start using prettier as a team, and before every commit. There's also a setting so it runs every time you save**
- [x] camelCase and BEM
- [x] Share responsibility for project board and issues
- [x] **Commit little and often like saving a Word doc + get co-authoring thing to work! (Gio)**
- [x] Let's all try to be mindful of whether we are changing something that was established in a previous commit. If we really need to do it, it might help to let the other team know
- [x] Relax about being scrum master :)
- [x] co-author commits - sharing is caring

### 3c Continue
- [x] Pair swapping often :)
- [x] Teaching each other things
- [x] Using live share and group hangouts - use more to ask questions?
- [x] respecting each other's learning objectives

---

## WK4
### 4a Stop

### 4b Go
- [ ] **Review Estimates -> Actual**
- [ ] **Simple CSS asap, e.g. basic styling based on HTML template**
- [x] Exploring other people’s approaches to solving a problem
- [ ] **End liveshare sessions for git merge**

### 4c Continue
- [x] Being awesome
- [x] Jumping into rooms/checking in and asking questions
- [x] using Miro and Jitsi as a group beforhand
- [x] **making clear issues to work within the parameters of**
- [x] Great code review

---

## WK5
### 5a Stop
- [x] Enabling Oli to steal our passwords

### 5b Go
- [x] Mind map of file architecture (Miro?)
- [ ] **Maybe having set in breaks?**
- [ ] **Also reminding each other to drink water and not look at the screen 20/20/20**
- [x] Fixing Oli being able to hack us
- [x] Bring this joyful energy into future teams (stay resilient)
- [ ] **Maybe 3min-ish group movement**
- [x] User manual feedback

### 5c Continue
- [x] Pokemon analogies
- [x] Being total angels
- [x] Being honest to each other :+1:
- [x] Being flexible (honesty is key!)
- [x] Asking each other questions
- [x] Being a fantastic scrum master
- [x] Listening to each other
- [x] Reluctantly learning Oli’s best practice
- [x] More GIFs, pics and demo time than writing on slides
- [x] Laughing/joking!! :100:
- [x] Relaxed environment but still productive

## WK6
### 6a Stop
- [ ] Copy and paste
- [x] Mobbing too long (soft stop)

### 6b Go
- [x] Killing those darlings ruthlessly :knife:
- [x] Group effort for readme
- [x] User flow first

## 6c Continue
- [x] Being chill af
- [x] Explaining code to the other pairs
- [x] Tactical mobbing
- [x] Excellent tag game
- [x] Planning :+1:
- [x] Being flexible
- [x] Reflective SGCs & thoughtful stand ups
- [x] Self-learning mindfully

## WK 7
### 7a Stop
- [x] Being so slow with learning new things like Express. I'd already got it by Sunday
- [x] Mapping promises you can't keep

### 7b Go
- [x] Making sure every group is building a running app next week
- [ ] COVID19 project (work on something together outside course)
- [ ] More tools we learn about e.g. debug module and CI
- [x] Make sure code reviews issues are done before going back to original plans

### 7c Continue
- [x] Being....... LEGENDARY
- [x] Scrum Master :handshake:
- [x] miro and readmes
- [x] Smooth as silk planning and execution
- [x] Focus on flow fom user perspective
- [x] Amazing knowledge sharing
- [x] Great debugging
- [ ] Celebrating victories

## WK8
### 8a Stop
### 8b Go
- [ ] Take breaks when debugging
- [ ] Modularising and abstracting from the start
- [ ] Try other solutions, besides tutorial (?)
- [ ] Use next week to re-energise

### 8c Continue
- [x] Swap pairs
- [ ] Being an awesome artist
- [ ] mobbing done right ( just enough and when neccessary )
- [x] Great comunication
- [x] Great clarity on issues