P
Project Slave
I have a project with 13 subprojects, all being tracked in a single plan.
Each of these 13 subprojects go thru a 5 stage software development life
cycle (requirements, design, development, testing and implementation).
Currently, the plan is ordered by the 5 development lifecycle stages and
within each stage, the 13 subprojects are scheduled. So, essentially, these
13 subprojects appear at 5 places in the plan, which is kind of cumbersome.
My question is, is it a best practice to do a plan like this (5 major
sections and 13 minor subsections) or flip the order (13 major sections, 5
subsections).
Each of these 13 subprojects go thru a 5 stage software development life
cycle (requirements, design, development, testing and implementation).
Currently, the plan is ordered by the 5 development lifecycle stages and
within each stage, the 13 subprojects are scheduled. So, essentially, these
13 subprojects appear at 5 places in the plan, which is kind of cumbersome.
My question is, is it a best practice to do a plan like this (5 major
sections and 13 minor subsections) or flip the order (13 major sections, 5
subsections).