Headers shows up as task

[JM]

I just finished sequencing (assigning precessor relationships) a series of
distinct project tasks. The project tasks are grouped by distinct themes. The
themes are listed as headers for each set of projects. Since they are themes
and not project tasks, they should not have predecessor or any other such
relationships. In fact, I don't want them showing up at all in the gannt
chart since they don't have anything to do with the timeline (only with
organizing the information in the WBS sheet).

Does anyone know how I can still keep those 'headers' in the WBS without
their showing in the gannt screen? Thanks.

 

[Rob Schneider]

By "headers" do you mean what Project calls "summary" tasks?

You can use a Filter to filter out Summary tasks, or even use the
Outline Level field to filter out whatever level you want.

--rms

www.rmschneider.com

 

[JulieS]

Another option is to turn off the display of summary tasks through
Tools > Options, View tab.

Julie
Project MVP

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

 

[Steve House]

In addition to Rob's answer, if your "headers" are Project's summary tasks,
you can go to the Tools/Options menu, select the View tab, and clear the
checkbox labeled "Show summary tasks."

Not sure what you mean by "themes" but be advised that in a properly built
WBS the summary tasks should be rollups for the activiites that lead to the
production of a specific project deliverable. If we were building a shed,
for example, some summary tasks might be "Clear Site" "Lay Foundation"
"Erect Walls" "Install Roof" ... etc and indented within each would be the
all the various activities that need to be scheduled and coordinated in
order to create a clear site, the foundation, the walls, the roof and so
forth. What I call "administrative" breakdowns by department, or team or
budget category or task type or skill required seem to inevitably lead to a
confused and unusable schedule and I'm concernced that what you're calling
"grouping by distinct themes" is something like that, grouping them based on
some common characteristic of the task rather than a proper deliverables
oriented breakdown and grouping. Just something to consider before you get
too deep....

 

[Jim Aksel]

Please accept my appology if this post appears to elementary or
condenscending (it is certainly not intended that way).

For "Themes" if you are refering to "Summary Tasks" as all have pointed out,
I think we all made the assumption you had that layout.

Just in case, tasks can be indented below one another to create summaries:
"Clear Land" may have subtasks of "Rent Weed Wacker", "Purchase Shovels",
"Hire Workers", etc. These subtasks can be indented underneath "Clear Land"
by using the green arrow buttons on the Formatting toolbar.

So highlighting all the subtasks and then selecting indent (right green
arrow), you will create a summary task for "Clear Land"

As Steve pointed out, it is usually very important these summary tasks are
for some type of deliverable. Some go so far as to say that every task in
the schedule should start with an Action Verb like I did (Rent, Purchase,
Hire).
--
If this post was helpful, please consider rating it.

Jim Aksel, MVP

Check out my blog for more information:
http://www.msprojectblog.com