Executive Summary from Web Access

B

Bill

I'm getting re-introduced to Project Server after a couple years. I have
created a dummy project and have published it. I've created a couple
Enterprise Project Date custom fields. My goal is to provide my executives
with Web Access where they can see a summary of all projects. I envision
that they would have a "project" that would show approx 10-20 projects and
for each of these projects, there would be 5-10 dates that would be important
to show. Basically, it's a gantt chart of all active projects in one master
project.
What I'd like is for each project to provide the Enterprise Project Date
values and the master project get updated automatically.
Can someone point me in the right direction here?
 
J

John Sitka

I don't think you need a master project in this case.
key groupings and measures can break the projects down
into meaningful views
1) a set of outline codes which defines groups that represent different styles and/or status
of a project.
Is it R&D, is it production
Is it current or on hold/pending

2.) a key measure utilizing the deadline and planned finish(Finish) values
This can be calculated as a variance and displayed as a graphical indicator.
It is easy to use one of the Enterprise Project Date custom fields for this. That makes it nice
because when Exec's negotiate (sell premium time, expand scope, beg for extensions) they can
get their assistant to edit the date time without using the Project client.

So in one case there is a Project Center view that shows all ongoing production Projects
their remaining work, work, Start, Finish, deadline and finish/deadline variance are all displayed as columns.
The work values rollup to summarys so work = Enterprise Load accross those projects (past and future)
remaining work = Enterprise Load from today on (future only)
The variance between deadline (Enterprise Project Date) and Finish can by ordered (even if it is an indicator)
using the auto filter to focus in on which projects are tracking poorly. Invariably people want to dig down when
they see a problem. So each Project could be picked apart as an individual. That's is simply what most people demand.
Hopefully their examinination of a problem does not lead to tunnel vision, and the above described view should
be put into context with resource load capacity and performance over a cube analysis so these measures can be put into
a system context across the time dimension.

Make another view that considers projects on hold, or not yet won or combine any of the groupings in a way that are meaningful.
Even by year or by quarter. just another custom code or field to isolate or refine what focus is needed and the rollups are good
indicators

Example
3 value stream manager views
Bill remaining work across all his projects is 20000
Betty remaining work across all her projects is 40000
Brett remaining work across all his projects is 15000
Betty is our best person but the Bill and Brett need to step up
Pick candidate work to go to Bill and Brett (the easy stuff) Voila, Executive desicion made, where's my bonus!!!!

I can't see much value in this*, but for sure the view I describe above does show Start and Finish in a summary roll up;
as Minimum Start and Maximum Finish accross many projects.

* 11 projects total all starting around the same time
10 projects 1 month long each
1 project 3 months long for three months
Yes you have work until the Rolled up Finish but you need to
win some work after month one.
 
Top