Of course, a number of companies don't operate real SPRINTs at all. They run small three/four week waterfall projects that deliver something at the end. You know what I mean... One week for design, one week for development and one week for testing rather than integrated design, develop & test activities.
The problems this causes is identical to their Waterfall big brother:
- Testing being squeezed at the end of the cycle and either not completed properly or causing "delays"
- Everyone rushing at the end to complete things that can't really be completed in the time available
- Everyone working extra hours & weekends to deliver what they promised
- Everyone getting increasingly stressed as the end of the SPRINT looms large.
Add that to the "technical" debt that SCRUMs slowly develop over the first few sprints without automated testing or integrated development and you've a recipe for serious conflict!
So look honestly at your SCRUM process during your next retrospective. Are you really running small waterfalls? Is your team getting stressed? Can your team get better at working together on parallel design, development & test?
I promise you it'll make everyone's life so much better and you'll deliver so much more.