Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Depends on what the "you" is here.

If the "you" is the team, go ahead. Add anything you want, as long as you deliver what you promised in the beginning of the sprint.

If the "you" is an external person asking for a "quick job", then the default answer is "talk to the scrum master" whose default answer will be "No.". Then they can start discussing if it is so urgent and important that it can't wait 1-10 business days for the next sprint and/or small enough not to disrupt other work.

The rules are there to protect the team. If the team is willing to take ad-hoc work, nothing in the agile rules says they can't do so. The point is that nobody outside of the team can force them to take on extra work mid-sprint and disrupt their planned work.



> If the "you" is an external person asking for a "quick job", then the default answer is "talk to the scrum master" whose default answer will be "No.

I hate working with people like this. So unhelpful.


I hate being interrupted by people too, that's why I like the Scrum style of working when there is an external client (or an unruly internal one).




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: