1. Roger Boesch Technology Solution Professional - Visual Studio Team System blogs.msdn.com/rogerboesch Microsoft Schweiz GmbH

2. The software development process Process layer Planning layer Working layer Implementation in Team System Work Item types Features Feature planning Control of progress Usage statistics of TFS

3. ScenariosScenarios ValuePropositionsValuePropositions ExperiencesExperiences FeaturesFeatures FeaturePlanningFeaturePlanning ImplementationImplementationEstimationPlaninngEstimationPlaninng Checkpoint #1 Design Design Checkpoint #2 Demo Demo IsolationIsolation Release(s)Release(s) Iteration(s)Iteration(s) Feature Crews QualityGatesQualityGates QualityGatesQualityGates QualityGatesQualityGates

4. Features Experiences Value proposition Main objectives Scenario Value Prop ExpFeature ExpFeature Value Prop ExpFeature

5. Scenarios The (Main-)business objectives Goals of the division for a release Value propositions The value from customer perspective Ask always: Why should the customer pay for it? A scenario contains multiple value propositions Experiences Business level use case What experience do we need that a customer realize the value Epic story

6. Features The feature we need to implement, to enable the experience to release the value props to meet the divisional goal Features are the break-down of the work. Feature crew Independent (isolated) team contains multiple members Interdisciplinary (all roles needed to be indipendent) Fully responsible for an assigned feature Goal A feature should be possible to implement in 4-6 weeks Quality gates Ensures constant quality DevDiv: „More then 3000 persons working on over 700 features“

7. Create a branch to ensure the isolated work Checkpoint #1 = Design Show how the feature should be implemeneted Checkpoint #2 = Functionality Show how the feature is implemented If a feature is complete, all the changes from the main branch will be integrated into the feature branch Before a feature branch is merged into the main branch, a set of quality gates must be reached. (Ex. >= 70% code coverage through automated testing) When all quality gates are reached, the feature can be merged. Quality gates ensuring, that the main release is always in a (nearly) stable state

9. Security PlanStatic Code AnalysisCode CoverageNo performance regressionsLocalization testingAPI reviewsAll bugs fixed

10. Process and tools support individuals, teams and organizations frictionlessly and transparently “How we use our own tools to develop software”!

11. Value Propositions Scenarios are implemented as fields (not as WIT) Connection to experiences through links Text field containing prosa text Experiences Connection to value propositions through links Connection to features through links Features Connection to experiences through links Definition fields (Ex. planning, progress etc.) Text field with a short description OnePage link (Url) containing more details

15. Excel Sheet with values from TFS The data from the estimation is delivered by TFS The input is done in different other tools Advantage: Central project data warehouse (single source) Order of the features is top-down (ranking) Compare with team capacity Yellow>= 70%, Red>= 100% Quick overview what’s possible and what’s not possible Yellow/Red game: Find the cut-line in the feature list (playground) Example: Move larger features down, but move also multiple smaller features above the cut-line Try to remove most of the yellow and red entries

17. Start- and end dates Feature start Commitment of checkpoint #1 (Date) Estimation checkpoint #2 (Date) and feature end (Date) Checkpoint #1 Commitment of checkpoint #2 (Date) and Feature end (Date) Checkpoint #2 Commitment of feature end (Date) Progress in percentage Open and closed work (Features) in percentage Risk level Green: Estimated date would be reached Yellow: Estimated date is not sure (Risk) Red: Estimated date will not be reached Prosa text contains the state of the feature crew

20. Developer divsion Users 4500 registered users Work items 490‘000 work items (All types) 290‘000 attached files Version control 370 Mio. files 560‘000 ckeck-in‘s 57‘000 shelvesets 15‘000 workspaces

21. © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.