Measuring interruptions: How to keep your team in the ‘zone’
alexweinstein.substack.com
This article was originally posted as a guest post on Geekwire; it is republished here for the readers of this blog. When you look at productive output from a software development team, there’s one factor that almost always predicts problems. You can have top talent; an outstanding idea; great agile process. And yet, if you don’t treat interruptions as a significant source of danger, the progress will be slow and painful.
Measuring interruptions: How to keep your team in the ‘zone’
Measuring interruptions: How to keep your…
Measuring interruptions: How to keep your team in the ‘zone’
This article was originally posted as a guest post on Geekwire; it is republished here for the readers of this blog. When you look at productive output from a software development team, there’s one factor that almost always predicts problems. You can have top talent; an outstanding idea; great agile process. And yet, if you don’t treat interruptions as a significant source of danger, the progress will be slow and painful.