Legacy Code Workshop
It was difficult getting our items to a point where the workshop was more then "find the dependency issue". And this was after coming in "prepared". I feel like we dropped the ball here.
How to improve:
Getting production code under test is not a 'contained' process. It quickly spends a lot of time on items that should be demonstrated once or twice, but then moved along. Spending time prior working with us to get something working in the test harness, then remove pieces to turn it into the above state would have been beneficial for the class as a whole.