Backlog is owned by Product Owner; Backlog grooming is about verification and prioritization of Backlog. New stories are added and Epics are decomposed. Definition of Done are described. Story points are estimated, stories are prioritized and scheduled for sprints.
In my experience, Story name, description, and definition of done was ready for each story. All Technical Architects from different domains used to have a meeting and each story was discussed based on the complexities first. Teams normally involved in the discussions were Development Team, QA Team, Infrastructure Team, UI Team, and Automation Team. Business Analysts used to explain each points of Story and based on it we all used to finalize story points. Priorities were given by Business Analysts. In First couple of meetings, we felt it very chaotic and problematic. The reason was our lack of understanding of SCRUM and rigidness. However, we soon realize that too much time is invested in the overall discussions (More than 2-3 Days). So We came to conclusion that before all this meetings with Business Analysts and Scrum Master, we need to have internal meeting for our understanding and then we can have next discussions with BAs. After that we used to involve SCRUM Master. The benefit was evident as there was a understanding and clarity of rhoughts between offshore team and BAs, we reduced time upto 50% in all meetings.
What I feel:
I feel that to gain real benefits, all domains / teams involved in the application development has to have one specialist for that particular team who understands that technology well. The benefit of this is true prediction or near perfection in prediction. If stop Gap arrangements are done for the specific team then it is very difficult to predict time and it usually becomes a speed breaker.
Free Agile Scrum Cheat Sheet & Handbook:
|The Essential Scrum Cheat Sheet||Free Cheat Sheet:Agile Adoption||Free Scrum Master’s Handbook|