Efficient Software Development with Visual Studio Team System

Slide 1: Efficient Software Development with Visual Studio Team System Richard Bushnell Consultant richard.bushnell@gmail.com January 10th, 2008

Slide 2: Agenda  Introduction  Project Management with VSTS  Day-to-day Development  Testing  Reporting  Training  Q&A 2

Slide 3: Parts of Team System  Visual Studio Team Suite  Team Explorer  Various Editions  Project Portal  Guidance  Reports  Administration  Security  Data Warehouse 3

Slide 4: Why use Team System?  Communication  Transparency  Software Development Process  Integration 4

Slide 5: Projects Roles  Process Specific  VSTS Editions  Architecture  Developement  Database  Test  Project Manager  Roles can be shared 5

Slide 6: Better Communication  Obvious benefits  Faster, more dynamic teams  Higher quality  Ownership  VSTS provides:  Various views of data  Data-entry integrated in IDE  Policies for automation  Notifications  Portal tools, e.g. Calendar 6

Slide 7: Software Development Process  Process provides  Structure  Understanding  Discipline  Alternatives in VSTS  MSF for Agile Process  MSF for CMMI  Scrum  Integrated into  Project items  Portal and reports  Project Guidance 7

Slide 8: Transparency for the Customer  Better understanding = Happier customers  VSTS provides integrated  Tracking  Reports 8

Slide 9: Team System Integration 9

Slide 10: Project Management - Planning  Definition of Scenarios  Assignment of Tasks  Planning of Iterations  Integration with MS Project and Excel 10

Slide 11: Planning and Definition of Work Items  Inside Visual Studio  MS Project  MS Excel 11

Slide 12: Types of Work Items  Bugs  Tasks  Scenarios  Quality of Service Requirements  Risks 12

Slide 13: Development  Source Control  Standards, Guidelines  Quality Control  Work Item Tracking  Builds 13

Slide 14: Source Control  Check in/out  Why?  New features  Workspaces  Policies  Branching  Example – policies applied to check-in 14

Slide 15: Standards and Guidelines  Best practices from MS built-in  E.g. Naming best practices  Can be automated with check-in policy  Portal Site  Document repository 15

Slide 16: Software Quality  Bug tracking  Code analysis  Testing  Reporting 16

Slide 17: Work Item Tracking  Developer adds details at check-in  Policies can enforce rules  Items can be linked  Changesets  Example  Overriding policy 17

Slide 18: Building with Team Server  Build server fully integrated  NEW - Continuous Builds  Latest technology  Integrated testing and quality checks  Example  Set up a new build  Run on demand 18

Slide 19: Testing  Unit Testing  Performance Testing 19

Slide 20: Unit Testing  Done by developer as he goes  Work Item or Task defines initial test  Unit test tests each type in code 20

Slide 21: Unit Testing in VSTS  Test projects  Test templates and wizards  Test Runners  Check-in policies  Build integration  Best practices  Don't generate tests  Internal vs Public 21

Slide 22: Quality Assurance Testing  Performance Testing  Load Testing  Manual Tests  E.g. Integration tests, User acceptance  Test-data generator  Demo  Creating and running a unit test 22

Slide 23: Reports for Project Management  Transparency  Development to project management  Project management to customer  Integrated in Project Portal  Actual Quality versus Planned Velocity  Unplanned Work  Velocity  Bug Rates  Bugs by Priority  Reactivations  Quality Indicators  Remaining Work 23