Autumn of Agile Iteration 01 Part D Screencast is Available

I’m happy to report that the latest installment in the Autumn of Agile screencast series is now available for immediate download from the main site.

Refactoring to Eliminate Technical Debt

In this screencast, we take some time to do some (minor) refactorings to start to pay down some technical debt that we’ve started to incur in the project.  It may seem strange to worry about technical debt before we’ve even finished our first user story(!) but from experience I have learned that its never too soon to start incurring technical debt and so its never too soon to start to spend some effort paying it down either.  If you let it get ahead of you, many projects never manage to entirely recover.

Time more under Control

I did manage to solve another of my problems with this installment: its length is back under control smile_thinking.  This screencast clocks in at a more manageable 1:45 or so and while others have indicated that length isn’t a concern for them, for my own sanity I would prefer that these by kept to a more reasonable length (where possible).

I have (mostly) put to bed my concerns that the length of these will be prohibitive for viewers, but that obviously doesn’t mean that I’m going to make them long just for the sake of it. smile_zipit

Still Covered A Lot

Despite the short(er) length, we still managed to cover quite a bit of territory in this installment including…

  • understanding some pitfalls of just accepting Windsor’s default Singleton lifecycle for its objects
  • refactoring our component registrations in the container to leverage the Windsor fluent Registration API
  • identifying that 9 out of 10 times you think you’ve found a bug in someone else’s framework it really means its time to look much more closely at your own work (to see where you went wrong!)
  • changing the behavior of the AddSkills(…) method on our Employee object to handle trying to add duplicate skills
  • finally closing our first user story (yay!)
  • evaluating our burn-down rate to predict when TargetProcess thinks we will be (finally) done with the project based on present iteration velocity
  • Our first retrospective
  • Getting set for Iteration 02

As always, questions, comments, and other feedback are welcome.

Happy viewing~!