[nsxwolf]

With Agile, I have found that I'm never able to just take a day off here and there. I need to take enough time off that I can meaningfully commit to taking less work in the sprint, otherwise my day off just leads to working nights and weekends to catch up. So it's either take the entire 2-week sprint off, or an entire week and hope I can correctly estimate what half a workload looks like.

Yes, yes, doing Agile wrong etc

[IshKebab]

Or you can just catch up when you're working? I don't understand what this has to do with agile. Are they going to fire you if you don't finish the sprint's tasks?

[nsxwolf]

Eventually, yes?

Everywhere I’ve ever worked has treated sprints as an endless series of 2 week deadlines.

(Yes, I understand this is not “real” agile. I’ve never seen “real” agile and don’t personally know anyone who has.)

[IshKebab]

Well that sucks. Everywhere I've worked has treated sprints as a short term planning exercise. There's no penalty for not finishing all your sprint tasks; it just means your estimate was off and you probably need to add less work to the next sprint.

[bryan2]

I think it’d be really hard not to psychologically anchor.

My experience with agile is either: * you get stressed out being measured at such a low resolution and sandbag or * you wind up in a low accountability context because even management knows how messed up scrum is for their use case.

I wish we had something better.