Throwing more people at an engineering productivity problem is rarely the right solution. In this blog post, we discuss five typical causes of slowness and present practical ways for your team to maintain productivity.| www.swarmia.com
Today, having Continuous Integration is table stakes. Yet, CI pipelines are a common cause for developer frustration. And that’s why in this blog post, we walk through the five properties that make for a great CI experience.| www.swarmia.com
Interruptions — anything that yanks a developer out of that elusive “flow” state — can appear out of nowhere. When you make your processes interruption-aware, your team can focus on what they do best: building great products.| www.swarmia.com
If your daily stand-ups feel like a waste of time, they probably are. Here’s what’s wrong with most stand-ups — and what you can do about it.| www.swarmia.com
Eight great reasons why you should write small pull requests and tips on how to do it in practice.| www.swarmia.com
Retrospectives using only subjective data easily lead to skewed insights and actions. One solution is to add a "present hard data" step to your retrospectives.| www.swarmia.com
Learn why the most successful teams use code reviews, how to adopt them with your team, and what 16 best practices we recommend.| www.swarmia.com