Raleigh Code Camp

Well, it's fall so it must be time for another Code Camp.

I'm going to be presenting a session about using WaTiN in Visual Studio and some best practices for using it with TDD.

The ironic thing is, if I had done the presentation two months ago, it would be much different from the presentation I'm going to give on Sunday. TDD and Agile (which is something we are working on implementing within our group, with an eye toward seeding it out to the other dev groups in our company) has definitely been a learning and growing experience.

Looking back over the two years that we've been slowly changing our processes and development methods, it's been a very eye-opening experience. When we think back to where we were at when we first started, and how we did things back then, we simply say 'Wow, how the heck did we get anything done?'.

We implemented Agile and TDD in small pieces, using each scrum to try things out and see what worked and what didn't. Fortunately if something didn't work, it was not something that prevented us from meeting our backlog items, or effecting our schedule.

So in the past two years, we've never missed a delivery date on our scrums and projects, and we've had to switch projects a few times due to business needs. We've gotten buy in from the Strategic consulting group, QA, Managers, and product owners at our company. The best part is, all the feedback to our team is how much they enjoy working on projects with us compared to the old Waterfall method other groups are still using.

In fact, one of our latest scrums, we actually accomplished something I have never seen before. We completed an entire release to our production application without a single bug for the whole process. That's from initial Product backlog meeting, to the final release which was about 2 months ago. To our group this was the huge pay-off, and it was so awesome to be able to accomplish this without having to kill ourselves. We didn't work a bit of overtime, and we ended up delivering extra backlog items as well.

Anyway, WaTiN was one of those pieces that we tried, and unfortunately we made a wrong assumption or two on how to use it. We've now got it in the right place in our development lifecycle, and picked up the right tool for our true Unit Tests.

I'm just wondering now after reading this over, where our group will be in another 2 years?

Life is Good :)