Tag: Refinement

To conduct the workshop, follow these steps:

• In 30-minute cycles,
  • The PO presents the next PBIs that aren’t Ready to the team. (up to 5 minutes)
  • The Development Team decomposes into sub-teams of 3-4 people.
  • Each sub-team selects one of the next PBIs and gets it Ready. (15-20 minutes)
    • Use User Stories, 3 Cs, INVEST, your Definition of Ready, etc. to guide you.
    • If Readiness is blocked by an impediment outside the Scrum team, the sub-team makes a concrete plan for what they will do to get the PBI Ready before the next Sprint Planning or Backlog Refinement meeting.
  • Merge back into whole group, the full Scrum team.
  • Sub-teams present their work to the whole group. (5-10 minutes)
  • Take a break (5 minutes)
  • Repeat
• Celebrate!

Read the original article here: https://kasperowski.com/how-to-a-great-product-backlog-refinement-workshop/

Scrum is a practical framework to build products, provided you identify in advance what to build. But even after a successful product discovery phase, you may struggle to make the right thing in the right way if your product backlog is not up to the job. Garbage in, garbage out – as the saying goes. The following article points at 28 of the most common product backlog anti-patterns – including the product backlog refinement process – that limit your Scrum team’s success.

Read the complete article here: https://age-of-product.com/28-product-backlog-anti-patterns/

This article on Product Backlog refinement shows that Refinement is more than just a meeting where the whole Scrum Team is having a discussion. It requires and involves everyone with shared and special responsibilities. It’s easy to lose sight of the importance of Product Backlog refinement because of your focus on the Sprint. But making time for healthy Product Backlog Refinement makes way for an awesome collaboration and teamwork, building a product that customers really enjoy!

Read the complete article from Jasper Alblas here: https://www.scrum.org/resources/blog/scrum-trenches-product-backlog-refinement-scrum-team-responsibility