Scrum Buts - and how to remove them
summary
Lists ten common “ScrumButs” and fixes: third-party vendors claiming agile refuse planning or docs so ask for product backlog and sprint cadence; separate dev and test teams become multi-sprint bottlenecks so merge into one product backlog and one Sprint (works after 2–3 Sprints); burn downs must burn down only completed items; lack of retros yields surprisingly many issues (one team produces 40 Post-it notes in the first retro); mid‑Sprint ad hoc changes force teams to abandon Sprint — protect focus with a Product Owner and clear planning.
AI-written summary · about
