Team members get interrupted throughout their working day. Some of the interruptions are high value – e.g. a team member asking questions that helps the team stay in flow. Some are important, such as a production support issue, although we should understand their cost to see where to improve our system. In other cases, the interruptions are from outside the team and most of these interruptions should be blocked by the ScrumMaster or Product Owner, and redirected or saved for a better time.
Scrum By Example – Interruptions Hurt the Team
Scrum by Example – How to Handle Production Support Issues in Scrum
Resource Links:
- A Diary Study of Task Switching and Interruptions
- High Cost of Interruptions
- Impact of task switching and work interruptions on software development processes
- Interrupts: Just a Minute Never Is [PDF Warning]
- Managing Sprint Interruptions by Tracking Buffer Use
- Programmer Interrupted Key quote: A programmer is likely to get just one uninterrupted 2-hour session in a day
- Worker, Interrupted: The Cost of Task Switching
- What’s the cost of interrupting developers?
See Also:
*Thank you for visiting the World's Largest Opinionated Agile Reference Library. This content is created and the links are curated through the lens of Agile Pain Relief Consulting's view of what is effective in the practice of Scrum and Agile. We don't accept submissions and emails to that effect are marked as spam. Book listings may use affiliate links that could result in a small commission received by us if you purchase, but they do not affect the price at all. From experience, this won't amount to anything more than a cup of coffee in a year.« Back to Glossary Index
