Difference between revisions of "Coaching Environment - TDD"

(New page: == Contact Information == Craig Larman, craig@craiglarman.com. +1 214 914 7593 == Room, Walls, Whiteboards == * People will be organized into table-teams, averaging 5 or 6 people per tea...)
 
Line 2: Line 2:
 
Craig Larman, craig@craiglarman.com. +1 214 914 7593
 
Craig Larman, craig@craiglarman.com. +1 214 914 7593
  
 +
== Context, People ==
 +
While working on the real (usually messy legacy) code, coach developers in how to break dependencies, test in isolation, and do TDD.
 +
 +
min 2 developers, plus coach. max 3 developers.
  
 
== Room, Walls, Whiteboards ==
 
== Room, Walls, Whiteboards ==
* People will be organized into table-teams, averaging 5 or 6 people per team. Thus, we need  NumStudents/5 tables; e.g., 6 or 7 tables if 35 students. The tables are ideally in separate islands, circular or square, with a team at each.  
+
* People will be organized around 1 computer and 2-4 LARGE computer monitors.  
  
* Don’t make it a crowded room; there are a number of exercises that involve the teams moving around.
+
* 1 whiteboard
  
* There are several wall exercises, involving flip chart paper or PostIt Note layouts; each team needs some unencumbered clear wall space for this.
+
* 1 flip chart paper  
  
 +
* 1 tape (e.g., masking tape), unless the flip charts of PostIt flip charts with sticky back
  
== Supplies for the Coach/Speaker  ==
+
* WHITEBOARD marker pens
Read this: [[Supplies - for Coach Use]]
 
  
 
+
* whiteboard eraser
== Table Layout ==
 
* Round tables are ideal
 
 
 
* Tables should not be against the walls; we are using the walls as a main working area in this course.
 
 
 
* Distribute the tables throughout the room
 
  
  
 
== Computers, Software and Networking ==
 
== Computers, Software and Networking ==
* There are a few short exercises on spreadsheets. These are team exercises (average 5 persons per team). Thus, at least one laptop is required for each team; two is nicer. Therefore, ask people to bring a laptop if they have one.
+
* 1 fast computer connected to the real product software, with internal network and internet access.
 
 
* A power supply is NOT needed for each table, because the computer use is minimal. However, please ensure there are some powerstrips “somewhere” in the room so students can recharge laptops.
 
 
 
* No network is required.  
 
 
 
 
 
== Other Supplies for Student Use ==
 
Read this: [[Supplies - Creativity Tools]]
 
 
 
  
== Pictures of Classroom Setup ==
+
* all normal development tools working
[[Image:Csm1.jpg | 680px| ]]
 
  
[[Image:Csm2.jpg | 680px| ]]
+
* NB!! pre-installation of the chosen TDD framework (JUnit, NUnit, BoostTest, ...). ACTION >> Check with the coach with framework to install, and prepare this before the coaching session.

Revision as of 11:43, 16 December 2009

Contact Information

Craig Larman, craig@craiglarman.com. +1 214 914 7593

Context, People

While working on the real (usually messy legacy) code, coach developers in how to break dependencies, test in isolation, and do TDD.

min 2 developers, plus coach. max 3 developers.

Room, Walls, Whiteboards

  • People will be organized around 1 computer and 2-4 LARGE computer monitors.
  • 1 whiteboard
  • 1 flip chart paper
  • 1 tape (e.g., masking tape), unless the flip charts of PostIt flip charts with sticky back
  • WHITEBOARD marker pens
  • whiteboard eraser


Computers, Software and Networking

  • 1 fast computer connected to the real product software, with internal network and internet access.
  • all normal development tools working
  • NB!! pre-installation of the chosen TDD framework (JUnit, NUnit, BoostTest, ...). ACTION >> Check with the coach with framework to install, and prepare this before the coaching session.