TFS 2013 Initiatives und Features die ideale Ergänzung

TFS 2013 Initiatives und Features

Die Arbeit mit dem TFS 2012 macht, nicht erst seit dem letzten Update, definitiv Spass! Was allerdings noch immer fehlt ist eine Separierung zwischen Kundenanforderung und Backlog Item (PBI). Nicht jede Kundenanforderung lässt sich innerhalb von einem Sprint umsetzen und so war das Tracking der WorkItems immer relativ mühsam, wenn es um die Planung ging.

Diese Lücke sollte der TFS 2013 nun schliessen. Mit der Einführung von TFS 2013 Initiatives und Features, welche „oberhalb“ der PBI angesiedelt sind, wird eine Gesamtsicht über das Projekt ermöglicht.

Auszug aus dem MSDN Artikel:

In Team Foundation Server (TFS) 2012, you managed your team’s work in a backlog. In Team Foundation Server 2013 Preview, you can manage your work in a portfolio backlog that provides a management team insight into work across several agile teams. A management team defines the high-level goals and tracks work across multiple agile teams. Agile teams are the ones doing the work, breaking down items into tasks, fixing bugs, and contributing to the overall picture. All teams will have their own backlogs and boards, and will also have a roll-up view of the customer experiences supported by their work. When you’re done, you’ll be able to manage your portfolio of projects by grouping work according to backlog levels and see how it’s being accomplished across multiple teams.

Each team works on its own backlog, while the hierarchy of backlog work item types enables managers to view a roll-up of progress at a higher level. In this whitepaper, we’ll walk you through how to set up this kind of structure by following the hypothetical example of the Phone Saver management team and the agile teams working on specific areas of the overall project.

Each team has its own view of the work

Leave a Reply




Time limit is exhausted. Please reload CAPTCHA.