Culture
Why We Transitioned From Sprints to Basecamp’s "Shape Up" Methodology 8 minutes read.
"It wasn’t as simple as picking Shape Up off the shelf and running with it. We had many radical candor conversations about what was working, what wasn’t, what we’ve learned, and what’s ideal for us as a team. Remember, not every process is for every team — you need to understand what does and doesn’t work best for your specific team. What are your team’s strengths? What do you need to get better at? Reflection every few weeks is key to growth." -- Shape Up is an excellent book with many interesting concepts worth knowing, even if you don't plan to use it. I like how Cory Torres Bishop shares their process to experiment with it, while focusing on the value they seek to get as a team and deliver to their customers.
Read it later via
Instapaper.
Share
it via
Twitter
or
email.
The Structure and Process Fallacy 3 minutes read.
"No organisation structure can compensate for a poor Developer Experience." -- Nick Tune is right to say that org structure won't save you. The odds of a big re-org or launching a new process helping you are getting lower if it comes top-down with little context and expectations setting between the different groups.
Read it later via
Instapaper.
Share
it via
Twitter
or
email.
The Paradox of Production Alerts (Slides) 9 minutes read.
This deck by Charity Majors should be required reading to anyone building software. Share it with your teammates and discuss what's worth adopting (e.g., SLO-based alerts versus symptom-based alerts) to improve the quality of your systems and products.
Read it later via
Instapaper.
Share
it via
Twitter
or
email.