Neha – Developer 1, Bob – Product Owner, Peter – Agile Coach
Neha – We are always missing acceptance criteria and functional details in a story. It is really tough to commit a story with little or no clarity.
Bob – The Agile lets you evolve the requirements as you move. This is perfectly alright. I am within the boundary. I will write the acceptance criteria when I get the time.
Peter- The requirements can evolve and that’s an advantage for a customer while stories cannot keep evolving during the sprint. You have an opportunity to refine the acceptance criteria. If the functional requirements are not clear or acceptance criteria cannot be determined during planning/grooming, the story shouldn’t be committed. It should be moved for a later sprint.
Bob – Can I write the acceptance criteria and later change it altogether during the sprint as we progress?
Peter – No for sure. The change in a story once committed is a “scope creep”. You must move that to the next sprint of post-re-estimation, you might have to remove some other stories out of a sprint. Ideally, you are not allowed to change anything during a sprint. Adding more details to acceptance criteria to make it more clear as you move should be fine, though.
Bob – Fair! I will take out the stories where I don’t have clarity.
Challenge – Writing a one-liner description for a story should be fine and we will keep updating it while working in progress during the sprint.