In this series of blog posts regarding Power BI and Azure DevOps, we have discussed how to connect Power BI to data held in Azure DevOps projects using Analytics View, using Power BI visualisations to display and compare work item statistics, and how project team members can contribute to ensure the data held in Azure DevOps are up to date to ensure accurate reporting. In this final post, we focus on display detailed data of parent and children work items in a Power BI report page.
If your project team uses Azure DevOps to manage your project delivery, one thing that the built in dashboard widgets do not do well is the visualisation of historical statistics from the project. In this post we discuss how this can be achieved by using Analytics View and Power BI visualisation.
What are some of the questions that project team use reporting to help them understand? At the end of a sprint the team might wish to take a look at how work items were closed. In this blog post we take a look at work item closure trends and how Power BI reporting of data from Azure DevOps based on Analytics Views can be used to help with these investigations.
In previous post we explored how data from Azure DevOps projects can be exposed and made available for reporting in Power BI using Analytics View. In this post we look at the data model from Analytics View and some of the basic Power BI design concepts.
If you use Azure DevOps to manage your project and you need to do complex visualisation of project delivery statistics, you can now use Power BI for Azure DevOps using the Analytics Service.
If you use Azure DevOps (formerly Visual Studio Team Services) you would already be familiar with their Dashboards and widgets you can add to the Dashboards (e.g. see the example dashboard in the 1st post). So when would you need to consider using Power BI for reporting?
Recently I wrapped up a project where I spent a lot of time doing delivery reporting out of the old Team Foundation Service 2015 (TFS 2015). I became interested in how the reporting might have improved in the latest online version of Azure DevOps (formerly Visual Studio Team Services – VSTS). In this series of blog posts I shall dive into the reporting capabilities of Azure DevOps for project management and later the currently beta release of a Power BI connector to Azure DevOps.
Ever got stuck with round after round of requirements gathering and yet you feel no closer to getting stakeholder consensus? How about months of development close to go live, only to find your hard work wasted as the business has changed direction or process, rendering your deliverable obsolete? How can we avoid these pitfalls and deliver CRM projects with business impact?
Why should people working in CRM deliveries take a look at the CRM Manifesto? Why should consultants sign on as a signatory to support its goals?
Ever wish for a way to embed tailored help content specific to your organisation directly into Dynamics 365? Now you can! It’s called Learning Path….