TDD Bootcamp - Revision history

Clarman at 19:47, 23 March 2008

2008-03-23T19:47:09Z

Clarman at 20:58, 21 March 2008

2008-03-21T20:58:50Z

Clarman at 20:58, 21 March 2008

2008-03-21T20:58:00Z

Clarman at 20:55, 21 March 2008

2008-03-21T20:55:42Z

Clarman at 20:55, 21 March 2008

2008-03-21T20:55:25Z

Clarman at 17:14, 21 March 2008

2008-03-21T17:14:41Z

Clarman at 16:02, 21 March 2008

2008-03-21T16:02:16Z

Dnunn at 17:04, 3 March 2008

2008-03-03T17:04:57Z

Dnunn at 17:02, 3 March 2008

2008-03-03T17:02:59Z

Clarman at 18:34, 31 January 2008

2008-01-31T18:34:30Z

@@ Line 21: / Line 21: @@
 == Methods of Education ==
-xxx
+primarily workshop exercises & coaching; some discussion, presentation, Q&A
@@ Line 57: / Line 57: @@
 * Test, TDD and refactoring
 * Lessons learned

← Older revision		Revision as of 20:58, 21 March 2008
Line 68:		Line 68:

	== Environment - Room, Tools, Texts ==		== Environment - Room, Tools, Texts ==
−	[[Course Environment - Workshop ~~Style2~~]]	+	[[Course Environment - Workshop Style4]]

← Older revision		Revision as of 20:58, 21 March 2008
Line 68:		Line 68:

	== Environment - Room, Tools, Texts ==		== Environment - Room, Tools, Texts ==
−	[[Course Environment - ~~Agile Software Development with TDD]]~~	+	[[Course Environment - Workshop Style2]]
−
−	~~[[Environment - TDD Software~~]]

@@ Line 69: / Line 69: @@
 == Environment - Room, Tools, Texts ==
 [[Course Environment - Agile Software Development with TDD]]
 [[Environment - TDD Software]

← Older revision		Revision as of 20:55, 21 March 2008
Line 69:		Line 69:
	== Environment - Room, Tools, Texts ==		== Environment - Room, Tools, Texts ==
	[[Course Environment - Agile Software Development with TDD]]		[[Course Environment - Agile Software Development with TDD]]
		+	[[Environment - TDD Software]

@@ Line 18: / Line 18: @@
 <br>
 Having at least the shell of a working CI site helps immensely but is not a prerequisite.
-<br>
-<br>
-== Agenda ==
+== Methods of Education ==
 * Intros
 * TDD is not unit testing: The deep motivation and benefits of TDD
@@ Line 32: / Line 57: @@
 * Test, TDD and refactoring
 * Lessons learned
-==Course Level==
+== Related Courses ==
-Immersive: This bootcamp model leans heavily on the attendees commitment and desire to progress their project work using TDD.
+[[foo]]

@@ Line 46: / Line 46: @@
 * apply basic refactorings and refactoring tools
 * transform agile OO models into OO code and tests
 ==Course Level==
 Immersive: This bootcamp model leans heavily on the attendees commitment and desire to progress their project work using TDD.
-== Environment & Participants ==
 [[Course Environment - Agile Software Development with TDD]]

@@ Line 40: / Line 40: @@
 ==Skills Gained==
 Upon completion of this course, students should be able to:
-    * test-drive in their existing code-base
+* test-drive in their existing code-base
-    * run CI builds
+* run CI builds
-    * develop with CI as a key value (as a developer habit, not a tool-set)
+* develop with CI as a key value (as a developer habit, not a tool-set)
-    * apply basic refactorings and refactoring tools
+* apply basic refactorings and refactoring tools
-    * transform agile OO models into OO code and tests
+* transform agile OO models into OO code and tests
 ==Course Level==
 Immersive: This bootcamp model leans heavily on the attendees commitment and desire to progress their project work using TDD.

@@ Line 1: / Line 1: @@
 == Overview ==
-The TDD bootcamp is an experience-driven workshop, not lecture driven. The "written" materials of the course are normally a few posters on the wall and the agenda. The workshop may be supplemented with learning aids from the [[ Agile TDD and Refactoring]] course, or may follow that course.
+days or 10 days
 <br>
 <br>
 While it may be possible to lecture on TDD and refactoring for days on end, our observations on TDD adoption is that the primary problems are two-fold:
-* First and foremost, developers have been trained to write the code first and manually debug to test their solutions. Replacing this changed habit with one that requires more forethought, discipline, and more code, cannot be done through lecture. It must be done through practice for an extended period of time. The bootcamp is an alternate approach to “sit side-by-side” instruction (which has a low adoption rate) or the “use consultants for ½ your team” (which has a high adoption rate).
+* Developers have been trained to write the code first and manually debug to test their solutions. Replacing this changed habit with one that requires more forethought, discipline, and more code, cannot be done through lecture. It must be done through practice for an extended period of time. The bootcamp is an alternate approach to “sit side-by-side” instruction (which has a low adoption rate) or the “use consultants for ½ your team” (which has a high adoption rate, along with a high cost).
-* Second, many of the developers are working with large, poorly coded (for unit testing at least) applications.
+* Many of the developers are working with large, poorly coded applications and time, advice, and encouragement is needed to overcome the initial obstacles to enabling test-driving modifications to that code.
 <br>
 The design of this bootcamp assumes:
 * While lecture is valuable, experience is more valuable.
-* While knowledgeable instructors are valuable, encouraging the students to find the knowledge on web, on their own, is more valuable.
+* While knowledgeable instructors are valuable, encouraging the students to find the knowledge on their own, is more valuable.
 <br>
 <br>
@@ Line 34: / Line 32: @@
 * Test, TDD and refactoring
 * Lessons learned

@@ Line 5: / Line 5: @@
 While it may be possible to lecture on TDD and refactoring for days on end, our observations on TDD adoption is that the primary problems are two-fold:
 * First and foremost, developers have been trained to write the code first and manually debug to test their solutions. Replacing this changed habit with one that requires more forethought, discipline, and more code, cannot be done through lecture. It must be done through practice for an extended period of time. The bootcamp is an alternate approach to “sit side-by-side” instruction (which has a low adoption rate) or the “use consultants for ½ your team” (which has a high adoption rate).
-* Second, many of the developers are working with large, poorly coded (for unit testing at least) applications. Doing TDD to build a Stack simply does not address the issues they'll have when they try to work on their code, nor does simply saying "snip the dependencies".
+* Second, many of the developers are working with large, poorly coded (for unit testing at least) applications.
 <br>
 <br>
@@ Line 15: / Line 17: @@
 <br>
 The theme of the bootcamp is to dare people to do things differently than they did last week--TDD is just one part of that. They don't think working off the main trunk or a project branch will work? OK, how about we just try it for two weeks? They don't think they can check in every 30 minutes? Ok, just try it. They don't think they can evolve towards the software architecture they have in mind with YAGNI? Maybe, let's try it YAGNI for a while, ruthlessly.
+<br>
 Having at least the shell of a working CI site helps immensely but is not a prerequisite.
+<br>
 == Agenda ==
 * Intros
@@ Line 26: / Line 30: @@
 ** who is responsible for the quality of the s/w you write?
 ** What do you do to ensure it?
 * What to test?
 * Test tools selection
 * Test, TDD and refactoring
 * Lessons learned