Story Conversation in Agile Scrum


Story Conversation is all about drilling down story details and validates exact requirements. It helps all cross functional team to implement user stories in correct manner.
My Experiences:

We had multiple conversation with Product Owner and BAs. More often with BAs, All queries from the offshore team were discussed and conversation was recorded and stories were edited based on the discussions.

In earlier Sprint Meetings, we realized that there are too many queries from cross functional development teams and hence we decided to keep another level of meeting (pre-meeting) to understand all user stories which we may include in the next sprint.

Following are some articles in Agile Series you may like:
Introduction to Agile Scrum in 2 Minutes What is Agile Scrum
Agile Manifesto and My Experiences Product Owner in Agile
Story Point Estimation in Agile Scrum Backlog Grooming in Agile Scrum
Product Backlog in Agile Scrum Story Conversation in Agile Scrum
Role of Agile Scrum Product Owner What is Scrum Master
Agile Scrum Team Members Sprint Planning in Agile Scrum
Scrum Sprint Retrospective Meeting Documentation in Agile Scrum
Stories and Epics in Agile Scrum Definition of Done in Agile Scrum

Initially we thought it is a additional time we are giving but in Sprint Meeting we realized that it helped in reduction of time as our understanding was far better when we were in Sprint Meeting.

What I feel:

Story Conversations should focus on the entire team and it must not be hijacked by a specific team. In such scenario visible benefits of Story Conversation is not gained and it results into waste of time.

Free Agile Scrum Cheat Sheet & Handbook:

The Essential Scrum Cheat Sheet Free Cheat Sheet:Agile Adoption Free Scrum Master's Handbook

Labels: ,