User Story Refinement/User Story Workshop
Hello
I am new to Scrum and Jira, i am looking to become a Scrum Master
In the company i work for the Scrum team have User Story Workshops/Refinement Sessions
Questions.
- In terms of the Acceptance Criteria, how does the Product Owner Get these. How can they be sure those are indeed the complete list of Acceptance Criteria
-
In terms of the Meeting approach/Mechanics - How does one know if the Story will need Dev/Testing/Prod Release. The reason i ask is that they have a standard template for Features and Stories which as standard include Dev/Test Prod etc. But in some case these might not be applicable
Regards
Rice
It's the Increment being put into use which must be Done. The things you are describing may or may not represent a certain level of Done, but where is the Definition of Done for the whole Sprint Increment? That's what I would advise you to get in order with the Developers. Ultimately they will be accountable for the quality of the work they do.
Acceptance Criteria come out of conversations with the stakeholders, often the customers or users of the product being built. The Product Owner is the one who is primarily accountable for managing the Product Backlog and ensuring that the work done by the team is valuable, which often means interacting frequently with stakeholders and understanding their needs and desires. However, it's often less than optimal to have the Product Owner be a gatekeeper between the rest of the Scrum Team and the stakeholders.
Unfortunately, I don't think anyone can tell you what work a given Product Backlog Item would need to be considered Done. This depends a lot on your context. But I'd keep in mind that the goal is to produce a usable, valuable Increment each Sprint. Since the Product Backlog consists of work needed to improve the product, I suspect most (if not all) will need to be designed, developed, tested, and released or deployed to be valuable to stakeholders.