1. Definitely not. If the story needs fit, wiggle, adjustment, then it's either not really done, or you raise the changes as another story for the next sprint.

1. Definitely not. If the story needs fit, wiggle, adjustment, then it's either not really done, or you raise the changes as another story for the next sprint. 2. Done is done - it's a binary yes/no thing. Done but not tested is not done. Done but needs documentation is not done. This varies from place to place, but code-done is not done, and coding is usually only 30-odd % of the work. 2b. If that's the case, then you're overcommitted. Next sprint, drop back to what you managed to get done this sprint. The idea is to get things repeatable and features turning out in a maintainable steady fashion. In practice, it works - if there's some discipline from both the devs and the business. If stuff gets shoehorned in, or devs are pulled off to work on critical stuff, then it works about as well as you'd expect (ie. not very).