1. Neno Loje MVP für Team System www.teamsystempro.de mit Team Foundation Server 2010

2. Einleitung Application Lifecycle Management Visual Studio Team Foundation Server 2010 Microsoft Solutions Framework (MSF) Projektplanung Projektsteuerung & Transparenz Einbeziehung aller Projektinteressierten Anforderungen

4. Plan Task 1 Task 4 Task 3 Task 2 Value-upWork-down In traditional project management tasks are decomposed into items and checked off as completed Value-up methods deliver incremental value for the customer to evaluate each iteration

5. Team System

6. Business Analysts Requirements Management QoS Management Requirements Analysis Architects Architecture Modeling Analysis and Design Design for Deployment UI Designers UI Design UI Prototyping UI Flow Modeling DBAs Database Design Database Source Control Database Test Data Gen Developers Code Analysis Unit Testing Version Control Testers Test Case Management Manual Testing Load Testing Automated Testing Operations Customer Support Infrastructure Architecture Infrastructure Deployment Project Managers Project Planning Task Assignment Bug Tracking Development Executives Portfolio Management Project Organization Stakeholder Communication

8. Create and track tasks, scenarios, requirements Assign work across team Friction-free updates for team Use workflow to enforce process Work tracking integrated with source control, builds, tests Multi-dimensional record of your project over time

9. No support for hierarchy No tools for quickly managing your backlog No tools for managing team or individual capacity

10. Top-to-Bottom Traceability Requirements Traceability Parent/Child Relationships Rollup and Drilldown Agile Planning Built-in product backlog mgmt Built-in iteration planning Easily customizable Great Project Integration Full dependency linking Full round-tripping w/ TFS

11. Planning a Sprint with Team Foundation Server 2010

13. Reports indicate how the project is trending How many work items are remaining? How many unplanned work items do we have? (scope creep, or dark matter) Which requirements have been tested? How quickly are we resolving and closing work items? How many bugs are being re-activated? …

14. Built-in reports may not answer all questions Customizing process templates can break the built-in reports SQL Server Reporting Services very sophisticated… … but requires specialized skillset. Even with those skills, takes too much effort. Ad hoc reporting against the OLAP cube is possible… … but the schema can be tricky to master.

15. Reporting for mere mortals Generate reports from queries Manipulate data with Excel Friendlier OLAP cube Share the knowledge Embed reports via MOSS

16. Building and Customizing Reports with Team Foundation Server 2010

18. Stakeholders play a vital role in the successful delivery of an agile development project. Role of stakeholders: Project funding Provide requirements Prioritize work Review deliverables Provide feedback Change their minds

19. What is the team building? When will it be done? Is the team on track? What obstacles is the team facing? How do I file bugs? How do I request features?

20. Information-rich dashboards Roll-up reports show KPIs Drill-down for further analysis Quickly customizable Easy interaction with developers Web-based bug filing Web-based feature requests Track status of bugs / features

21. A Stakeholderss view of Team Foundation Server 2010

36. Team Explorer Web Access MTMExcelProject Is web based? Integrated with Visual Studio? Easy for Developers? Easy for Stakeholders? Can bulk-edit work items? Can re-prioritize work items? Can help compute priority? Requires a CAL? Übernommen von: Richard Hundhausen, www.accentient.com

37. Integration with… … MS Outlook: TeamCompanion ($)TeamCompanion … MS Word : Word2TFS (free)Word2TFS … Mind Manager: Requirements Mapper ($)Requirements Mapper

38. "Basic Configuration" Reporting & Project Portal optional 64-bit, DC, Client OS (Windows Vista & 7) Voraussetzungen (Server): SQL Server 2008, WSS 3.0 SP2 HDD free space 1.5x size of current TFS databases (Upgrade) Voraussetzungen (Client): Office 2007 SP1, Windows XP SP3 (oder höher) VS 2010 (oder VS 2005/2008 mit SP1 und Patch) 1 TFS und 1 CAL in jedem VS mit MSDN

39. Team Foundation Server 2010 Neue Work Items (z.B. User Story, Test Case, etc.) Hierarchische Work Items Diverse Work Item-Verknüpfungstypen Excel-Sheets für Projekt-/Iterationsplanung Berichte von Work Item Queries generieren Berichte & Dashboards

40. Überblick Visual Studio 2010 Quick Reference GuidanceVisual Studio 2010 Quick Reference Guidance (deu.) Installation, Konfiguration & Administration Vorbereiten auf den Team Foundation Server 2010Vorbereiten auf den Team Foundation Server 2010 (deu.) Team Foundation Installation Guide for Visual Studio Team System 2010Team Foundation Installation Guide for Visual Studio Team System 2010 (engl.) Visual Studio 2010 TFS Upgrade GuideVisual Studio 2010 TFS Upgrade Guide (engl.) Visual Studio 2010 and Team Foundation Server 2010 VM FactoryVisual Studio 2010 and Team Foundation Server 2010 VM Factory (engl.) TFS Integration PlatformTFS Integration Platform (engl.) Visual Studio 2010 Licensing White PaperVisual Studio 2010 Licensing White Paper (engl.) Anforderungsmanagement Visual Studio 2010 Team Foundation Server Requirements Management GuidanceVisual Studio 2010 Team Foundation Server Requirements Management Guidance (engl.) Architektur System Modellierung, System Analyse sowie deren Erweiterbarkeit und Integration mit dem Visual Studio Team Foundation Serverdem Visual Studio Team Foundation Server (deu.) Versionsverwaltung / Konfigurationsmanagement Visual Studio TFS Branching Guide 2010Visual Studio TFS Branching Guide 2010 (engl.) Unternehmensweit einheitliche Build-Prozesse abbilden mit Microsoft Visual Studio 2010Unternehmensweit einheitliche Build-Prozesse abbilden mit Microsoft Visual Studio 2010* (deu.) Testen Effiziente Qualitätssicherung und Testen mit Microsoft Visual Studio 2010Effiziente Qualitätssicherung und Testen mit Microsoft Visual Studio 2010 (deu.) Prozesse & Vorgehensmodelle Agile Softwareentwicklung mit dem Visual Studio Team System nach ScrumAgile Softwareentwicklung mit dem Visual Studio Team System nach Scrum (deu.)

41. Im Anschluss oder per E-Mail an: neno@teamfoundationserver.de