Story refinement checklist

For Product to answer:

Are the changes expected to affect the style in which authors will write a review's text? If yes, have copyeditors been consulted?
Does the story require user-facing text? If yes, have Support been asked to review text for clarity?
Do we expect this feature to present a new challenge to users? For example, if new validation prevents authors from submitting when previously they could? If yes, are all of the Support team aware? Have the MSU been consulted?
Does this story impact Methods, or the reporting of Methods? If so, have the Methods Implementation Editor and MSU been consulted?
Does the story contain a description of value that is clear to the whole team?
Are there dependencies upon other user stories?
Are there dependencies upon other team(s)?
Is the value of this story threatened by probable development in e.g. 6-12 months?
Should the problem be solved by software or could it be solved in other ways?
Is the solution easy to use or does it require lengthy documentation? Consider re-designing.
Have person(s) been identified and informed in time to participate in user acceptance testing?
What communication is required for the story? Action → Define what communication is required for what type of changes, banner, on-off e-mail, author/staff digest (informed by support, CES, methods support team)

For Engineering/QA to answer:

Are there dependencies with other team(s)?
What parts of the system will be touched when implementing the story?
Is there a potential that unused code will be activated?
Are there critical test areas?
Do testers know how they would test the user story?
Are the ACs testable? Is there clear accountability if not?
Does the team need any new knowledge or upskilling to deliver the story?
Do we understand what we can do with the system after the user story is completed (that we cannot do with the current system)?
Do we feel confident that we could take the ticket for development/testing/sign-off without further input?

If a story is estimated: