During a knowledge sharing session I conducted on user story
writing, I asked the audience: "What does a User Story mean to you?"
The image below captures their responses.
As a Scrum Master, I believe the role is to
facilitate the "3 Cs" to ensure stories deliver a value:
·
Card: A story is more than just a
"As a... I want... So that..." template. It must contain enough
detail to ensure the team knows exactly what to deliver and how to demonstrate
that value.
·
Conversation: Must encourage continuous
dialogue. It is about the team initiating discussions to clarify requirements
and uncover the "why" behind the work.
·
Confirmation: This is about driving
alignment on the "Definition of Done." What does success look like at
the end.
I would love to hear your thoughts. How do you approach user stories with your teams?
No comments:
Post a Comment