Agile Architecture Learning Workshop - Revision history

Clarman at 17:01, 2 May 2023

2023-05-02T17:01:05Z

Clarman at 17:00, 2 May 2023

2023-05-02T17:00:40Z

Clarman: Clarman moved page Agile Architecture Documentation Workshop to Agile Architecture Learning Workshop

2023-05-02T16:56:12Z

Clarman moved page Agile Architecture Documentation Workshop to Agile Architecture Learning Workshop

Clarman at 06:41, 11 December 2012

2012-12-11T06:41:39Z

Clarman at 06:39, 11 December 2012

2012-12-11T06:39:36Z

Clarman at 14:20, 11 March 2012

2012-03-11T14:20:30Z

Clarman at 07:42, 16 February 2012

2012-02-16T07:42:58Z

Clarman at 04:55, 12 February 2012

2012-02-12T04:55:47Z

Clarman at 04:55, 12 February 2012

2012-02-12T04:55:34Z

Clarman at 04:54, 12 February 2012

2012-02-12T04:54:07Z

← Older revision		Revision as of 17:01, 2 May 2023
Line 1:		Line 1:
	== Overview ==		== Overview ==
−	1-2 days (for most systems, if this is the first ~~agile arch doc~~ workshop, 2 days is more realistic; later workshops can be 1 day)	+	1-2 days (for most systems, if this is the first such workshop, 2 days is more realistic; later workshops can be 1 day)

← Older revision		Revision as of 17:00, 2 May 2023
Line 3:		Line 3:


−	In this workshop, people apply agile modeling ~~and documentation~~ techniques to ~~document~~ their software architecture. We take an "N+1" view-model approach, creating the logical view, deployment view, and more, and also write "technical memos." This is done "at the walls" in a small teams, sketching on vast whiteboard spaces, in a wiki, and with video capture of Q&A sessions for different architectural views and technical memos. As will be seen, not only is the architecture documentation created, but the workshop is also a context for ''learning'' about the architecture. For example, different sub-groups are working in parallel on different walls, one doing the logical view, one doing the deployment view, and so forth. We practice "show and tell" visiting other walls, and in this way learn from each other. Another example: we do pair writing and pair review of different technical memos, and learn from each other.	+	In this workshop, people apply agile modeling techniques to collaborate and ''learn'' together their existing as-is software architecture (it is not a workshop for future architecture). One may also call this an Architecture ''Documentation'' workshop, but the focus is on the people learning together and transferring knowledge between them with various methods; the final outputs created and saved ("documents") for others to study are truly secondary to the key idea: ''learning'' the existing state of the system.
		+
		+
		+	We take an "N+1" view-model approach, creating the logical view, deployment view, and more, and also write "technical memos." This is done "at the walls" in a small teams, sketching on vast whiteboard spaces, in a wiki, and with video capture of Q&A sessions for different architectural views and technical memos. As will be seen, not only is the architecture documentation created, but the workshop is also a context for ''learning'' about the architecture. For example, different sub-groups are working in parallel on different walls, one doing the logical view, one doing the deployment view, and so forth. We practice "show and tell" visiting other walls, and in this way learn from each other. Another example: we do pair writing and pair review of different technical memos, and learn from each other.

@@ Line 42: / Line 42: @@
 == Environment - Room, Tools, Texts ==
 * If this is a large group (e.g., more than 10 people), we will need an especially large modeling room with truly *massive* whiteboard areas, in which each group uses 2 of the 4 walls.
 * 1-2 computer projectors and 1-2 project screens (or big white walls we can project on to)

@@ Line 43: / Line 43: @@
 * If this is a large group (e.g., more than 10 people), we will need an especially large modeling room with truly *massive* whiteboard areas, in which each group uses 2 of the 4 walls.
-* 2 computer projectors and 2 project screens (or big white walls we can project on to)
+* 1-2 computer projectors and 1-2 project screens (or big white walls we can project on to)
 * wiki, with all participants having access
-* 2 video cameras with tripod, storage in each for at least 5 hours of video
+* 1-2 video cameras with tripod, storage in each for at least 5 hours of video
 * Also, read and organize for this: [[Course Environment - Workshop Style7]]

@@ Line 42: / Line 42: @@
 == Environment - Room, Tools, Texts ==
 * If this is a large group (e.g., more than 10 people), we will need an especially large modeling room with truly *massive* whiteboard areas, in which each group uses 2 of the 4 walls.
 * wiki, with all participants having access

← Older revision	Revision as of 16:56, 2 May 2023
(No difference)

← Older revision		Revision as of 07:42, 16 February 2012
Line 7:		Line 7:

	The output is an N+1 view model of the architecture combined with technical memos, captured in wiki pages, videos of Q&A sessions related to views and technical memos, and perhaps equally important, learning and an increased shared understanding of the architecture that has been documented.		The output is an N+1 view model of the architecture combined with technical memos, captured in wiki pages, videos of Q&A sessions related to views and technical memos, and perhaps equally important, learning and an increased shared understanding of the architecture that has been documented.
		+
		+
		+	This workshop can also be combined with the definition and organization of a self-study plus Q&A mentoring system for new hires to your company, to speed and improve the architectural knowledge of your staff.

@@ Line 1: / Line 1: @@
 == Overview ==
 -2 days (for most systems, if this is the first agile arch doc workshop, 2 days is more realistic; later workshops can be 1 day)
 In this workshop, people apply agile modeling and documentation techniques to document their software architecture. We take an "N+1" view-model approach, creating the logical view, deployment view, and more, and also write "technical memos." This is done "at the walls" in a small teams, sketching on vast whiteboard spaces, in a wiki, and with video capture of Q&A sessions for different architectural views and technical memos. As will be seen, not only is the architecture documentation created, but the workshop is also a context for ''learning'' about the architecture. For example, different sub-groups are working in parallel on different walls, one doing the logical view, one doing the deployment view, and so forth. We practice "show and tell" visiting other walls, and in this way learn from each other. Another example: we do pair writing and pair review of different technical memos, and learn from each other.