Sprint 2, Day 1

After the fantastic 1st blog post from Russ, I’m going to lower the standards a bit!

Russ being the boss (and proving that he doesn’t look like himself in photos). He’s pointing at the thing Hanna & Farnaz were not meant to work on in the afternoon!

Key stuff we did / learned today:

Roles for sprint 2:

- Scrum Master = Russ

- Blogger = Hanna

- Equally Important Team Players = Farnaz & Kriss.

Agenda for stand-up (posted on Slack by Russ):

- Check-ins: give the food that reflects your state.

- One thing you have learnt since last meeting

- One thing you want to work on this sprint

- Possible blockers

Then:

- Decide on tickets; Split tickets

- Choose the one task to mob

- Assign pair tasks; Assign pairs

- Separate for mob research

How the stand-up went:

- Russ brought a magic frog — whoever holds the frog speaks!

- Meeting went well except Farnaz was stuck in commuting hell (trespasser on line…)

Feedback from Sophie (Makers coach):

Good stuff:

- Mood check-ins

- Rotating roles

- Fitting in own work e.g. stop at 4:30pm for process workshop

- The magic frog!

- Looking at Trello board in meeting

Stuff to improve:

- Too many items on Trello board “In progress” column

- Hesitating at estimating ticket sizes — just guess, refine later

What we did — morning shift:

Kriss & Hanna read up on Rails. Russ & Farnaz tried to fix Travis issue.

Attended a Q&A lead by Katerina.

Then split into pairs:

- Russ & Kriss sorted deployment issues (Travis / Heroku)

- Farnaz & Hanna did user authentication. Also, Farnaz got help from Katerina on testing, Hanna asked Sophie to clarify user requirements.

What we did — afternoon shift:

Caught up after lunch, then split up into pairs again. BUT being a bit of a fool, I forgot which task which pair were working on, so led my pair to work on the same damn thing as the other pair… Oops. Apparently it was fixed in the end, will find out in tomorrow’s stand-up.

Summary

Good stuff:

- Stand-up meeting

- Pairing

- Got stuff working in the end

- Forgiving when someone screws up…

Room for improvement:

- Being 100% sure who is working on what (make it idiot-proof!)

- Co-authoring git commits…

Notes / Technical resources:

- From Russ: walkthrough we used for generating sign up via devise in Sprint 1: https://medium.com/@mchisti/creating-simple-users-in-rails-with-devise-gem-tutorial-cd91d2ef36d5