R
Rob Schneider
Folks,
Our large IT organization, for which my role is a customer, is
consolidating many separate and diverse MIS applications and process
into the product called PlanView www.planview.com, which is marketed for
"comprehensive IT portfolio management".
One of the advertised "benefits" is reduction in license fees for the
thousands of copies of Microsoft Project. Accordingly, the expectation
is that use of Microsoft Project will cease. Use of Project has always
been problematic in this organizatoin as the vast majority of people
with a license didn't use it, and those who did use it tended to use it
prescriptively as a Gant Chart maker for use in PowerPoint. Already I'm
detecting people looking at me funny when I propose using Project to
help develop a project plan. They feel already under pressure to use the
"strategic" product PlanView which despite being months away from
release is already "politically correct".
My opinion, based on prior experimental use of PlanView is that it is
unrealistic to expect Project can be eliminated (assuming it's used
properly in the first place). I'm wondering therefore if there are any
people in this forum who have familiarity with both products and can
provide me guidance about-
: the role of Project in a PlanView shop
: capability of Project vs. Planview for scheduling (critical path,
earned value, resource leveling, schedule duration computation, etc.)
Our large IT organization, for which my role is a customer, is
consolidating many separate and diverse MIS applications and process
into the product called PlanView www.planview.com, which is marketed for
"comprehensive IT portfolio management".
One of the advertised "benefits" is reduction in license fees for the
thousands of copies of Microsoft Project. Accordingly, the expectation
is that use of Microsoft Project will cease. Use of Project has always
been problematic in this organizatoin as the vast majority of people
with a license didn't use it, and those who did use it tended to use it
prescriptively as a Gant Chart maker for use in PowerPoint. Already I'm
detecting people looking at me funny when I propose using Project to
help develop a project plan. They feel already under pressure to use the
"strategic" product PlanView which despite being months away from
release is already "politically correct".
My opinion, based on prior experimental use of PlanView is that it is
unrealistic to expect Project can be eliminated (assuming it's used
properly in the first place). I'm wondering therefore if there are any
people in this forum who have familiarity with both products and can
provide me guidance about-
: the role of Project in a PlanView shop
: capability of Project vs. Planview for scheduling (critical path,
earned value, resource leveling, schedule duration computation, etc.)