Product Backlog Refinement (grooming) Workshop

Revision as of 04:49, 22 December 2009 by Clarman (talk | contribs) (New page: == Overview == 1 day In Scrum, 5-10% of each Sprint should be spent on refining the Product Backlog, with the Team and Product Owner. This is ideally done in a focused workshop. The activ...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Overview

1 day

In Scrum, 5-10% of each Sprint should be spent on refining the Product Backlog, with the Team and Product Owner. This is ideally done in a focused workshop. The activities include:

  • splitting large items (e.g., user stories)
  • detailed analysis of items (e.g., using acceptance test-driven development techniques, among others)
  • re-estimation of the Release Backlog (a portion of the Product Backlog)

and most other agile methods there is a period, before the first iteration, during which we need to create a release plan or initial Product Backlog of high-level requirements, estimates, and so forth. A target date and content goal are needed. In Scrum terms, we need to create the Release Backlog -- the subset of the Product Backlog describing the next release, in terms of items, effort estimates, value estimates, risk, and priority.

Learning how to do agile release planning requires coaching-while-doing; it can't be effectively learnt in a classroom setting. In this workshop, the coach will facilitate the activities of release planning for a real product, while educating.


Methods of Education

primarily workshop exercises & coaching; some discussion, presentation, Q&A


Audience

This can be for 1 or 2 (maximum) product groups. Attendees should include a cross-functional representation from product management, developers, testers, marketing, sales, and other relevant stakeholders


Level

This is an immersive workshop. No prior knowledge is required, but the experiences and knowledge will extend from introductory to intermediate or advanced.


Prerequisites

none.


Objectives

This is not a course per se, but a product-specific (or 2 products maximum) workshop to create the release plan for a Scrum-based development release. Nevertheless, learning how to do agile release planning is an important complimentary goal, in addition to actually creating the plan. Thus, learning objectives include (but are not limited to):

  • agile estimating and planning
  • modeling with user stories
  • splitting large user stories
  • mind mapping
  • affinity clustering
  • Scrum Product Backlog creation
  • prioritization in Scrum
  • much more


Outline

  • Vision workshop
  • Requirements workshop
  • Effort estimation workshop
  • Value estimation workshop
  • Risk estimation workshop
  • Product (Release) Backlog shaping and prioritization


Maximum Participants

30


Environment - Room, Tools, Texts

Read this: Course Environment - Workshop Style1


Text and Notes