![]() ![]() It covers four common patterns for teams: In all aspects of software design, delivery, and operation, we start with the team. Therefore, an organization should never assign work to individuals only to teams. We consider the team to be the smallest entity of delivery within the organization. The main thesis of the book is to engage in “team-first thinking”: The core concepts of the book are cognitive load, Conway’s law and the “Inverse Conway Maneuver” which translates to: if you need a system with X components then you should have X teams.įrom Jacob Kaplan-Moss’s blog which goes in more detail: “Team Topologies: Organizing Business and Technology Teams for Fast Flow” by Matthew Skelton and Manuel Paisįor later stage scaling teams and how to think about it. I recommend supplementing this book with Swarmia. Should you use these metrics and draw immediate conclusion if you team is amazing or sucks? Metrics without the context are a huge danger, but can trigger valuable investigations and gaining more understanding. Time to restore service: The time it takes to restore service in production after an incident.Change failure rate: The share of incidents, rollbacks, and failures out of all deployments.Change lead time: The time it takes to get committed code to run in production.Deployment frequency: How often a software team pushes changes to production.Introducing DORA metrics - read more here. Can you measure good engineering? The main point the book is trying to make is that you can avoid sacrificing quality and focusing on the right things you can increase velocity of your organization. “Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations” by Nicole Forsgren, Jez Humble and Gene Kimĭata-driven approach to best practices in engineering. I think it applies to marketing and other “scalable” roles, but that’s not my place to comment. ![]() ![]() Why your designers should not have to jump through ridiculous hoops to get their best work done and why your product people should be empowered to take risky but calculated decisions. Why it’s worth paying the top dollar to get the best possible engineers. My recommendation is to take the ideas here with a giant grain of salt, it’s likely not something that applies to your seed-stage B2B SaaS startup where cash is in limited supply and you have commission based roles.īecause I think it helps to think about how you should treat product, engineering and design roles. The book is full of anecdotes of the CEO and interviews from the various employees that make the case for the above. Make sure that they know they own their shit, they are expected to take risks and will get fired if they don’t get results on time.Remove redundant bureaucracy because you hired the “best” and they hate stupid rules that don’t bring any value.Then you pay top of the market salaries to those who are left and recruit the “best” people.First you aggressively fire anyone that is not a “top performer”.The core idea is that an exceptional company increases talent density and establishes a culture of freedom and responsibility.Īllow me to put it less diplomatically in steps: It’s about the (in)famous Netflix culture. “No Rules Rules: Netflix and the Culture of Reinvention” by Erin Meyer and Reed Hastings ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |