Everything you need to know about the experience of self-forming teams, and a workbook to help you get started.
We equate ‘speed’ to being busy, frantic meetings, and the flurry at the end of each sprint. But real ‘speed’ looks far different.
Over the last couple decades, our industry has seen a lot of changes in how we run engineering teams. Here’s a brief overview, and a look at what’s next.
2017 software developer productivity survey in the US and Great Britain.
Showcase the updates your team has made in a way your company can understand.
Surviving your first security audit—what to expect from start to finish and beyond.
Meaningful data cuts through office politics, and helps your team move faster.
When your engineering team talks about technical debt, listen like you would to the finance team talking about financial debt.
Use Impact to see who is carrying the load, understand how staffing changes are making a difference, and see if yesterday’s work matches today’s standup.
How to identify, respond, and prevent spikes in code churn (before it’s too late).
A concise guide to Code Churn (with examples)—and why this metric is important to effective software managers.
Adopting a priority-driven development strategy (we stopped worrying about Trello and just started using it).
Get Engineering Impact: the weekly newsletter for managers of software teams
Keep current with trends in engineering leadership, productivity, culture, and scaling development teams.