fiatcode/tdd-workshop
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Add initial slides for TDD workshop presentation with custom styles and navigation

Browse source
This commit is contained in:
fiatcode 2026-04-16 00:22:22 +07:00
parent 3a4521f52a
commit 5b4df9ebd6
No known key found for this signature in database
4 changed files with 1043 additions and 227 deletions
Download patch file Download diff file Expand all files Collapse all files

36
FACILITATOR_GUIDE.md
View file

@ -1,10 +1,13 @@
# Workshop Facilitator Guide — Quick Reference
**Duration:** 2 hours
**Format:** Live demo + hands-on practice with Password Validator or Shopping Cart katas
**Duration:** 80 minutes
**Format:** Live demo + hands-on practice with Password Validator or Shopping Cart katas using 3-Way Ping-Pong (mob programming)
**Team Size:** 3 people (2 developers + you as facilitator/participant)
> **Note:** For the complete detailed plan with minute-by-minute timing, scripts, and checklists, see **WORKSHOP_PLAN.md**. This guide focuses on facilitation tips and kata-specific insights.
> **Facilitator Role:** You'll participate as the 3rd person in the rotation, experiencing TDD alongside the developers. This creates a collaborative learning environment rather than traditional top-down teaching.
---
## Essential Documents
@ -37,14 +40,11 @@ Before the workshop, familiarize yourself with:
| Time | Activity | See |
|------|----------|-----|
| 0:00-0:10 | Welcome & Setup Check | WORKSHOP_PLAN.md |
| 0:10-0:25 | **Live Demo: FizzBuzz TDD** | fizzbuzz/DEMO_SCRIPT.md |
| 0:25-0:30 | Exercise Introduction | Section below |
| 0:30-1:15 | Hands-on Practice (Part 1) | Circulate & nudge |
| 1:15-1:30 | Mid-Point Check-in | WORKSHOP_PLAN.md |
| 1:30-2:00 | Hands-on Practice (Part 2) | Circulate & nudge |
| 2:00-2:10 | Show & Tell | 2-3 volunteers |
| 2:10-2:20 | Retrospective | WORKSHOP_PLAN.md |
| 0:00-0:05 | Welcome & Setup Check | WORKSHOP_PLAN.md |
| 0:05-0:20 | **Live Demo: FizzBuzz TDD** | fizzbuzz/DEMO_SCRIPT.md |
| 0:20-0:25 | Exercise Intro (3-Way Ping-Pong) | Section below |
| 0:25-1:05 | Hands-on Practice (Mob Programming) | Circulate & nudge |
| 1:05-1:20 | Combined Retrospective | WORKSHOP_PLAN.md |
---
@ -77,17 +77,26 @@ Before the workshop, familiarize yourself with:
---
## What to watch for while circulating
## What to watch for while participating
**Your dual role:** You're both a participant in the rotation AND a gentle guide.
**Good signs:**
- Running `dart test` after every small change
- Seeing RED before touching `lib/`
- Short, focused commits (or at least talking through each step)
- Smooth keyboard passing between the 3 roles (Red, Green, Refactor)
**Gentle interventions:**
**Gentle interventions (when it's not your turn at keyboard):**
- *"Have you run the test yet? What did it say?"* — nudge anyone writing too much code before testing
- *"Can you make it pass with even less code?"* — push toward minimal Green
- *"Now that it's Green, what could you clean up?"* — prompt the Refactor step
- *"It's time to pass the keyboard! Let's rotate."* — enforce the rotation
**When it's your turn:**
- Model the behavior you want to see (run tests frequently, minimal code, think aloud)
- Ask questions rather than giving answers: *"What's the simplest thing that could work here?"*
- Show vulnerability: *"Hmm, I'm not sure. What do you think?"*
---
@ -142,7 +151,8 @@ The point is: TDD forces you to decide, and the test documents the decision perm
1. *"What was the first test you wrote? Why that one?"*
2. *"Did your design change as you added more tests? How?"*
3. *"Did you ever feel tempted to skip the Red step and just write the code?"*
4. *"What would have been different if you'd designed the class first, then written tests?"*
4. *"How did the 3-way ping-pong dynamic change how you wrote code?"*
5. *"What would have been different if you'd designed the class first, then written tests?"*
---