[bluGill]

I have long abandoned scrum for Kanban. I don't care about sprints, and getting things done by the end. Just give me (or since I'm the team leader now often I'm the one giving) the next thing to work on and when it is done I'll start the next. Nobody cares about what you got done this sprint, they care about what what got into the next release. Next release includes a lot of manual testing as despite a very great automated test program we constantly discover a lot of serious bugs in manual test that are difficult to automate.

we gave up on points. All anyone cares about is days. Thus it is better to retro on the days estimate vs days to deliver and make adjustments on our end. Nobody cares about days for an individual story anyway - they want the days for the complete feature (or at least enough of the feature that we can ship it)

[nottorp]

> despite a very great automated test program we constantly discover a lot of serious bugs in manual test that are difficult to automate

+1 :)

Yes, I could just upvote. But this deserves more emphasis than that.

[tilwidnk]

Agreed, Scrum is a death march. Kanban is the way.

[shortlived]

Yeah, you are doing it wrong if scrum is deadlines. I've worked with people who had to pull all nighters to get all sprint content done before the sprint closes. I'm using it more as a window to do some cheap analysis on our progress.

[skydhash]

They are always deadlines as long as the cycle is official. An informal status update can be done with the project management tool, a 1:1 meeting or a quick team meeting (in this order)

[The_Colonel]

My experience is very different. Sprint wasn't a deadline in any of the companies I've worked at.