I'd be really interested to know ( I was going to do a Ask HN ) on who has to track their time at work, how big the company is you work for, what detail do you

I'd be really interested to know ( I was going to do a Ask HN ) on who has to track their time at work, how big the company is you work for, what detail do you track to and whether you think it's useful and if so, how is it useful?. I personally work in a semi small product based company and we don't track time, but we have a few "point in time goals" where we need to get a solution sorted by a specific date. I started with extreme programming in 2000 and used to use the planning ideas and velocity indicators, which is okish, but kind of a blunt tool. However the real mechanism to deal with problems is scope management. So now I just work on the idea of continuous focusing on goals and scope management of those goals. This works pretty well in a small team and time frames that are not too long (2 - 3 months). However a lot of our development is purely feature based, which is often not time critical, but are scope managed to what I'd call "worthwhile" increments So instead of worrying about time, my emphasis is goals/focus, feedback on progress and scope management. This tends to lead to good time outcomes.