Mulitiple projects

[tshad]

I am new to MS Project and want to start formalizing my project control.

I have various projects I work on. Design and build multiple web sites, in
house software, networking etc.

I am trying to figure out the best way to use Project to handle this.

Would I create a Project (in MS Project) for each of my projects? One for
each of my Web sites. One for each of my In-house projects. One for
network support and purchasing etc.

I know you can use Multiple Projects in one by creating many projects and
then creating a Master project and including them in that project. But I
don't know if that is the best way to do that. Most of the books on MS
Project just show you how to create a project and then all the options you
can do with it. But not really much on how to handle multiple projects.
Some of which are on going. Such as a web site that you are constantly
updating.

Is there a good place to find this?

Thanks,

Tom

 

[Mike Glen]

Hi Tom,

Welcome to this Microsoft Project newsgroup

My personal view is to keep things simple and create one project file for
each of your projects and then consolitate them into a master as you
suggested. My reasoning is that when projects are completed they can easily
be archived, whereas putting them all into one file makes this complicated
in the long run.

FAQs, companion products and other useful Project information can be seen at
this web address: http://project.mvps.org/faqs.htm

Hope this helps - please let us know how you get on

Mike Glen
MS Project MVP
See http://tinyurl.com/2xbhc for Project Tutorials

 

[tshad]

Sounds good.

But how would you handle a Project that is pretty much a continuous project.

Say you have a Web Project that you design, build and deliver. You then
have new features that you add continuously. Would you just keep adding
tasks to the Project or would you keep starting new Projects. When you
first start the Project you would typically have design time, development
time, Beta Testing and Bring Live. This would obviously have an end point.
But as you go you add features that users ask for or new features you had
planned on but wanted to get the project out the door so you plan on adding
new features later from a feature list.

Would you set a new Project for everything after bringing live?

Thanks,

Tom

 

[Mike Glen]

Basically, Yes. A project could be defined as a unique undertaking that has
a clearly defined Start and FINISH, requiring the management of men,
materiel and money. Thus, when the website site is finished, so it the
project. If it subsequently requires a new feature, then this is a new
project in its own right. I don't know if others have different views?

Mike Glen
Project MVP

 

[tshad]

Hi Tom,

Welcome to this Microsoft Project newsgroup

My personal view is to keep things simple and create one project file for
each of your projects and then consolitate them into a master as you
suggested. My reasoning is that when projects are completed they can
easily be archived, whereas putting them all into one file makes this
complicated in the long run.

How do you make a master?

If I have 3 projects, can I have a master project look at each project and
display the projects in relation to each other?

Thanks,

Tom

 

[tshad]

Found a pretty good article on this at:

http://pubs.logicalexpressions.com/Pub0009/LPMArticle.asp?ID=443

Tom

 

[Mike Glen]

Hi Tom,

You found a good one there Good luck

Mike Glen
Project MVP

 

[JulieS]

Hmmmm. That article would be written, of course, by none other than the
illustrious Mike Glen, Project MVP and one of the top "answer gurus"
from this self-same news group?

Julie

 

[tshad]

Hmmmm. That article would be written, of course, by none other than the
illustrious Mike Glen, Project MVP and one of the top "answer gurus" from
this self-same news group?

I noticed that.

I also saw his other articles as well and plan to get to them in good order.
Just need the time

Tom

 

[JulieS]

I noticed that.

I also saw his other articles as well and plan to get to them in good
order. Just need the time

Tom

Hi Tom,

I know what you mean. If Project could only halt time from progressing
so we could all catch up......

Julie
<snip>

 

[tshad]

Hi Tom,

I know what you mean. If Project could only halt time from progressing so
we could all catch up......

I think that about lots of things I would like to pursue

Tom

 

[ProjPro Cyrus]

I have setup a Master Project with two subprojects. When I group by
enterprise outline codes the tasks are "meshed" together, without regard to
which project they come from. For example, might have a task from the 1st
proj, then a task from the 2nd proj, then a task from the 2st proj, etc. If I
want to group by subproject, I just add Project to my Grouping.

However, when I view the Master Project in PWA 2007, the system always
groups on Project (after whatever grouping I apply). I don't always want this
view. I sometimes want to see the tasks "meshed" without regard to which
project they came from. This is simple in ProjPro2007, in fact, its the
default.

Can anyone suggest how I can get rid of the Project Grouping in PWA 2007 for
a Master Project?

Thanks so much for your help,

Cyrus

 

[Mike Glen]

Hi Cyrus,

Try posting on the server newsgroup. Please see FAQ Item: 24. Project
Newsgroups. FAQs, companion products and other useful Project information
can be seen at this web address: http://project.mvps.org/faqs.htm

Mike Glen
Project MVP