Sometimes organizations form Special Teams assigned to tackle technical bugs or other challenges. Frequently, these special teams make the very problem that they’re meant to solve, worse.
Three quick reasons, among many:
– other teams no longer feel responsible for dealing with the problem: defects; security; …
– queues build up in front of the special team, often making it difficult to release
– special teams have an incentive to keep their problems around forever to justify their continued existance
Scrum by Example – Stuck Waiting for Other Teams
- Agile Organization Design – Jeff Anderson
Mark Levison has been helping Scrum teams and organizations with Agile, Scrum and Kanban style approaches since 2001. From certified scrum master training to custom Agile courses, he has helped well over 8,000 individuals, earning him respect and top rated reviews as one of the pioneers within the industry, as well as a raft of certifications from the ScrumAlliance. Mark has been a speaker at various Agile Conferences for more than 20 years, and is a published Scrum author with eBooks as well as articles on InfoQ.com, ScrumAlliance.org an AgileAlliance.org.
*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