Tammi - responses in blue, below:
1. How does your organization estimate a task or resource level in MSP
- Mostly still using long tasks (4-5 per project, each lasting 12-18 months), much like allocations - by head, by quarter. Doing this either via MSP, ITD Assignment Editor, though there is a CA PPM screen that allows this to, not just as well as ITD's solution.
- Personally, I'll do this by getting team in a room, confirm first the WBS, the dependencies, then the resources assigned to each task; given estimates from task members, will then put these into Remaining Work, plot network diagram on plotter (3' by whatever length needed), then bring team back to challenge - are dependencies really correct, and also chopping each tasks' hours by half (can't always get away with this, but its usually profitable, as people always pad every task. I then take the padding from all tasks, sum it, cut it in half, and use it as a project buffer between last task and customer due date (see Critical Chain by Goldratt). My customers have been so happy that they've said we need to do this on all projects....
2. Did you start using MSP immediately with CA PPM or did you use another scheduling tool such as OWB?
- Started with MSP and most are still using
- We do have a substantial group that has flipped to OWB - its free and the interface is much faster; so far, they are happy with it
3. Is there any functionality that’s lost due to the integration with CA PPM based on your configuration, meaning views or schedule?
- I don't think so. We have a team that has heavily customized the tool bars in MSP - these still work when exporting a project from CA PPM to MSP, though we had to make some changes - they utilized a number of text and number fields reserved for CA PPM/MSP interface - wish they had involved me from the start - could have gone easier.
4. What was the decision factor in using MSP
- MSP is widely used in automotive
- Resistance to change
- Belief that we need to use same tool that our customers and suppliers use (not true, as the apps all export/import to/from XML, today)
- Belief that once trained in MSP, one knows how to plan a project (not true - we're getting better, but still see a number of plans that can't be scheduled due to dependency and dependency type errors)
5. CA provided recommended settings in order to use MSP with CA PPM, did those setting work or did you have revise to optimize your use of MSP
- follow their recommendations, they work for us; if you have a problem, this will be first thing they ask you to correct
6. Task level details around what happens when a task is supposed to be complete by a certain date and that date passes, what occurs for ETC for resources?
- nothing happens, except variance metrics will start to show tasks are falling behind, except that if one updates schedule, using 'move incomplete work to current date,' the unused ETC will be pushed forward, basically rescheduling the task(s); I've seen discussions regarding how to automate the update of schedules, as project managers sometimes forget - there's an 'AutoSchedule Project' job, but we've not yet played with this. Going back through the history stored in my head (goes back quite a ways, now...), I recall that this job wasn't always available, people were asking for such a thing. I expect that it is running the algorithm for the Clarity Gantt Chart, so would want to be careful if/when rolling this out.
- do you want something to happen? may need to add a 'current date' attribute to task object and have it updated by a job, that would then kick off a process when task finish date variance exceeds a threshold.
- personally, I like the do nothing approach - a project has lots of tasks, some will get done early, some late - if monitoring for the early completions, can take advantage of them, making up any time lost on late tasks - better to monitor the project buffer - this way, every task doesn't turn into a firefight, which is counterproductive.
We are still on the legacy version of the CA PPM/MSP interface, as we are still on 14.2 - the XML version not working well, there, yet. Hoping XML version is faster on 15.x.
The MSP interface is still exceedingly slow when opening multi-level, hierarchical projects - which is a majority of our work. This is perhaps the primary reason for our one group's move to OWB.
Also, note that one cannot use another investment type between projects or between programs and projects. We'd like to run a program, say with a particular customer, contain a number of products we are launching for them, with each products' supporting projects underneath. If we try to open the program into MSP, the interface will stop at the program level, not working through the Product layer to the child projects underneath. I've not tried this with OWB but expect the same behavior - there are workarounds, but they don't reflect reality as well.
Hope this is helpful!
Dale