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