Agile → Overview → Backlogs → Sprint Backlog
Use a sprint planning meeting to determine which stories will be committed to during a given sprint. A sprint backlog should only contain stories that the development team has committed to for that sprint. Stories in a sprint backlog should be well-written, have a high priority and a high business value, and should have an accurate story point estimate.
Unlike a product or a release backlog, a sprint backlog should not change once it has been committed to by a development team. A product owner should not add or delete any stories and should only edit a user story after discussing the proposed changes with any affected team members. All work items in a sprint backlog should have assigned owners.
Copyright © 2003–2009 Serena Software, Inc. All rights reserved.