1 / 26

Visual Studio Team System

Visual Studio Team System. Anton Delsink Developer Tools Technology Specialist Microsoft Gulf, Dubai Anton.Delsink@microsoft.com. announcing. Available November 2007. 3.5. Team System. Business Analyst. Web Clients and XML Web Services. Operations, QA and Help Desk. Third-Party IDEs.

cato
Download Presentation

Visual Studio Team System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Visual Studio Team System Anton DelsinkDeveloper Tools Technology Specialist Microsoft Gulf, DubaiAnton.Delsink@microsoft.com

  2. announcing Available November 2007 3.5

  3. Team System Business Analyst Web Clients and XML Web Services Operations, QA and Help Desk Third-Party IDEs

  4. Example Workflow Bugs Non FunctionalRequirements Dev Team Tasks Use Case Business Analyst Project Manager Test Production Errors Operations Change Requests

  5. Work Items Bugs Active Resolved Closed Closed Resolved Proposed Use Case Tasks Active Description Current State Attachments Who it is assigned to Links to other Work Items Audited history “Work Items are the units of communications within the development team” Customizeable Title

  6. Do We Need to Shift Resources? Bulge in work in process (i.e. in testing) indicates inadequate resources or inadequate incoming quality

  7. Work Item Interface Business requirements captured and managed to enable end-to-end traceability

  8. Web Interface

  9. Visual Studio Team Work Item Types Orange = customized MSF work item type White = new work item type

  10. Exit Criteria

  11. Exit criteria summary

  12. Exit criteria over time

  13. Collecting more information for bugs

  14. Tracking feature progress

  15. Feature progress details

  16. Project Planning Full integration into Microsoft Project fora real-time viewof work items

  17. Version Control Associate work items with each check-in to provide traceability from requirements to code

  18. Team Build • Retooled for 2008 • Build definition UI integrated into VS • Mappings • Triggers • Retention Policy • Target build agents • Manageable build queues

  19. Build Execution BuildDefinition \ TFSBuild.proj

  20. Version Control • Annotate • Folder Diff • Destroy • Get Latest On Checkout • Workspace improvements • Offline improvements • Extranet support for the TFS Proxy • Command line help

  21. Defining a Branching Structure • Should address at a minimum • New feature development and bug fixing—DEV • Product stabilization and readiness for release—MAIN • Sustained, quick-fix engineering for released products—PRODUCTION

  22. Evolving Branching Structure • Balance competing code isolation needs for • new feature development • bug-fixes • stabilization • sustained engineering of releases • May need to consider multiple isolation models

  23. Performance and Scalability • 2008 is 2x faster than 2005 • Any size team, any size project • Deploying broadly across Microsoft • 7k active users, 1,000 projects, 25 TFS instances 2008 Hardware Recommendations

  24. Team System

  25. Agenda • 17:15 – Raffle Draw

  26. Team System Business Analyst Web Clients and XML Web Services Operations, QA and Help Desk Third-Party IDEs

More Related