MSDN Magazine - December 2008 - (Page 48)

Active Fixed, As Designed, Deferred, Duplicate, Obsolete, Unable to Reproduce Regression, Reactivation Fixed, As Designed, Deferred, Duplicate, Obsolete, Unable to Reproduce Closed Resolution Denied, Wrong Fix, Test Failed Resolved Deferred, Obsolete, Unable to Reproduce, As Designed, Duplicate, Fixed Figure 3 MSF Agile Bug States and Transitions Proposed Approved, Investigate Active Fixed, As Designed Resolved Fixed Closed in Error, Regression Not Fixed Investigation Complete Deferred, Rejected, Duplicate er difference you’ll find between the two types of bugs is purpose. Microsoft made the MSF Agile bug a catch-all for all defects. If you examine a non-customized MSF Agile bug, you’ll see that it contains a Boolean field named Issue. For the CMMI process template, Microsoft created a separate Issue work item type. This is just one example of the differences. However, differences such as these will affect your team’s workflow when using a team project. Each of the MSF work item types has a section in the documentation labeled Process Guidance. The process guidance is broken down into two sections: work streams and activities. Work streams are a logical flow of activities typically related to a given role. An activity is a group of steps focused on a particular task. Each activity has both entry and exit criteria and is associated with one or more roles and a work stream. For example, if you look at the Reproduce the Bug activity in MSF Agile, you’ll see it’s a part of the Fix a Bug work stream and developer is the only participating role. Other activities such as Determine Iteration Length, which is also from the MSF Agile template’s Plan an Iteration work stream, have both a responsible role (the project manger) and participating roles (developers and database developers). Depending on how mature your team and process already is, you might adopt all, some, or none of the advice provided in the guidance. However, it’s important to realize that Microsoft has designed the work items, reports, and documents included with each template to work within the design of each template’s guidance. Thus, you should review the documentation and figure out what works and what doesn’t for your team. You can then decide if you want to live within the framework presented or adapt it for your team. Deferred, Duplicate, Not a Bug, Cannot Reproduce Process Template Customization Closed Figure 4 MSF CMMI Bug States and Transitions Figure 5 Importing the Lightweight Scrum Template 48 msdn magazine While it may be possible for your team to work with one of the Microsoft templates out of the box, more than likely you will want to change something. Number one on most teams’ lists is customization of work items. Beyond that there are check-in policies, the SharePoint portal site, and reports to create and customize. Since my very first MSDN Magazine column, I have extolled the benefits of Team System’s rich customization feature set, and process templates are no exception. Just about every single piece of a process template is changeable and customizable. In fact, a good way to find out just what’s possible is for you to take the time to explore two of the more popular third-party templates that extol the virtues of the Scrum development lifestyle. Conchango (scrumforteamsystem.com) published the first Scrum public template that I’m aware of, and there are template versions for TFS 2005 and TFS 2008. As we go to press, Conchango provides both templates free to the community but requires that you register to get the download link. Once you’ve downloaded the template, you extract the contents and run the setup package. Once configured, you’ll find the template as a choice in the New Team Project wizard. If you create a team project, you’ll note that Custom Process Templates http://www.scrumforteamsystem.com

Table of Contents Feed for the Digital Edition of MSDN Magazine - December 2008

MSDN Magazine - December 2008 Contents Toolbox CLR Inside Out Advanced Basics Cutting Edge Patterns In Practice Team System Real-World WF Visual Studio OBA Tools SOA Data Access Geneva Framework Test Run Foundations Windows With C++ Going Places End Bracket

MSDN Magazine - December 2008

For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.