none
Project/Work Package plans - Best Practice? RRS feed

  • Question

  • What are people's views on best practice for creating separate "work package" plans and tracking thereof?

    Is the default best approach just to create Master and Sub project plans or just to make everything a project plan and track using custom fields and codes to group workpackages into projects?  Pros and Cons either way??

    thanks

    Saturday, April 20, 2013 1:45 PM

Answers

  • Stev Scott42 --
     
    If different PMs need to manage the different work packages, I recommend that each work package be a separate project, and all of these work packages should roll up into a master project.  If one PM will manage all of the work packages, theoretically you could place all of the work packages in a single project, so long as the project is not so large that the PM could not manage it well.  Hope this helps.
     

    Dale A. Howard [MVP]

    • Marked as answer by Stev Scott42 Sunday, April 21, 2013 10:35 AM
    Sunday, April 21, 2013 1:10 AM
    Moderator

All replies

  • Stev Scott42 --
     
    If different PMs need to manage the different work packages, I recommend that each work package be a separate project, and all of these work packages should roll up into a master project.  If one PM will manage all of the work packages, theoretically you could place all of the work packages in a single project, so long as the project is not so large that the PM could not manage it well.  Hope this helps.
     

    Dale A. Howard [MVP]

    • Marked as answer by Stev Scott42 Sunday, April 21, 2013 10:35 AM
    Sunday, April 21, 2013 1:10 AM
    Moderator
  • thanks Dale
    Sunday, April 21, 2013 10:35 AM