Monday, July 6, 2009

A Two Day Event: SDLC in a Box on July 15-16, 2009

This 2 day event will focus on application life-cycle management, we will review how one may leverage TFS and VSTS on a project, from initial conception through requirements gathering, design, development, testing, build & review processes. We will demonstrate integration with non-Microsoft development and best-of-breed partner solutions & offerings for Visual Studio 2008 Team System.

For additional information please see

Target Audience:
This two day sessions is targeted for Developers, Architects, Project Managers, DBAs and Business Analysts looking for ALM and researching Team Foundation Server.

1. Alexei Govorine:
Co-Founder of the
Central Ohio ALM Group
ALM/.NET Practice Manager for Quick Solutions
2. Mike Gresley:
MS SLG Dev Tools team
David Baliles:
MS SLG Dev Tools team
Co-Founder of the SDLC in a Box program

Capitol Annex Bldg: Room 171, 700 Capital Avenue Frankfort, KY 40601

July 15-16, 2009 from 9-4:30 PM

Registration Link:

Draft Agenda of the event topics:
Day 1:

  1. Introductions
  2. SDLC in a Box: Background
  3. Application Lifecycle Management
  4. VSTS & TFS Overview
  5. Customization / Setup
  6. Team Explorer Overview (Security, Collaboration, Alerts, Source Control)
  7. Work Item Management (Tools for Managing Requirements)
  8. Architecture

Day 2:

  1. Database
  2. Development
  3. Unit Testing & Test-Driven (TDD)
  4. Code Promotion: Building & Deploying code
  5. Functional Testing
  6. Branching & Hotfix Demonstration
  7. Reports
  8. Q&A
  9. (optional) Lap Around VSTS 2010


Sarin Shah said...

Hi Alexey,

I have a question regarding load testing. Is sql server database or database on local box required in order to run LOAD TEST? said...

Well, the answer is Yes and No.
Technically you do not need SQL Server in order to run Load Tests, but SQL Server is needed for storing Load Test Results, you may elect not to store the data or you can configure a remote SQL Server to hold the Load Test Results database. Here is a good article that outlines your option with regards to SQL Server configuration:

hope that it helps