bigprojectpm
IS-IT--Management
I am managing a very big project (multi-year, dozens of people) using an iterative development approach based on the Unified Process. I have multiple people who manage portions of the project (subprojects in essence). For example, UI design is a separate vendor - yet integrated in our work, QA is separate, and another PM I have managing work of the internal tech team. I am struggling to find a best practice - or least painful anyway, approach to structuring my MS Project files. I started with the UP phases, Inception, Elaboration, etc, and put the iterations within those. For each iteration, though, each of the above subprojects has tasks. I prefer (and in the case of UI it is necessary) to have the individual PMs manage tasks in their own project file(s). On the other hand, I need to look at completeness and dependencies within each phase and iteration at the master level.
I have thought of three options with one chosen so far for now anyway, but am curious for other ideas.
Option 1) Use a separate subproject file for each iteration for the subprojects. This is my current approach at least for the dev stuff. However, because of project overall size, we have multiple higher-level cycles (BIG subprojects) that are full UP cycles (Inception, Elaboration, etc) and those BIG subprojects overlap, so there are times when there may be an elaboration iteration for cycle n going on at the same time as a construction iteration for the prior cycle, etc.), in somewhat of a factory model for resource usage. That means the other PMs managing the separate subproject files could have several at once to manage.
Option 2) Use one subproject file for each discipline (UI vendor, QA, Dev) and create dependency tasks only in the master project that tie back to the subprojects, so I can see the key dates in the master in the UP outline order. This is my approach for the UI vendor tasks.
Option 3) Abandon the UP outline order in the master project altogether - but then it's harder to manage and assess UP iterations as a whole.
I also thought about whether I could use option 2 but add a field somehow to the tasks such that I could re-sort in the master project to see all the tasks in the UP order, but it seemed like that might be pretty hard, fragile, and I wasn't sure it would be workable, so I haven't seriously pursued trying the idea out.
Any suggestions?
Many thanks.
I have thought of three options with one chosen so far for now anyway, but am curious for other ideas.
Option 1) Use a separate subproject file for each iteration for the subprojects. This is my current approach at least for the dev stuff. However, because of project overall size, we have multiple higher-level cycles (BIG subprojects) that are full UP cycles (Inception, Elaboration, etc) and those BIG subprojects overlap, so there are times when there may be an elaboration iteration for cycle n going on at the same time as a construction iteration for the prior cycle, etc.), in somewhat of a factory model for resource usage. That means the other PMs managing the separate subproject files could have several at once to manage.
Option 2) Use one subproject file for each discipline (UI vendor, QA, Dev) and create dependency tasks only in the master project that tie back to the subprojects, so I can see the key dates in the master in the UP outline order. This is my approach for the UI vendor tasks.
Option 3) Abandon the UP outline order in the master project altogether - but then it's harder to manage and assess UP iterations as a whole.
I also thought about whether I could use option 2 but add a field somehow to the tasks such that I could re-sort in the master project to see all the tasks in the UP order, but it seemed like that might be pretty hard, fragile, and I wasn't sure it would be workable, so I haven't seriously pursued trying the idea out.
Any suggestions?
Many thanks.