{"id":37822,"date":"2019-10-14T06:00:13","date_gmt":"2019-10-14T13:00:13","guid":{"rendered":"http:\/\/devblogs.microsoft.com\/premier-developer\/?p=37822"},"modified":"2019-11-25T06:46:49","modified_gmt":"2019-11-25T13:46:49","slug":"tracking-cross-team-projects-portfolio-with-azure-devops-boards","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/premier-developer\/tracking-cross-team-projects-portfolio-with-azure-devops-boards\/","title":{"rendered":"Tracking Cross-team Projects Portfolio with Azure DevOps Boards"},"content":{"rendered":"

In his previous post<\/a>, App Dev Manager Ricardo de Almeida<\/a> explained how to perform portfolio tracking in Azure DevOps\/TFS using Delivery Plans.<\/a> In this follow-up, he talks about the recently released Feature timeline and Epic Roadmap<\/a> extension.<\/p>\n

\n

A quick recap:<\/h3>\n

Last year I decided to share how I was using Azure DevOps and the Delivery Plans<\/a> extension to support one of my customers in their digital transformation starting by the mindset change from a prescriptive model to an agile approach and as I described in my previously post<\/a>:<\/p>\n

\u201cThe first step is by helping customer understand that agile project management is a paradigm breaker for those coming from traditional software project management methodologies and several mindset changes will be required, but besides the differences between both methods, business\u2019 needs must come first and if part of this transition requires that some aspects from the legacy process be kept, this is a great opportunity to show to this customer that, by using agile process and agile tools we can have an even better control about the value (no more only software) that the developers team are creating to the company, but now doing it in an incremental and interactive way.<\/em>\u201d<\/p>\n

Here I share some results of this first step:<\/p>\n