Home » Blogs » bhardister's blog

Developing a VSTS/TFS 2010 Demo

Now that I have the 2010 beta 1 installed, I'm working on a demo that I will then further expand into walk-throughs for supporting training and VSTS/TFS evaluation by our SW Engineers.

I'm still having problems getting the MS Test and Lab Manager (MTLM) to deploy an environment (I'm a Hyper-V/SCVMM newbee). However, I'm moving on still keeping the fire burning on getting thoses MTLM issues resovled ASAP.

For the demo I'm using a team collection with three team projects assuming a product line (shared code) development model. I'm using the MSF Agile v5 process template.

The outline for my demo is as follows:

  1. Planning a project
    • Program Manager(PM) creates the product backlog using the product backlog spreadsheet in Excel
    • The PM allocates backlog items to a project in the spreadsheet and then creates the project plan using MS Project
    • The Systems Engineer (SE) creates the SRS for the features allocated to the project then uploads this to the document repository on the team portal.
    • From the IDE the Project Engineer (PE) breaks down features into implementable user stories and creates the high-level task plan
    • The PE reviews the project scope with the PM and SE using the Project Dashboard and Reports on the team portal
    • The PM adds an additional feature to the Project. The SE and PE make the needed updates and they all review the revised plan on the portal
    • The SCM Engineer (SCME) sets up the project in version control and creates CI and Test builds
  2. Design
    • The Systems Engineer(SE) develops the activity digram and use case diagrams
    • The Architect reviews the existing code base with the Architecture Explorer (AE) and by reverse engineering sequence diagrams from code
    • The Architect determines the appropriate dependency rules and creates the Layer Diagram to enforce this
  3. Development
    • The SW Lead (SWL) makes the tasks assignments using the IDE
    • Developers begin the cycle of creating unit tests, coding and check-in (integrated with work item updates)
  4. Builds
    • CI and Test builds execute and build reports reviewed
    • The build defintions are reviewed and enhanced to better meet the projects needs
  5. Test-Fix-Verify
    • Testers develop their test cases
    • Testers execute test cases and file bugs
    • Developers debug and apply fixes
    • Testers review the impact of the changes on existing test cases
    • Testers re-run test cases and verify fixes
  6. Management and Release
    • During the project progress is reviewed and stand-ups and other meetings are conducted where the portal, MS project and work item based reports are used to monitor progress and manage risk
    • When system testing is completed and the release date is scheduled, the SCME creates the release branch and build. Acceptance testing is conducted, show-stoppers bugs are fixed and the SW is shipped.