The Stack Overflow podcast is back! Listen to an interview with our new CEO.
    Tweeted twitter.com/#!/StackProgrammer/status/420420903206674432
    Post Reopened by Bart van Ingen Schenau, Martijn Pieters, k3b, ChrisF
    Question Unprotected by maple_shaft
    Post Closed as "duplicate" by gnat, maple_shaft of
    Notice added Insufficient explanation by maple_shaft
    Question Protected by maple_shaft
2 typo corrected
| link

Do Scrum sprints mean to work at the fastest pasepace possible?

1
source | link

Do Scrum sprints mean to work at the fastest pase possible?

I recently interviewed with some companies that do Agile, Scrum to be more precise and there are some things that don't quite seem like Agile to me. I'll take one case that particularly interests me right now, that of Scrum sprints.

One particular project manager I talked to (yes, I said project manager) proudly stated that people in her team understand ("were told" is what I picked up from the context) that you don't go home when the working hours are over, you go home when the job is done, no matter how much it takes. What I've read in between the lines is that we pack as much features as possible into a sprint and work overtime to make it happen.

Now, I haven't done Agile by now (worked with financial and governmental institutions which most still do prefer waterfall) but my understanding is that:

  • sprint in Scrum is the name for the generic iteration in Agile;
  • the team should work at a sustainable pace and try to avoid long term overtime as that has effects only on the short time and the effects are dwarfed by the problems they incur in the long time.

Are my statements right? And, should I take the manager's presentation as a red flag?