Agile Story Completion Checklist

user story checklist

As agile stories are finished, the product owner should work with their agile team and the team’s scrum master to make sure that finished stories are truly complete.   Typically at the end-of-sprint demonstration, user stories are demoed and then marked as complete.   Each organization/team should have a checklist that is used to define what complete means to them.  Here is a starting point to build your team’s checklist:

 

Ο  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 test 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 systems?

Ο  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?

Comments are closed.