Stories and advice for dev leaders, written by dev leaders. How to scale your team, which metrics to use, how to grow your career… even how to explain software development to your CEO (hint: very carefully 😉 )
Scrum velocity or team velocity is a measurement of development capacity. We’re looking at good, bad, and ugly uses of scrum team velocity.
Metrics alone do not improve dev teams. For continuous improvement, engineering orgs need visibility, context and workflow automation.
We start by recapping what cycle time is in the context of software delivery then take you through tactics so you can reduce cycle time.
Engineering productivity helps you with measuring the efficiency of your team’s engineering process. But which metrics should you track?
By tracking Git analytics, you can obtain accurate insights from your project and improve your team’s output. Learn how in this post.
How to reduce cyclomatic complexity? In this post, you’ll learn not only that, but also what is this metric and why you should reduce it.
Git statistics might be valuable to improve your project’s health. In this post, learn about the most important ones and how to track them.
What is branch coverage? That’s the question we’ll answer today. You’ll learn what this metric is all about and how it can help you.
LinearB and Clubhouse integrate to create the future of software project delivery for dev teams. Discover how we’re fixing project management for Dev Teams.
Code duplication makes software less maintainable and reduces our ability to iterate fast. Learn what duplication is and how to prevent it.