Difference between revisions of "Coaching Environment - TDD"
| Line 1: | Line 1: | ||
== Contact Information == | == Contact Information == | ||
Craig Larman, craig@craiglarman.com. +1 214 914 7593 | Craig Larman, craig@craiglarman.com. +1 214 914 7593 | ||
| + | |||
== Context, People == | == Context, People == | ||
| Line 6: | Line 7: | ||
min 2 developers, plus coach. max 3 developers. | min 2 developers, plus coach. max 3 developers. | ||
| + | |||
== Room, Walls, Whiteboards == | == Room, Walls, Whiteboards == | ||
Revision as of 11:44, 16 December 2009
Contents
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.