Agile Modeling Design Workshop - Revision history

Clarman at 11:15, 17 July 2011

2011-07-17T11:15:40Z

Clarman at 23:30, 15 July 2010

2010-07-15T23:30:58Z

Clarman at 13:12, 16 November 2008

2008-11-16T13:12:59Z

Clarman at 13:12, 16 November 2008

2008-11-16T13:12:08Z

Clarman at 13:11, 16 November 2008

2008-11-16T13:11:05Z

Clarman at 13:10, 16 November 2008

2008-11-16T13:10:31Z

Clarman at 13:06, 16 November 2008

2008-11-16T13:06:32Z

Clarman at 13:05, 16 November 2008

2008-11-16T13:05:25Z

Clarman at 13:00, 16 November 2008

2008-11-16T13:00:30Z

Clarman at 12:59, 16 November 2008

2008-11-16T12:59:48Z

@@ Line 1: / Line 1: @@
 == Overview ==
--5 days
+.5-5 days
 In this case, a picture is definitely worth a thousand words: [[Agile Modeling Pictures]]

@@ Line 29: / Line 29: @@
 == Prerequisites ==
-There are not strict prerequisites. However, people who have attended any one of the follow courses will be better prepared to take full advantage of this workshop:
+There are not strict prerequisites; my decision will depend on the group and product. However, people who have attended any one of the follow courses will be better prepared to take full advantage of this workshop, and may be requested to do so before this workshop:
 * [[Agile Software Development: Hands-on Practices, Principles, Agile Modeling, and TDD]]
 * [[Agile Design and Modeling for Advanced Object Design with Patterns]]
 * [[Applying UML and Patterns: Hands-on Mastery of OOA/D, Agile Modeling, & Patterns -- & with TDD introduction]]

← Older revision		Revision as of 13:12, 16 November 2008
Line 37:		Line 37:

	== Objectives ==		== Objectives ==
−	This is not a course per se, but a product-specific (or 2 products maximum) workshop to do design work. Nevertheless, in the context of the workshop, participants will learn more about visual modeling, new ways to model problems, and specific analysis- or design-patterns, as required.	+	This is not a course per se, but a product-specific (or 2 products maximum) workshop to do design work. Nevertheless, in the context of the workshop, participants will learn more about visual modeling, new ways to model problems, and specific analysis patterns or design patterns, as required.

@@ Line 8: / Line 8: @@
 <br>
 <br>
-Then, after a design workshop, the team can sit down at their tables, ideally surrounded by their sketches on the walls, and start implementing the product, inspired by the agile models on the walls.
+Then, after a design workshop, the team can sit down at their tables, ideally surrounded by their sketches, and start implementing the product, inspired by the agile models on the walls.
 <br>
 <br>

@@ Line 2: / Line 2: @@
 -5 days
-In this case, a picture is definitely worth a thousand words:
+In this case, a picture is definitely worth a thousand words: [[Agile Modeling Pictures]]
 <br>
 <br>

← Older revision		Revision as of 13:10, 16 November 2008
Line 27:		Line 27:

	== Level ==		== Level ==
−	This is an immersive workshop. No prior knowledge is absolutely required~~, but the~~ experiences and knowledge will extend from introductory to intermediate or advanced. ~~And, it the~~ workshop is most effective for people who have met the prerequisites.	+	This is an immersive workshop. No prior knowledge is absolutely required. The experiences and knowledge will extend from introductory to intermediate or advanced. The workshop is most effective for people who have met the "soft" prerequisites.

← Older revision		Revision as of 13:06, 16 November 2008
Line 55:		Line 55:
	If there are two groups, we will need an especially large modeling room with truly massive whiteboard areas, in which each group uses 2 of the 4 walls.		If there are two groups, we will need an especially large modeling room with truly massive whiteboard areas, in which each group uses 2 of the 4 walls.

−	Read this: [[Course Environment - Workshop ~~Style1~~]]	+	Read this: [[Course Environment - Workshop Style2]]
−
−
−	~~'''Text and Notes'''~~
−	* a useful pre-read is [http://www.scrumprimer.com/ The Scrum Primer]

@@ Line 21: / Line 21: @@
 == Audience ==
-This can only be for one product group. Attendees should include the cross-functional development team, the Scrum team composed of all areas of discipline (software, interaction design, domain expertise, database, architecture, business analysis, documentation, testing, ...) necessary for creating the product.
+This can only be for one or two product groups. Attendees should include the cross-functional development team, the Scrum team composed of all areas of discipline (software, interaction design, domain expertise, database, architecture, business analysis, documentation, testing, ...) necessary for creating the product.
@@ Line 37: / Line 39: @@
 == 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):
+This is not a course per se, but a product-specific (or 2 products maximum) workshop to do design work. Nevertheless, in the context of the workshop, participants will learn more about visual modeling, new ways to model problems, and specific analysis- or design-patterns, as required.
 == Outline ==
-* Vision workshop
+* set up the modeling walls
-* Requirements workshop
+* short group session to synchronize
-* Effort estimation workshop
+* agile design modeling at the walls
 == Maximum Participants ==
+For each product group (2 maximum): 9 people (i.e., one maximum-sized Scrum team)
 == Environment - Room, Tools, Texts ==
 Read this: [[Course Environment - Workshop Style1]]