• Like
  • Save
Visual Studio ALM 2010 And The PMO V 1
Upcoming SlideShare
Loading in...5
×
 

Visual Studio ALM 2010 And The PMO V 1

on

  • 1,276 views

 

Statistics

Views

Total Views
1,276
Views on SlideShare
1,269
Embed Views
7

Actions

Likes
2
Downloads
93
Comments
0

1 Embed 7

http://www.slideshare.net 7

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Visual Studio ALM 2010 And The PMO V 1 Visual Studio ALM 2010 And The PMO V 1 Presentation Transcript

    • IT’s Top Priorities - Today 2009 2008 2007 2006 Improving Business Processes 1 1 1 1 Reducing Enterprise Cost 2 5 2 2 Improving enterprise workforce effectiveness 3 6 4 * Attracting and Retaining new customers 4 2 3 3 Increasing the use of Information or Analytics 5 8 7 6 Creating new products or service (innovation) 6 3 10 9 Targeting customers and markets more effectively 7 9 * * Managing Change initiatives 8 12 * * Expanding current customer relationships 9 7 * * Expanding into new markets or geographies 10 4 9 * Source: Gartner, “Meeting the Challenge: The 2009 CIO Agenda”
    • Companies are… Looking to Reducing Increase But…Businesses are NOT slashing IT Capital Productivityspending in a knee-jerk response Investments They ARE looking to IT for help: Raise Enterprise Effectiveness Restructure for Productivity and Agility Reducing Modernize Infrastructure Operating Manage Change Costs Restructuring Introducing New Products/Services to Gain Market Share Meeting the Challenge: The 2009 CIO Agenda – Gartner Research
    • Am I getting the most value for my investment?
    • Which project is most at risk? What can we do? Are we in compliance?
    • Is it on track? Is it on budget?
    • Is it on track? Are we meeting the customer need?
    • Plan Projects Trace Requirements to Results Report Project Status to Stakeholders Standardize and Improve the Team’s Process Manage the Portfolio
    • • Provide tools for development teams to get work done – maximum productivity with no red tape • Enable valuable collaboration between the PMO and the dev team – alignment, iteration, continuous stream of value • Give your leadership/PMO the ability to make effective decisions with full transparency and accurate up to date information
    • CH2MHill. Grange Insurance.
    • Piraeus. Thomson Reuters. “
    • 20 Microsoft Confidential
    • We start with the team’s current list of requirements
    • Easily enter new requirements – using web dashboards
    • All stored on master TFS server - flow back into Visual Studio for dev team
    • …The team can align their plans by breaking down the requirements into work…
    • …continuing until all the requirements are broken down successfully…
    • The Project Manager opens the same plan from TFS into MS Project for easy scheduling…
    • She can use the new Team Planner view to quickly view the team workload…
    • …assign tasks…
    • …and level out the work…
    • Project’s new “manually scheduled tasks” gives the Project Manager control over tasks that are commitment based while still supporting easy auto-scheduling of the rest.
    • …or we can do it all automatically… 
    • …and my whole team is load- balanced, taking dependencies into account
    • Finally, in VS 2010 all my information from Project is back in TFS, for easy coordination between the dev team and the PMO
    • 36 Microsoft Confidential
    • All requirements/tasks/… always stored on same master TFS server for a single source of truth The team can use the Agile Planning workbooks to assign work…
    • …and use a simple view to load balance the team
    • Planning can account for out of the office time
    • The team can easily flip adjust the work assignments based on capacity…
    • …until the team is load- balanced. The team is ready to commit to this work.
    • During development, a built-in burndown provides visibility into the team progress
    • 44 Microsoft Confidential
    • Again, starting with a list of requirements
    • I can run queries which will tell me which requirements are being tested…
    • …and which requirements are not being tested!
    • That same set of requirements is pulled …and testers can through into the then easily add/link testing tools… the right test cases to verify their implementation
    • When the tester runs tests, new bugs are automatically created with trace relationships to the right test cases and requirements
    • …and those bugs automatically flow back in Visual Studio, enabling team collaboration...
    • The development team views the bugs in their tool, Visual Studio
    • From the bug, it is easy to see the failed test case
    • The developer can drill into details on the test case to resolve the issue
    • Again, same set of requirements… With quality and progress traced and reported back, for complete end to end traceability
    • Everyone has transparency into the overall quality
    • 56 Microsoft Confidential
    • Several dashboards provide additional transparency, including team progress Reports are all just Excel, so they’re simple to open and customize
    • The dashboards are interactive. Web parts give direct access to TFS data….allowing stakeholders to communicate to the team
    • Logging issues and checking on their progress
    • My team can manage all their work from a personal dashboard
    • PMO Project Server data, metrics, work products, TFS models, CMDB ALM policies, Ops compliance Management Packs, Policy Templates, Capacity Models Tested Configured VMs Datacenter Models, Automated Diagnostics
    • Late in the project she and the CIO perform a data-driven analysis of the entire portfolio to review what is meeting goals, including prioritizing incoming demand What is cool: Project server provides teams with a way to get a handle on the tons of projects they have running, to quantitatively assess business value.
    • They confirm the value of the current project, which will help them prioritize resources and budget for the upcoming quarter What is cool: Unified quantitative view of the business value of projects – priority, cost, value, resources & status
    • The Project Manager creates a new Team Project and associates the project plan the VSTS project
    • The PM reviews the full portfolio of projects across the enterprise. All other projects are on track but this project is visibly in trouble. What is cool: VSTS-Project Server integration gives you top to bottom transparency and unified project management. Project Server rollup pulls key dev project stats (bugs, etc.) from VSTS
    • • Standardize • Full planning tools • End to end The Future TFS 2010 TFS 2008 process with with both MS business process templates Project and Excel alignment, • Define metrics to Agile Planning balancing and manage projects • Full requirements tracking the entire • Utilize CMMI or traceability project portfolio Agile best practices • Simplified • Complete out of the box Transparency with integration from • Receive accurate reports and operations to status from the dev SharePoint development, team dashboards flowing production issues quickly and seamlessly back to the software team
    • • Scrum and TFS 2010 • Getting Started with Sarbanes-Oxley (SOX) • Managing Requirements with TFS 2010 • Reporting with TFS 2010 … please contact Tom Sanchez for details and further discussions/presentations/Pilots
    • © 2009 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.
    • 70 Microsoft Confidential
    • 71 Microsoft Confidential
    • Examples of Analysis by Leadership Where should I force load-balancing/risk management conversations? Weekly bug fix rates by team 6/3/2009 - 6/10/2009 - 6/17/2009 - 6/24/2009 - Current Weeks to fix Team 6/9/2009 6/16/2009 6/23/2009 6/30/2009 backlog backlog* TeamLab 22 32 23 95 406 9.4 WPF and SL Designer 74 63 46 106 583 8.1 Visual Studio Platform (VSP) 196 191 198 227 1416 7.0 ISV and Native Tools (VC) 93 96 104 119 714 6.9 Visual Web Developer 91 74 123 82 540 5.8 TeamEng 209 197 121 255 1041 5.3 TeamTest 101 128 153 340 875 4.8 TeamArch 150 125 175 123 689 4.8 BizApps 93 89 107 170 533 4.6 TFS 267 304 211 420 1157 3.9 Visual Studio Languages 142 116 123 130 473 3.7 PCP 47 82 94 72 112 1.5 Bug distribution Team People Bugs Bugs/person VSP 71 1257 17.7 Cider 30 521 17.4 VWD 40 522 13.1 TeamArch 61 632 10.4 TeamTest 79 712 9 ISVNT 82 636 7.8 TeamEng 97 706 7.3 TFS 132 919 7 TeamLab 43 274 6.4 VSL 79 481 6.1 BizApps 81 483 6 PCP 55 117 2.1
    • Examples of Analysis by Leadership Have we successfully controlled Dev10 Beta 2 DCRs?
    • Examples of Analysis by Autonomous Teams What areas should we manage aggressively?
    • Examples of Analysis by Autonomous Teams Are We Converging on DCRs? Where are Problem Areas?
    • Examples of Analysis by Autonomous Teams How Are Crews Doing Against Exit Criteria?
    • Examples of Analysis by Autonomous Teams Late in Dev10 Development How are We Progressing on Feature Crews?
    • Automated Exit Criteria Tracking
    • 83 Microsoft Confidential
    • I can run queries which will tell me which requirements are being tested…
    • …and which requirements are not being tested!
    • A tester working in the VSTS Test and Lab Manager can see the requirements and create their tests
    • The tester runs the tests
    • Which starts up the Microsoft Test Runner…
    • …stepping the manual tester through each test step
    • Rich, actionable bugs can be created right from the test
    • Automatically capturing all the environment data
    • February 2008 “Trends 2008: Project-Based Solutions”