Difference between revisions of "Agile Release Planning Workshop"

Line 13: Line 13:
  
 
== Audience ==
 
== Audience ==
This can be 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
+
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
  
  

Revision as of 15:01, 23 March 2008

Overview

3-5 days

In Scrum and most other agile methods there is a period, before the first iteration, during which we need to create a release plan 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

xxx


Outline

xxx


Maximum Participants

30


Environment - Room, Tools, Texts

Read this: Course Environment - Workshop Style1


Text and Notes