Agile Release Planning Workshop - Revision history

Clarman at 21:12, 5 February 2012

2012-02-05T21:12:26Z

Clarman at 06:53, 28 October 2008

2008-10-28T06:53:05Z

Clarman at 05:20, 26 March 2008

2008-03-26T05:20:52Z

Clarman at 05:19, 26 March 2008

2008-03-26T05:19:41Z

Clarman at 22:01, 23 March 2008

2008-03-23T22:01:31Z

Clarman at 22:01, 23 March 2008

2008-03-23T22:01:12Z

Clarman at 20:36, 23 March 2008

2008-03-23T20:36:55Z

Clarman at 19:45, 23 March 2008

2008-03-23T19:45:01Z

Clarman at 20:01, 21 March 2008

2008-03-21T20:01:44Z

Clarman: New page: == Overview == xxx == Methods of Education == xxx == Audience == xxx == Level== xxx ==Prerequisites== none ==Objectives== xxx == Outline == xxx == Related Courses == foo...

2008-03-21T18:29:04Z

New page: == Overview == xxx == Methods of Education == xxx == Audience == xxx == Level== xxx ==Prerequisites== none ==Objectives== xxx == Outline == xxx == Related Courses == foo...

New page

== Overview ==
xxx

== Methods of Education ==
xxx

== Audience ==
xxx

== Level==
xxx

==Prerequisites==
none

==Objectives==
xxx

== Outline ==
xxx

== Related Courses ==
[[foo]]

== Maximum Participants ==
30

== Environment - Room, Tools, Texts ==

@@ Line 39: / Line 39: @@
 == Outline ==
 * Vision workshop
 * Requirements workshop
 * Effort estimation workshop

@@ Line 1: / Line 1: @@
 == Overview ==
 -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.
+In Scrum 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.
 <br>
 <br>
@@ Line 29: / Line 29: @@
 * agile estimating and planning
 * modeling with user stories
 * mind mapping
 * affinity clustering

@@ Line 25: / Line 25: @@
 == 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 a relevant secondary goal, in addition to actually creating the plan. Thus, learning objectives include (but certainly not limited to):
+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
@@ Line 34: / Line 34: @@
 * prioritization in Scrum
 * much more
 == Outline ==

@@ Line 25: / Line 25: @@
 == Objectives ==
-xxx
+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 a relevant secondary goal, in addition to actually creating the plan. Thus, learning objectives include (but certainly not limited to):
 == Outline ==
-xxx
+* Vision workshop

← Older revision		Revision as of 22:01, 23 March 2008
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

@@ Line 1: / Line 1: @@
-TO BE COMPLETED -- copy from PDF description
+== Overview ==
 == Methods of Education ==
-Discussion, presentation, Q&A, workshop exercises
+primarily workshop exercises & coaching; some discussion, presentation, Q&A

← Older revision		Revision as of 20:01, 21 March 2008
Line 37:		Line 37:

	== Environment - Room, Tools, Texts ==		== Environment - Room, Tools, Texts ==
		+	Read this: [[Course Environment - Workshop Style1]]
		+
		+
		+	'''Text and Notes'''
		+	* a useful pre-read is [http://www.scrumprimer.com/ The Scrum Primer]