Team Troubleshooting
  • Home
  • About me
  • My favorite links
  • Start here

How to spot the five reasons why your code review process is slowing you down

4 years ago 1 min read
> When code review is laborious and takes hours or days, developers avoid working in small batches and instead batch up many changes. This in turn leads to a downward spiral where reviewers
Read Now Read Later
Matias Lespiau
By: Matias Lespiau

These four questions will tell you where to start troubleshooting your team's velocity.

4 years ago 1 min read
As a VP of Engineering, I work with more than 30 software engineering teams. Over time, I developed a heuristic to help me identify velocity issues quickly. The four questions: Is there high
Read Now Read Later
Matias Lespiau
By: Matias Lespiau

A minimalist framework to think about quality problems

4 years ago 2 min read
Every quality problem is either a problem in the quality bar or a problem in enforcing the quality bar. To consistently deliver quality work, we need a system that helps us achieve that.
Read Now Read Later
Matias Lespiau
By: Matias Lespiau

Struggling with velocity and need to improve it quickly? Instead of analyzing what's taking time, try this instead.

4 years ago 1 min read
> Work-in-progress rears its ugly head when you know that your team is drowning in work because you never put your foot down to any incoming requests. - @Dominica DeGrandis My go-to tool
Read Now Read Later
Matias Lespiau
By: Matias Lespiau

3 ways software development leaders can make room for investing in quality.

4 years ago 2 min read
> "The tragedy is that as soon as you frame internal quality as tradable, you've lost." - Martin Fowler. Tradable quality hypothesis How many times have you heard or
Read Now Read Later
Matias Lespiau
By: Matias Lespiau
Newer Posts
Page 7 of 8
Older Posts
Powered by Ghost
Team Troubleshooting