Continuing with the linkfest from my previous two posts as the wrap up from the Project Conference this week in Phoenix.
In this post, I’ll include links to the instructions for demos for PerformancePoint, PowerPivot and VBA Trend Analysis. Note that some of these links may not yet be active – but will be in the next several weeks.
PerformancePoint is another one of those underutilized tools in the Project Server reporting tool set. In our presentation, we showed how to create a PerformancePoint report, how to decompose it, and how to incorporate it into a filtered PerformancePoint dashboard.
For a technical overview as well as a link the official white papers on the topic, please check out this site.
See below for additional information on the specific functionality demonstrated at the conference.
2. Creating Personalized, Filtered Dashboards in PerformancePoint with Project Server data. Ever wonder how you can create dashboards and have them automatically filter based on the current user? Check out these posts (Part 1, Part 2 & Part 3).
Trend Analysis with VBA
One of the often heard requests around Microsoft Project and reporting is the ability to perform trend analysis over time. OLAP cubes will generally meet your needs for cost or effort based reporting, but trend reporting of items such as EVM or milestone variance has traditionally been a challenge.
Solutions typically include a custom SQL routine that takes snapshots of project fields or a third party tool such as UMT’s Project Essentials suite that lets users configure the fields using a simple UI.
For our demo the other day, I figured I’d demonstrate another technique. In that demo, we used VBA to record data in a spare Baseline10Cost field, then Excel Services to generate a report. Effectively, we’re creating custom timescaled data fields.
1. Enterprise BCWP Reporting (Part 1, Part 2, Part 3, Part 4) – although I should point out to those folks who attended my EVM presentation on Thursday that technically speaking, keeping historical BCWP in Project as an editable field isn’t really compliant with formal EVM reporting requirements. For something like that, a locked down SQL or third party solution is probably more appropriate.
2. Milestone Variance Analysis – here’s a solution to take a snapshot of milestone variance and store it in a spare Baseline Cost field – then extract into a useful report.
1. Reporting on Risks with External Lists (Part 1 & Part 2). This walks you through how to use Project Server Risk data to generate a dynamically updated, conditionally formatted SharePoint list. Here’s a walk through using the same approach to generate a list of projects.
1. Reporting with PowerPivot and Project Server 2010 – in this demo, Mike showed how to pull Project Server data into Excel – then combined the data with offline resource rate calculations. Finally, he showed how to use PowerPivot to aggregate Risk and Issues data across project workspaces. Watch the Project Team Blog over the next couple of weeks for that post. (I’ll probably come back and update this post when that gets published.)
…and that’s it for the links. Bring on the content!