Multiple Project vs Overhead Task Suggestion?

[Ted Musa]

We have a new VB6 to .NET project in which we will
allocate all of our resources to for four days a week and
the fifth day we will allocate all resources to handling
legacy code issues that arise in our Client Problem
Tracking System (PTS). What would be the best way to
handle these two issues? Should we have one project with
the PTS issues (variable) handled as an Overhead task?

 

[Gary L. Chefetz [MVP]]

Ted:

It depends on what you want out of system. Do you want a legacy system-level
cost analysis of the work then you'll treat it more formally than an
overhead task. If you don't give a hoot much where this effort is going
overhead it. Pick a priority and act accordingly.

In my experience, most IT organizations that want to move to activity based
management don't dismiss a stream of work that consumes 20% of the staff's
productive work time.