Visual Studio 2005 Team System: Software Project Management Hans Verbeeck [email protected] http://msdn.microsoft.com/teamsystem Visual Studio Visual Studio Visual Studio Team Architect Team Developer Team Test Application Designer Dynamic Code Analyzer Load/Web Testing Logical Datacenter.
Download ReportTranscript Visual Studio 2005 Team System: Software Project Management Hans Verbeeck [email protected] http://msdn.microsoft.com/teamsystem Visual Studio Visual Studio Visual Studio Team Architect Team Developer Team Test Application Designer Dynamic Code Analyzer Load/Web Testing Logical Datacenter.
Visual Studio 2005 Team System: Software Project Management Hans Verbeeck [email protected] http://msdn.microsoft.com/teamsystem Visual Studio Visual Studio Visual Studio Team Architect Team Developer Team Test Application Designer Dynamic Code Analyzer Load/Web Testing Logical Datacenter Designer Static Code Analyzer Manual Testing Deployment Designer Code Profiler Test Case Management Unit Testing Code Coverage Class Designer Visio and UML Modeling Team Foundation Client (includes CAL) Visual Studio Professional Edition Visual Studio Team Foundation Version Control Team Reporting Integration Services Team Build Work Item Tracking Project Portal Project Management Visual Studio Industry Partners Process and Architecture Guidance Visual Studio Team System A Software Project Team Jacqui Ackerman Project Manager Art Benson Architect Mort Gaines Developer Larry Sykes Product Manager Renee Davis Tester Following Best Practices What process is the team using? Where is the real data? Process “manuals” quickly become out-of-date Process alone does not bridge gaps Today - Project Managers Bridge Gaps Jacqui Ackerman Project Manager •Between People •Between Tools Copy and paste Status meetings Translating data Transferring work Chasing down loose ends The Problem with Process Productive Predictable Repeatable Why can’t process help productivity? The Rules Have Changed From Anticipation (Define, Design, Build) AdventureWorks ProjectPlan Jul 2004 ID Task Name Start Finish Duration 18 1 Define 7/19/2004 7/19/2004 1d 2 Design 7/20/2004 7/26/2004 5d 3 Build 7/27/2004 7/27/2004 1d 4 Deploy 7/28/2004 7/28/2004 1d 5 Party 7/29/2004 7/29/2004 1d To Adaptation (Envision, Explore, Adapt) ??????????? 19 20 21 22 23 24 25 26 27 28 29 30 31 Microsoft Solutions Framework (v4) is… Guidance on how to organize people and projects to plan, build, and deploy technology solutions successfully and effectively An agile software development process A formal software development process Framework for customers and partners to implement custom software development process Out of the box MSF processes MSF Agile “Evolve and adapt” Ideal for Competitive Environments Rely on People Plan as you go MSF Formal “Plan and optimize” Ideal for Regulated Environments Rely on Process Plan in advance MSF Delivered Accessible/Embedded Centralized Delivered via Team Foundation Server Current Exposed within Help Updated from MSDN Customizable Extended by Customers and Partners Methodology Templates Default settings for a Portfolio Project Consumed during project creation Tailored to common SDLC practices MSF Formal, MSF Agile (out of the box) Extreme Programming, RUP Industry Specific (financial, health care, etc.) <Your customer’s organization here> Portfolio Project Creation Methodology Template Portfolio Project Project Creation Wizard User Input Anatomy of a Methodology Template Methodology Definition Methodology.xml Guidance Reporting Methodology.zip Work Items Bug.xml Task.xml CustomWIType.xml Methodology.xml <task id="Currituck" assembly="Microsoft.VisualStudio.ProjectCreation" class="Microsoft.VisualStudio. WorkItemCreator" completionDescription="Work items uploaded to the project site."> <dependencies> <dependency taskId="CSS" /> </dependencies> <taskXml> <task name="WorkItemType"> <workItemTypes> <workItemType fileName="Bug.xml" typeName="Bug" /> <workItemType fileName="Task.xml" typeName="Task" /> <workItemType fileName="CustomWIType.xml" typeName="Custom Work Item Type"> <workItems> <workItem id="1"> <field name="title" value="Identify and assign team resources" /> <field name="Priority" value="1" /> <field name="State" value="Active" /> <field name="Active Date" value="1/1/04" /> <field name="SubState" value="Blocked" /> <field name="Reason" value="New" /> </workItem> Process “Baked In” - Key Concepts Role performs permissions sequences Security Group Activity belongs to User Work Stream produces & consumes Work Product tracks owns Work Item schedules Iteration Query Key: Process Guidance Prescribes VSTS Enacts Report Demo: - Team Explorer - Process Methodology - Customization - Project Creation What about all the other lists I manage? Change Requests Customer Requests Requirements Bugs Issues List Demo: - Office Integration Resolve Conflicts Work Item Publishing Errors ? 16 of 20 work items have published successfully. Review and resolve the following issues to publish the remaining work items. ID Title Issue 357 Setup: Set Permissions Conflict Not published 407 InitializeDeBugger all times Validation error Not published 437 Resize doesn’t work Access denied Not published 507 User interface additions Server connection failed Not published Status Details Conflicting fields Local version Server version (10/04/2004 1:23 PM by monetaho) Assigned to jensj monetaho Priority 2 4 View Server Version Publish Cancel Visual Studio Team System Reporting Cross Lifecycle Customizable Extensible Team Project . Work Items (Requirements, Tasks, Bugs, Features) Source Code Project Reports Builds Tests Example of cross domain report Readily Available Reporting Warehouse Object Model Test/Build Adapter Build Database Work Item Adapter Work Item Tracking Source Code Adapter Source Code Control Excel Custom Reporting Add-on Adapter Partner Tool A Project Counsel Discussions Documents Policy Portal Search Home I need to... -- select from list -- Quick Launch Project Portal Home Create New Project Documents Status Reports Presentations Modify My Page Projects Overview Projects Status Project X Specs Requirements Reports Standard Reports Envisioning Create a new report Communications Status reports 2/2 1 /1 Due Date Signoff 6/5/03 Yes 2 of 2 4 of 12 8 of 8 21 of 55 3 of 3 12 of 15 8/1/03 No 3 of 4 5 of 7 9 of 10 6 of 7 9/1/03 No 8 of 9 17 of 20 8 of 10 10/1/03 No 0 of 0 0 of 0 0 of 0 11/1/03 No 1 of 9 6 of 7 3 of 3 7 of 8 7/15/03 No 3 of 3 1 of 10 7/25/03 No 2 of 4 9 of 9 Weekly Executive Summary Given our active bug count and incoming rates, it's become apparent that we are not ready to start our final test pass today (6/16). Therefore, our new M2 exit path is as follows: M2 Fork: TBD (see below) Final test pass start: 6/30 (see below) Sign off: 7/11 Recently updated Documents Name 90% 80% 70% 60% 50% 40% 30% 20% 10% 0% Project Management Console Defect Tracking Tool MSWord Requirements Template Humongous Project Guidelines Contacts Jacqueline Ackerman - Project Manager Endicott Smith - VP Sales, Project Sponsor Anna Jones - Business Analyst Bert Lewis - Development Manager Barbara Baker - Test Manager Add New Link Standard Forms Modified By Vision Document Vision Document Fiona Business Requirements Business Requirements Betty MyHIC Functional Requirements Paula Feature Specifications Customer Interviews Betty Status Reporting Add New Document Defects Open Test Cases Run Defects/TC in Log Add New Link Over the past few weeks, teams have done extraordinary work getting bugs resolved, triaging hard, and consistently getting closer and closer to meeting our milestone exit criteria. Ask mode has helped in keeping the builds working, and we're ready to start group checkins, after the mass integration last week (Lab21, Lab22 and Lab25 RI'ed in one day!). However, this is about a week and a half behind the original schedule. Type er e dler ASP ey Cor Han FX Tick nsfer FX Mon Tra Links FX Hander Transfer ASP Stabilizing Deploying Alias Members 4/4 Risks FX Ticker Developing Roles Manager Team Subscription 0 Issues Planning Public Reports Workflow Project Schedule Defects Defect Trends 450 400 350 300 250 200 150 100 50 0 Project Portal web site provides role-based views of the development project. In addition to providing useful information directly (such as the plan of record, defect trends, and other reports), it also serves as a launching point for various other tools. Functional Requirements Create a new Form Reporting Warehouse http://humongous/myprojectportal/default.aspx Home SQL Server Reporting Services MyHICPortal - Microsoft Internet Explorer Reporting Extensibility Architecture Demo: - Project Portal - Reporting 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? For More Information… Visual Studio Team System Site Project Management Blogs http://msdn.microsoft.com/teamsystem http://weblogs.asp.net/keithrowe/ http://lab.msdn.microsoft.com/teamsyst em/community/blogs/ MSF Agile Web Site http://lab.msdn.microsoft.com/teamsyst em/workshop/msfagile/