Skip to content

Instantly share code, notes, and snippets.

@booty
Last active December 1, 2017 18:50
Show Gist options
  • Save booty/3d26b94cb689d6296efe6c57c3f082de to your computer and use it in GitHub Desktop.
Save booty/3d26b94cb689d6296efe6c57c3f082de to your computer and use it in GitHub Desktop.
JARVIS Retro Dec 1 2017.txt
What Went Well This Week
========================
- Healthy point total despite missing 1 people-day, plus have stories ready to ship on Monday
- Local deploys should be faster - always nice to help the whole team be more productive
- Owe a shout-out to Diego for Nitro Search sortable scopes; made the Project Score story much easier
- Going story-by-story in retro avoided "overlooked story syndrome"
- John appreciated detailed TB stories
- TB stories shipped in reasonable time; hasn't always been the case
- Github's Code Ownership feature has been useful & appreciated
- Bryan is a true hero of testing things - helped Garett and John
What Didn't Go Well This Week?
==============================
- Juggling/synchronizing Puppet/TB/Nitro releases still no fun (help on the way w/ Docker!)
- No have teh Dockerz
- Still unclear how to test some TB features/code paths in demo environments (was not an issue this week thanks to Bryan)
- While Ben was not always immediately available for TB questions, we were able to work around it
- For "Tim" questions (e.g. wording, etc) it would be good to have all questions answered at story definition time
- Not a problem yet, but we have questions about implementing designs from the UX team
- Team is relatively comfortable with front end work, but unfamiliar with current structure of Nitro front-end assets/organization
- Will want to make sure we work closely with UX group to make sure we're doing things "the right away"
- (We're excited though!)
- Still looking for the right balance when responding to other teams' (frequently-very-helpful and appreciated!) PR comments
- 99% of the time this goes well, don't want to overstate problem
Kaizen
======
At the outset of the UX projects, let's pester (Diego? Carlos? Bruno? Nova in general?) for some
hand-holding, so we can start out on the right architectural foot when creating the front-end code.
Essentially, just want to make sure we're making the right choices with regards to:
1. Should we create a new component, or no?
2. Where assets should go
3. Things we haven't thought of
David
=====
Role on team: 4.9
Department/Company: 4.9
???: 4.9
Garett
======
Role on team: 4.9
Department/Company: 4.9
Great British Bake-Off: 4.0 (suggestion from John: Yakitake Japan!)
John
====
Role on team: 4.4
Company: 5.0
Department: 5.0
Dirk Gently's Holistic Detective Agency: 5.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment