B
Bill Busby
We're still trying to crack the secret to a 'best practice' when it comes to
recording non-project time. We require 100% time reporting and on average
approx 70% of resource labor is for existing infrastructure support. The rest
is admin and projects. In the past we've created projects for this support
just so we can populate PWA lines. We want to move towards having projects be
pure projects and timesheets used to track the remaining effort. Some of our
challenges are...
1. Users would have to create the list of timesheet lines for each
timesheet period (not going to make this very popular..)
2. We need to be able to tie each timesheet line back to some purpose
(i.e., maintenance, billable support, enhancements, etc.). We thought about
using billing categories but the user has to choose the right one and the
choice can't be changed once made.
3. Most of our teams (couple of dozen teams of about 325 people) all do
very team-specific tasks so we'd like all DBA's to have a core set of
activities that differ from the core set for the network team.
Any insight on how we might approach this?
recording non-project time. We require 100% time reporting and on average
approx 70% of resource labor is for existing infrastructure support. The rest
is admin and projects. In the past we've created projects for this support
just so we can populate PWA lines. We want to move towards having projects be
pure projects and timesheets used to track the remaining effort. Some of our
challenges are...
1. Users would have to create the list of timesheet lines for each
timesheet period (not going to make this very popular..)
2. We need to be able to tie each timesheet line back to some purpose
(i.e., maintenance, billable support, enhancements, etc.). We thought about
using billing categories but the user has to choose the right one and the
choice can't be changed once made.
3. Most of our teams (couple of dozen teams of about 325 people) all do
very team-specific tasks so we'd like all DBA's to have a core set of
activities that differ from the core set for the network team.
Any insight on how we might approach this?