Archive

Archive for February, 2006

Slides from Atlanta User Group – Testing for Developers

February 27th, 2006

That was another enjoyable night. I must give a big thanks to all the hundred or so
people that showed up to hear me talk again. If anyone would like the slides please
click here
.

Paul Lockwood Atlanta, Presentations

Book Review: VS 2005 Team System by Richard Hundhausen

February 24th, 2006

All you really need to know is the following

  • This is one of the best written technical books I have ever read, and is an excellent introduction to Team System
  • If you have been working with Team System for some time this book is unlikely to teach you much, it is purely an introduction

The approximately 300 pages are filled with riveting content (disclaimer: I am a big fan of formal processes), and only uses screenshots where necessary. The book is far from another big font/ screenshots-on-every-page Barnes and Nobel shelf filler. As you may expect the book begins with an introduction to Team System, Test Server and its related Client Applications. Beyond these chapters, things get really interesting as Richard explains the different major roles in team system, which as we know related to different skus of Visual Studio. For each major role Richard covers the tools provided in that area, and major features. It was interesting to see that Testers do not get much in this release of Team System – this did not surprise me given Mercury’s dominance in this area. It was interesting to read in the latter parts of this book that Mercury are planning add-ins for VS2K5. Note: Developers are looked after in the testing department, but your SQA team does not get much.

Part three of the book covers MSF 4.0, MSF-Agile and MSF-CMII. Personally I think this material is better suited to a classroom, as I found it difficult to keep up with all precise terminology used by each approach. After re-reading the first pages again and again I ended up skim reading most of part three.

Interestingly the best part of the book is the only part I can criticize. Appendix A is ‘A Day in the Life of Team System’; it presents a summary of using Team System on a three month long project. This section was very helpful to me in tying the whole process together, but I just feel it was not presented in the best manner. With a pen I highlighted the key terms in the storyboard to show what part of team system was used when, but I feel the waffle outweighed talk about team system. Most people reading this book with have experience with many projects already and we just want a rapid summary.

All-in-all this is possibly the best technology book I have read since Code Complete and Writing Secure Code. Much of the material in this book will be out of date sometime next year when I expect we’ll see the second version of Team System, but I believe Richard is capable of writing a classic book that will stay on our bookshelves alongside Steve McConnell’s work.

Paul Lockwood Book Review

See you at Mix06

February 22nd, 2006

Mix means developers, designers and business professionals at the same conference.
Most devs I know are waiting for TechEd/ PDC, but I jumped at the chance to ‘win’
my ticket at the Architect’s meeting today (It will cost me about $400 for the flight +
hotel room). Taking a full week off week is too costly, and I am not quite networked
enough to justify attending PDC or TechEd. Most people I know only go to
them network, and barely see a presentation. I think I’ll enjoy the smaller gathering
in Vegas, where I hope to see some great people speak including the following who
are either major stars or I follow their web blog. Maybe unlike the bigger events
I’ll get have a beer with one or two of them.

http://mix06.com/

Superstar speakers: Hopefully I’ll get in the same room as them!
 William (Bill) H. Gates

 Tim O’Reilly

Famous among the geek set:
 Nikhil Kothari
 Rob Howard
 Jeffrey MacManus
 Joe Stegman
 Brad Abrams
 Scott Guthrie
 Doug Purdy
 Clemens Vasters
 Jeremy Zawodny

I’ll be sure to Google MSN-oogle [Paul remembers which company gave
him the ticket] everyone else speaking and see what I could otherwise be missing out
on.

Paul Lockwood Other