When you create a team project in TFS, you have out-of-box been given the ability to choose between 3 relatively common software development processes used in our industry ( Scrum, MSF for Agile, and CMMI) for planning and tracking work within your team(s). For those reading this blog very familiar with the information and process differences the various process template choices give you when you create a team project, jump to the section below entitled “Agile tooling, your process template choice and customization.” For others new to TFS, here’s the condensed summary of what is affected by this choice which can be difficult to grasp, even though the MSDN help has made great strides at least in helping to explain this. Understanding the process template choice as a background to this feature:Īs a background to my review of this feature, it is important to understand the TFS notion of what it means to choose a process template when you create a team project.
There is now a more friction-free experience for testers who want to create task board level bugs as expounded on below. However, this team-level choice isn’t what makes this enhancement not a total yawner since teams can easily make the choice not to manage bugs at one level or another by just not doing it. Mostly yawn for on-premise TFS shops, because since the 2012 release they have always had this ability to add bugs to the backlog and task board through a well-documented customization path - though making this a choice at the team level is new. However, in practice it has some friction points for some process templates more than others, and does not go far enough to give teams the option of managing bugs at both the task and backlog level as expounded on below. I rank this option in my “OK” category because at least VSOnline teams can now configure this behavior regardless of the process template chosen at team project creation time. OK for TFS Cloud/ Visual Studio Online users. (See half-way down my last blog article for the ranking system I’m using.) My ranking and rationale for this feature: (This option is the out-of-box option for team project’s configured to use the MSF-Agile process template.) (This option is new.)ģ. Have bugs managed separately through work item queries rather than clutter their backlog or task board with that detail. (This option has been the out-of-box behavior for those team projects configured using the Scrum or CMMI process template.)Ģ.Have bugs appear on the task board alongside of the task-level work items which are tracked as a part of what needs to be done for a requirement to be called “Done.” These will also appear in the team’s backlog as child work items under the requirement to which they are attached. Have bugs appear on the team’s backlog and assigned to iterations along with their process template’s requirement-level work items.
One of the ballyhooed features of Team Foundation Server 2015 is that individual teams in a team project (regardless of the process template their team project was configured to use and without customizing the process template) can now configure for themselves how/where they want to manage bug work items in one of 3 ways:ġ.
( Note: This post makes heavy use of links to official documentation to allow users new to TFS to investigate the concept via official documentation and yet keep this article on-point of communicating information not readily apparent by reading that documentation).
0 kommentar(er)
