Looking for recommendations/advisement from other groups...

We are planning to revise the structure of our time tracking data. All IT employees are asked to track all actual hours worked for a given week. We propose 3 main categories: Projects, Services, Applications. Services and Applications will have a standard list of tasks that help tie to a key subset of ITRT's / Technical Services.

Tasks for Applications include: App Design/Development, App Support/Maintenance, App Testing, App Integration, App Training

Tasks for Services include: Demand Mgmt, Service Mgmt, IT Strategy & Planning, BRM, Data Analytics, Risk Mgmt

 

• Service will be fed from our Service Library,  Apps from our APM inventory, and projects from MS Project
• All Apps and Services will be RtB
• Projects will be labeled RtB or CtB
• Time spent on incidents will automatically move over to populate the app/service worked on

Thoughts on this approach?

You may want to add non productive tasks (Training, PTO, meetings, etc)

Have a clear definition of projects. Is it based on funding source, or other criteria? There could be project like activities you may or may not want to track as projects.

Missing a task for Service support/maintenance

Assuming you have a defined workflow for timecard submission and approval. How is this process connected to the HR timecard processes?

Thank you for the feedback Juan.

Right now the timecard is not directly connected to our HR/payroll process. We do use the data, but our timekeepers manually pull reports and verify as they adjust the payroll timecard in the HR system.