What is the best practise for this?

[Alexander Barvinsky]

Greetings,
Case: one client with multiple activities which we want to track
(e.g. small projects, bugs fixing, operations tasks ).
We have installed MSPS 2007.
Question is what is the best practices for this situation in
organization of project framework? I need a single place to store
whole project documentation, tasks, etc. How to combine project plans
into one (and do we need to do this at all)? Do we need to use Master
project Plan with inserted into it sub-projects?
Thanks.
Best regards,
Alexander Barvinsky
http://pm4pm.org

 

[Jim Aksel]

The best practice for combining multiple projects is to use a Master File
with subprojects. However, use some common sense -- if the projects are 10
tasks and have a duration of one month I would suggest they are activities
and not a project by themself.

Generally, "Bug Fixes" is considered a Level of Effort task as part of a
larger project. The exception to that would be a separately funded project to
correct a specified number of well documented problems that would take
several months and result in something like a software patch, service pack,
or similar.


--
If this post was helpful, please consider rating it.

Jim

Visit http://project.mvps.org/ for FAQs and more information
about Microsoft Project