Page History

• The REQUESTER of a story is responsible for providing criteria to ACCEPT or REJECT delivery for DELIVERy a story. For code implementation stories, this includes provision of a test.

• The OWNER of a story STARTs, FINISHes and DELIVERs a story. Owners aren't assigned until the requester can evaluate delivery of a story.
• The PRODUCT OWNER 

• A story cannot be in a SPRINT without a requester, delivery criteria, and an owner.

Example:

1. Jonathan requests the Glacier Mock story. It goes into the icebox.  It has no owner. It has no acceptance criteria.
2. At the sprint planning meeting, we assign acceptance criteria and move the story to the backlog. The story has no owner to do the work.
3. If the story goes into the current sprint, it may not have an owner (Don't assign owners to stories outside sprints!).
4. At the next daily scrum, Chris decides to work on this story. He STARTs work on the story, and makes himself the owner.
5. 3 hours later, Chris is done with the work. Chris makes a pull request, makes Jonathan the reviewer, and clicks FINISH.
6. Jonathan (the requester) reviews the pull request (runs tests, etc.). When Jonathan thinks the ticket is complete, he accepts the pull request and clicks DELIVER in pivotal.
7. Some notifications happen, and Eddie creates a CHORE to evaluate.
8. Eddie ACCEPTs or REJECTs the story based on somethingoutcome of that chore.
9. If the work is subsequently revealed to be incomplete, Eddie REJECTs the story and moves it into the backlog.