Sprints incentivize both good and bad compromises. Without some time pressure, some developers may go after interesting things that aren't necessarily in the c

Sprints incentivize both good and bad compromises. Without some time pressure, some developers may go after interesting things that aren't necessarily in the company's best interest. With time pressure, tech debt tends to pile up, and corners get cut, documentation and tests get neglected etc... Personally, I will never again work for a company that does the 2 sprint with daily stand-ups. I am way less productive when I'm being shamed on a daily basis for falling "behind schedule" on some task that ended up being more complex than first glance would suggest. You may say "But that's not scrum!" Of course it isn't, but it is very often how it gets implemented.