--
You received this message because you are subscribed to the Google Groups "Scrum Alliance - transforming the world of work." group.
To unsubscribe from this group and stop receiving emails from it, send an email to scrumallianc...@googlegroups.com.
To post to this group, send email to scruma...@googlegroups.com.
Visit this group at http://groups.google.com/group/scrumalliance.
For more options, visit https://groups.google.com/d/optout.
I would say SM facilitate the meeting as well as do the following:1.Right people are present in that meeting2.Right questions are asked3.Right estimation is done for a specific story4.Stories are moved to right iterations
5. Capture meeting minutes if agreed upon trashing any user stories usually evolves in this meeting and send that notes to the team for future reference or ensure documented in the story of story removal.As a scrum master prior to the meeting you also make sure wireframes are ready if you refer to them in refinement meetings.
--On Tue, Apr 7, 2015 at 12:45 PM, Leslie Scantling <teamsc...@msn.com> wrote:I recently read a blog post from Mike Cohn regarding the backlog refinement meeting and it mentioned including the scrum master. I have always coached product owners that refining the backlog lives under their role/responsibility in our Agile implementation. As the scrum master, I certainly want to ensure the meeting happens, and that planning meetings are well prepared for with a estimated prioritized backlog, but am not fully sure what the purpose of the SM being in physical attendance in the refinement meeting. Can I get some input from members on how they feel a scrum master adds value here?
Regards -
Leslie Scantling
--
You received this message because you are subscribed to the Google Groups "Scrum Alliance - transforming the world of work." group.
To unsubscribe from this group and stop receiving emails from it, send an email to scrumallianc...@googlegroups.com.
To post to this group, send email to scruma...@googlegroups.com.
Visit this group at http://groups.google.com/group/scrumalliance.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "Scrum Alliance - transforming the world of work." group.
To unsubscribe from this group and stop receiving emails from it, send an email to scrumallianc...@googlegroups.com.
To post to this group, send email to scruma...@googlegroups.com.
Visit this group at http://groups.google.com/group/scrumalliance.
For more options, visit https://groups.google.com/d/optout.
Mark Levison | 1 (877) 248-8277 | Twitter | LinkedIn | Facebook Certified ScrumMaster Training: Vancouver | Edmonton | Ottawa | Montreal | Toronto Certified Product Owner & Private Training also available ~ Our Training Schedule Agile Pain Relief Consulting | Notes from a Tool User Proud Sponsor of Agile Tour Gatineau Ottawa and Agile Coach Camp Canada |
--
You received this message because you are subscribed to the Google Groups "Scrum Alliance - transforming the world of work." group.
To unsubscribe from this group and stop receiving emails from it, send an email to scrumallianc...@googlegroups.com.
To post to this group, send email to scruma...@googlegroups.com.
Visit this group at http://groups.google.com/group/scrumalliance.
For more options, visit https://groups.google.com/d/optout.
> To unsubscribe from this group and stop receiving emails from it, send an email to scrumalliance+unsubscribe@googlegroups.com.
> To post to this group, send email to scruma...@googlegroups.com.
> Visit this group at http://groups.google.com/group/scrumalliance.
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups "Scrum Alliance - transforming the world of work." group.
To unsubscribe from this group and stop receiving emails from it, send an email to scrumalliance+unsubscribe@googlegroups.com.
Product backlog refinement (activity)
Product backlog items are often large and general in nature, and they can come and go as priorities change. Because of this fluid environment, product backlog refinement is an ongoing activity throughout a Scrum project. When you refine the product backlog, you:
- Confirm the order of the product backlog items
- Remove or demote items that no longer seem important
- Add or promote items that come up or become more important
- Split larger items into smaller items
- Merge smaller items into larger items
- Estimate items
Product backlog refinement is an excellent way to prepare for upcoming sprints. During this process, you give special attention to selecting items coming up for the next sprint. Things to consider include:
- Identify which items are sprint-ready
- Each item for the sprint should represent an increment of "business value."
- The development team needs to be able to build each item within a single sprint.
Depending on the nature of the product, other skills and inputs may be needed. That's why product backlog refinement is really a responsibility of all team members, not just the product owner.
- Both the stakeholders and the entire Scrum team need to be clear on what is intended.
To unsubscribe from this group and stop receiving emails from it, send an email to scrumallianc...@googlegroups.com.
I am fortunate to have very good, technical and vested Product Owners who provide very strong leadership (with teams) iin owning backlogs and their
validity. I have never attended backlog refinement, but have always said I am available to do so if needed. I always look at the results and strength of the teams performance based on their retrospective,