Organizational Pattern: Don't Interrupt An Interrupt
February 25th, 2010
(From Organizational Patterns of Agile Software Development )
It’s important to balance a desire that SOMEONE ALWAYS MAKES PROGRESS (4.1.20) with the thrashing that can accompany short-term priority calls. One worker will inevitably be blocked on you—you can’t do both things at once. Complete, omniscient foresight and scheduling are unreasonable to expect.
Therefore:
If a developer is already working in “interrupt mode” on a critical issue, don’t put that work aside until it is complete or until that issue itself becomes hopelessly tangled.
blog comments powered by Disqus
