DEV461 Microsoft Visual Studio 2005 Team System: Advanced Project Management and Reporting Joel Semeniuk Microsoft Regional Director Microsoft MVP – Solutions Architecture INETA Speaker

Questions How many of you… Have a structured SDLC? Use one SDLC for all projects? Formally manage requirements? Are able to trace your requirements through design, implementation, and then build? Predict if you are going to hit your next milestone? Quantifiably demonstrate the effectiveness of your team?

More Questions SCM Policies? Impact of Change? Team Velocity ? ProcessEnforcement? Process Metrics and PKI? Process Constraints ? Accurate Estimates? Jacqui Ackerman Project Manager

Agenda Problems with software development The Project Management role Using Visual Studio Team System to Facilitate the Project Management role Summary

Project Success is Rare %23%49% SucceededChallengedFailed Source: The Standish Group International, Extreme Chaos, The Standish Group International, Inc., 2000 Average cost overrun: 45% Time overrun: 63% Functionality delivered on average: 67% Standish Group Separation of Goal and Function Separation of Business and Technology Poor Team Communication Tracking, Not Managing Either Inflexible or Immature Process No balance between Productivity and Predictability %15%51%

Project Success Factors Executive Support 18 User Involvement 16 Experienced Project Manager 14 Clear Business Objectives 12 Minimized Scope 10 Standard Software Infrastructure 8 Firm Basic Requirements 6 Formal Methodology 6 Reliable Estimates 5 Other5 Source: The Standish Group International, The Standish Report, 2001

A Software Project Team Jacqui Ackerman Project Manager Art Benson Architect Mort Gaines Developer Renee Davis Tester Renee Davis Tester Larry Sykes Product Manager

Agenda Problems with software development The Project Management role Using Visual Studio Team System to Facilitate the Project Management role Summary

The Role of the PM Project Managers should Manage Projects Scope Management Time Management Cost Management Quality Management HR Management Communication Management Risk Management Procurement Management Integration Management (Integrate other areas) Essentially, managing constraints

Most Common Constraints in Software Development People Hire better people 5.5 hours a day, 42 weeks per year Budget and Time Buffer time based on uncertainty Minimize local safety Functionality Hardest to buffer Resources CertaintyBuffer 100%15% 90%25% 80%50% 50-70%100% <50%200% Source: David Anderson, Agile Management for Software Engineering

Project Management Issues Transition from requirements to work products Disconnected team Project status Use of best practices MetricsMiscommunications Identifying constraints Balancing effort Using appropriate tools

Agenda Problems with software development The Project Management role Using Visual Studio Team System to Facilitate the Project Management role Summary

Source: David M. Anderson, Design for Manufacturability: Optimizing Cost, Quality, and Time-to-Market, Second Edition (2001), CIM Press Lessons From Manufacturing

Manufacturing Models Common theories JIT: Reduction of Inventory Total Quality Management: Quality and Conformance Theory of Constraints: Focus on Bottlenecks Lean: Combine most other theories Toyota Production System (Kanban) Six Sigma: Focus on Quality – complementary to Lean These have all impacted our lives Can this apply to the production of software? – YES! Source: David M. Anderson, Agile Management for Software Engineering

Return on Investment ROI = Throughput – Operating Expense Investment ROI1 = Throughput1 – Operating Expense1 Investment ROI1 > ROI

Visual Studio Team System Change ManagementWork Item TrackingReportingProject Portal Visual Studio Team Foundation Server Integration ServicesProject Management Process and Architecture Guidance Dynamic Code Analyzer Visual Studio Team Edition Software Architects Static Code AnalyzerCode ProfilerUnit TestingCode CoverageTeam Explorer (includes Team Foundation Server CAL)Visual Studio Professional EditionLoad TestingManual TestingTest Case ManagementApplication DesignerSystem DesignerLogical Datacenter Designer Visual Studio Team Edition Software Developers Visual Studio Team Edition Software Testers Visual Studio Industry Partners Team BuildClass Designer (in Visual Studio Standard Edition and higher) Deployment DesignerVisio for Enterprise Architects (in MSDN Premium Subscription)

How Visual Studio Team System Will Help Addresses common constraints leads to greater throughput and higher quality Work to identify and mitigate constraints within a system Works to help Minimize operational costs Increase throughput Minimize investment Make your projects more repeatable Make your projects more predictable

MSF Agile – Out of the Box Reports Bug Rates Code Complete report Dev/QA Bug Counts Dev/QA Work Exit Criteria Status Issues My bugs Requirements Stability Requirements Stability over Time Work Progress Work Progress over Time Generic Charting Builds Team Productivity Test Effectiveness Test Effectiveness over Build Code Coverage by Test Cases Regressions Result History for Test Summary Build (test summary) Test Failures By Owner without Bugs Test Failures with Closed or Resolved Bugs Test Failures without Bugs Tests Passing with Active or Resolved Bugs Build Details report Load Test Comparison report Load Test Selection report Load Test Summary report

Reports Readily Available

Work Item Tracking Reporting Warehouse SQL Server ReportingServices Source Code Control Partner Tool A Reporting Warehouse Object Model Microsoft Excel CustomReporting BuildDatabase Work Item Adapter Source Code AdapterAdd-onAdapterTest/BuildAdapter

Borland CaliberRMT Integrated into Visual Studio Team System Provides a rich requirements management environment Full Requirements Management Impact Analysis, Prioritization, and Fulfillment Analysis ReportingCollaboration Facilitates flow of requirements between business analysts, developers, testers, and other business stakeholders

CaliberRMT Integration

Key Features: CaliberRMT Projects Map to Team System Projects Work Items are Visible Within CaliberRM Requirements are Visible within Team System Data Warehouse Integration Full CaliberRM Traceability Support Trace from Requirements to Test Scenarios

Requirements are Key Team System does not provide extensive Requirements Management features Requirements Engineering is the heart of Process Improvement Team Communication is essential to good successful requirements management Full Requirements Tractability Essential Demonstrates Team System as an Integration Platform

Agenda Problems with software development The Project Management role Using Visual Studio Team System to Facilitate the Project Management role Summary

Best Practices Summary Establish traceability Create work breakdown structure Strive for transparency Manage communication Manage risk Integrate change control policies Customize your process Quality early and often

Visual Studio Team System & Project Management Productive AND Predictable Teams Process automates transitions between tools and the people Your team is on the same page You can view the data the way you want Using the tools you want While others view their data in their tools Status meetings become tactics meetings NO: Where are you on that? NO: When do you think you’ll be done? YES: How can we address the road blocks in your way?

Resources Visual Studio Team System Site: Project Management Newsgroups: s/project manager s/project manager MSF:

Resources Get these Books!!!

NET Charity Celebrity Tech·Ed Auction Like what you see? Bid for 1 hour of my consulting time on eBay and all the funds go to charity! 100% of your bid will go to Tsunami Relief Effort in Aceh, Indonesia

Your Feedback is Important! Please Fill Out a Survey for This Session on CommNet

© 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.