Project Management Central

Please login or join to subscribe to this thread

MS Project Embedded Plans
Last time we did a large project with multiple, semi-independent teams, we used a Master project plan and embedded the sub-plans into the Master (e.g. the environment plan was "separate" from the testing plan). As I recall, everything worked great until there were dependencies across plans. Then, some funky things started happening (dates, resource loading, etc.) when the sub-plans were updated. Time heals all wounds, and it's been about a year since I tried this. Any comments or suggestions to disuade me from trusting MS Project? Note: As an alternative, we're planning to use the tried-and-true Milestone tracking, wherein we only track the major milestones/dependencies in the Master and leave the detail plans separate.

Please login or join to reply

Content ID:

"We should be careful to get out of an experience only the wisdom that is in it - and stop there; lest we be like the cat that sits down on a hot stove-lid. She will never sit down on a hot stove-lid again, and that is well; but also she will never sit down on a cold one anymore."

- Mark Twain