Team Troubleshooting
  • Home
  • About me
  • My favorite links

The reason why most attempts to increase velocity fail (and how to fix it)

a year ago 5 min read
Improving a development team's velocity is no easy task for a leader. In 2015, I led a team that was taking a long time to build new features, but it was tough to
Read Now Read Later
Matias Lespiau
By: Matias Lespiau

2 things successful teams do to spend less time doing reviews and increase their velocity (but you have to do both to reap the value)

a year ago 2 min read
There is a vicious cycle in software development between doing large changes and slow feedback loops. When the feedback loop is slow, people will batch more changes together, and when the batch is
Read Now Read Later
Matias Lespiau
By: Matias Lespiau

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

a year 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 procrastinate
Read Now Read Later
Matias Lespiau
By: Matias Lespiau

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

a year 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

a year 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
Newer Posts
Page 2 of 3
Older Posts
Powered by Ghost
Team Troubleshooting