The rest of Day one
After the Keynote speech there was just enough time to grab a quick drink of coffee ( very strong coffee, obviously Microsoft do not want anyone snoring in the sessions ) before it was time to head to the next breakout session.
For those who have not attended TechEd, you are provided with a ring bound book of the available sessions with a brief breakdown of the subject matter. It is necessary to be quite selective of the sessions you attend as there are in general around twelve break out sessions, and five or so Interactive sessions going on at once.
Having decided on two possible choices I headed for the session entitled Unified Communications for Developers: Building Communications into your Applications As we at Esendex are in the business of business communication it seemed a fair choice. I sat through 20 minutes of the presentation and realized that the subject matter was really way to higher level to be of any real interest especially as the presentation seemed to revolve pricipally around the Sharepoint tool set, not one that we use. I therefore decided to drop into my second option a presentation by Bob Beauchemin, Best Practices for Optimizing Service Based Code in SQL Server 2005 and Beyond. Unfortunately for me by the time I had found the session and sat down Beauchemin was well into his stride and I was out of my depth not being a DBA. I should add that I found Beauchemin's comments about the slowness of Powerpoint and his dislike graphical visualisations somewhat tiresome. Rearrange the words Workman, tools, blames, his and bad.
Session Two I felt simply had to be better, and i am glad to say was significantly so.
Since signing up to attend TechEd I had been looking forward to attending any of the sessions dealing with Agile development methodologies. Session Two for me was all about the presentation by Roy Osherove Agile Development with Team System. It was an excellent session, humorous in parts, informative and well delivered. At Esendex we use the Extreme Programming methodology, and though Osherove concentrated mainly on SCRUM the principals are pretty much the same. Simply put Agile development requires that the work to be completed is broken up into small easily achievable pieces referred to as Sprints in SCRUM and Stories & Tasks in Extreme programming. Another key factor is the assumption that the customers requirements will change. If the requirements do change whilst a task/sprint is in progress, it should be put back into the product backlog ( list of outstanding work ) to be refactored. This should prevent 'mission creep' from occurring.
In a nutshell the support Visual Studio 2008 offers Agile development teams seems to be a significant improvement with the 'full house' of MSBuild ( not without its flaws see 'partially successful builds' ) source code versioning and unit testing (MSTest). These tools will allow you to write up the required tasks, monitor any changes to the source related explicitly to those tasks when checked in, build the source when any changes are made ( fingering any developer who checks in dodgy code), run the unit tests and also provide descriptive and graphical representations of development progress.
Osherove finished his session with a song.. yeah really and though his singing voice may not be the greatest the lyrics to the the theme of "Every breath you take" by the Police had everyone laughing.