The Story Completion Checklist contains the story name, activity, work products and status. As Agile stories are finished, the product owner will work with their Agile team and the team's scrum master to make sure that finished stories are truly complete.

A definition of "Done" is a clear and concise list of requirements that software must adhere to for the team to call it complete.

In order to status a user story as "Done," it must meet the following criteria:

	Is the story fully tested?
	Are necessary automated tests created?
	Are all tests checked into the appropriate test case management system?
	Have the customer requirements been fully met?
	Have customers/stakeholders viewed and accepted the tasks?
	Are changes fully documented in internal specs, etc.?
	Are changes fully reflected in customer-facing documentation (i.e. user manuals, etc.)?
	Are all scrum team members happy with the functionality?
	Are there any remaining caveats or gotchas in use?
	Have negative tests been demonstrated as well as positive?
	Is all necessary error checking in place?
	Have interfacing components/features been tested?
	Are all external dependencies met?
	Are any necessary legal agreements in place to use the work?
	Have workflows been reviewed by usability teams?
	Have text strings been reviewed by legal/UI/usability?
	Are all necessary text string translations in place?
	Are all localization requirements met?
	Have any newly discovered work items been recorded in the backlog?
	Are any bugs that are not going to be fixed documented in release notes/problem tracking items?
	Has the story been marked as complete in agile project management systems?
	Have all builds/branches been integrated into the mainline of code?
	Is the team sure that no other work is necessary?

The Story Completion Checklist provides a vehicle to record whether the story has been completed and Inspected and the number of defects found.

Scroll down to the Agile Story Completion Checklist example below.