November 5, 2020, 8:30 a.m. to 6 p.m. EDT | November 6, 2020 – February 7, 2021, On-Demand | Online Conference
Please login or join to subscribe to this thread
Just to put this in a context where you have the possibility to investigate more we implemented TBM in the company where I am working on. Perhaps is too much for your requirement but I am writing the reference trying to add more information. You can find information by searching "tbm council org"
I would be very happy if my procedure was helpful.
First of all, you should make a list of tasks that are performed iteratively daily, weekly or monthly.
This includes regular meetings, checking the progress of the work process, checking the status of the issue list, and more.
This can be created relatively easily by interviewing all members of your own organization.
Then measure the time required to complete each task.
Then, the total time is described in the monthly report as the time required for "fixed".
In addition, if there are other unexpected and unexpected tasks, name and manage them.
Each member manages the time required for the task individually.
I can't speak to the tools you're using, but it sounds like you are trying to blend a charging system configured for a functional based organization charging against individual projects, with projected work where people are assigned full time. Here is how I see it work in large matrix based organization structures:
The general support team charges to tickets. Charging against those tickets should be traceable back to the project that generated the work. The projectized work also rolls up to the project level budget, but it isn't broken down further or at least the same way.
An example is for project XYZ, every chargeline trees up to budget XYZ. The support team budget trees up to XYZ-a. The Implementation team trees up to XYZ-b. XYZ-a can be assigned to different tasks like XYZ-a1, XYZ-a2, XYZ-a3, etc. XYZb work is related to types of work at best, not to individual tasks. If you sit through a change board, you don't try to figure out how much time you spent for each change discussed. If you try, it's just expensive guesswork.
It can require a lot of work for accounting to break things into different buckets, so before we break things out into their own cost bucket, the question is whether it is worth the cost. Often the answer is NO unless we are considering large costs. Projectized people just charge to the project, not to individual tasks.
It's the cost of being projectized. You are dedicated to the project whether you are currently needed or not. The downside is occasional wasted time waiting for work. The upside is the reduction of waste waiting for a critical resource when you are needed.
Manual time reporting is a Theory X practice unless it is supporting billing to clients as in law firms. Assuming you are working on one or a few projects, you should be able to estimate your allocation to those and just flat-line report the time spent week-over-week. Anything more than that is not likely to add much value.
The focus should be on how much value is being realized by the delivery teams, not on how utilized they are.
Thanks for the tip, I am reading about it and seems very interesting. Looks like something that we could use in my company :)
What you said is likely what I have been doing, I am registering the time that I spend on each task and I provide a report at the end of the week.
All this process is manual, I was wondering if there would be some kind of tool - a desktop or web app - that can help to do it easier. Anyways, recording my time will be helpful when for myself in the future when I place my application to get the PMP certification.
At a previous employer, the developers used the Time Tracker feature in Jira and had the option to record time directly against their assigned tasks or on a timesheet. As a PM, I mainly used the timesheet as there typically weren't tasks assigned to me in Jira.
If implementing a new solution is not an option, does your ticketing system allow for a ticket to remain open for the duration of an implementation?
Please login or join to reply