Slides<\/a><\/p>\n I find that the retrospective is often a practice that agile teams skip out on, and I find this unfortunate because the retro really beautifully exemplifies the spirit of Agile since it involves reflecting on what you’ve done as a team and making decisions on how to iterate on your process. <\/p>\n Carbon Five follows a simple process for running retrospectives which is outlined in this blog post:<\/p>\n Carbon Five recipe for running simple Agile retrospectives<\/a><\/p>\n If you are a remote team, Carbon Five builds a tool called Stickies.io<\/a> which is great for retrospectives. It’s free to use.<\/p>\n When a team is big you need to make sure you’re hiring engineers who are able to work with people of other disciplines and maintain positive relationships with other teams.<\/p>\n It’s not enough for a candidate to be talented at programming if people in other teams struggle to work with them. <\/p>\n Slack – Three Unconventional Interview Questions<\/a><\/p>\n The best way to make sure you’re onboarding successfully is to have the steps somewhat documented and always be iterating on these steps.<\/p>\n On Amazon’s meeting culture: https:\/\/www.inc.com\/justin-bariso\/jeff-bezos-knows-how-to-run-a-meeting-here-are-his-three-simple-rules.html<\/a> <\/p>\n Back To Work Podcast – Invitation to a Blame Party<\/p>\n A great episode that touches on how to have effective meetings<\/p>\n http:\/\/5by5.tv\/b2w\/115<\/a><\/p>\n Sample design doc that describes extracting OAuth request serving into its own application: https:\/\/paper.dropbox.com\/doc\/OAuth-Migration-design-doc–ARjgA~twgejUiCLpRB3SkNvKAg-uetMvZEZKeZLKYbtcIznY<\/a><\/p>\n Managing Humans by Rands (Michael Lopp)<\/a><\/p>\n How Korean culture may have contributed to Korean Air’s abysmal safety record in the ’90s and how they since turned it around<\/a><\/p>\n Etsy’s thoughts on blameless postmortems<\/a><\/p>\n Google’s book on SRE<\/a><\/p>\n Summary of Amazon’s S3 outage<\/a><\/p>\n Diverse Teams Feel Less Comfortable – And That’s Why They Perform Better<\/a><\/p>\n Employee Onboarding at Startups is Broken – Here’s How to Fix It<\/a><\/p>\n How the Other Half Works: an Adventure in the Low Status of Software Engineers<\/a><\/p>\n Evidence-Based Scheduling<\/a><\/p>\n *Managing Humans, Third Edition* by Michael Lopp<\/a><\/p>\nRetrospectives<\/h2>\n
Interviewing for behavioral traits<\/h2>\n
Behavioral traits to look for<\/h3>\n
\n
\n
\n
\n
Tips and tricks for successful onboarding<\/h2>\n
Before the first day<\/h3>\n
\n
First Day<\/h3>\n
\n
First week<\/h3>\n
\n
\n
Meeting Culture<\/h2>\n
Design Documents<\/h2>\n
Postmortems and cultural effects on performance<\/h2>\n
SRE techniques<\/h2>\n
Miscellaneous<\/h2>\n
Books<\/h2>\n