• Save
Efficient Software Development with Visual Studio Team System 2008
Upcoming SlideShare
Loading in...5
×
 

Efficient Software Development with Visual Studio Team System 2008

on

  • 1,726 views

An introduction to Microsoft Visual Studio Team System 2008. The focus is on good software development practice using the suite of tools.

An introduction to Microsoft Visual Studio Team System 2008. The focus is on good software development practice using the suite of tools.

Statistics

Views

Total Views
1,726
Views on SlideShare
1,723
Embed Views
3

Actions

Likes
0
Downloads
0
Comments
0

1 Embed 3

http://www.slideshare.net 3

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Efficient Software Development with Visual Studio Team System 2008 Efficient Software Development with Visual Studio Team System 2008 Presentation Transcript

  • Richard Bushnell Consultant [email_address] January 10 th , 2008 Efficient Software Development with Visual Studio Team System
  • Agenda
    • Introduction
    • Project Management with VSTS
    • Day-to-day Development
    • Testing
    • Reporting
    • Training
    • Q&A
  • Parts of Team System
    • Visual Studio Team Suite
      • Team Explorer
      • Various Editions
    • Project Portal
      • Guidance
      • Reports
    • Administration
      • Security
      • Data Warehouse
  • Why use Team System?
    • Communication
    • Transparency
    • Software Development Process
    • Integration
  • Projects Roles
    • Process Specific
    • VSTS Editions
      • Architecture
      • Developement
      • Database
      • Test
    • Project Manager
    • Roles can be shared
  • 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
  • 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
  • Transparency for the Customer
    • Better understanding = Happier customers
    • VSTS provides integrated
      • Tracking
      • Reports
  • Team System Integration
  • Project Management - Planning
    • Definition of Scenarios
    • Assignment of Tasks
    • Planning of Iterations
    • Integration with MS Project and Excel
  • Planning and Definition of Work Items
    • Inside Visual Studio
    • MS Project
    • MS Excel
  • Types of Work Items
    • Bugs
    • Tasks
    • Scenarios
    • Quality of Service Requirements
    • Risks
  • Development
    • Source Control
    • Standards, Guidelines
    • Quality Control
    • Work Item Tracking
    • Builds
  • Source Control
    • Check in/out
      • Why?
      • New features
    • Workspaces
    • Policies
    • Branching
    • Example – policies applied to check-in
  • 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
    • Trivadis can offer guidelines too
      • E.g. Flat or 1 Project per department?(BI, DWH, WWW, Core)‏
      • Naming conventions for Namespaces, Projects and Files
  • Software Quality
    • Bug tracking
    • Code analysis
    • Testing
    • Reporting
  • Work Item Tracking
    • Developer adds details at check-in
    • Policies can enforce rules
    • Items can be linked
    • Changesets
    • Example
      • Overriding policy
  • 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
  • Testing
    • Unit Testing
    • Performance Testing
  • Unit Testing
    • Done by developer as he goes
    • Work Item or Task defines initial test
    • Unit test tests each type in code
  • 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
  • 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
  • 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