1

I have a question for you guys. Say, you're given a task as an item in a product backlog. Say, you have a deliverable that's due the following day. If you're behind on the task compared to when you made your estimates, what do you do about it? Does it make you anxious knowing your behind schedule? How do you deal with this? Do you tell the scrum master or the product owner?

closed as primarily opinion-based by Ampt, user40980, Wayne Molina, GlenH7, thorsten müller Jul 18 '14 at 7:05

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise. If this question can be reworded to fit the rules in the help center, please edit the question.

2
  • Yes, it makes me anxious. But I am usually both behind and anxious anyway.

  • That's what daily standups are for -- so the team doesn't discover a week later that you're a week behind.

1

I would usually relay that information to the scrum master during the daily scrum meeting. As soon as you know you're behind you should inform the scrum master so he can either get someone to help you (maybe someone else is ahead of schedule and has bandwidth to help), determine whether overtime is needed, or if it's an impediment outside of your team's control then the backlog item needs to be deferred he can provide rationale to stakeholders.

  • Working overtime should really only be a last resort for if the feature is actually needed at the end of that sprint (say, due to a bad promise from marketing). Otherwise your velocity is going to get screwed up and create the expectation that this higher number of story points is normal. – Izkata Jul 18 '14 at 4:19

Not the answer you're looking for? Browse other questions tagged or ask your own question.