1

For people who work fulltime for a software company as a developer, how are your hours tracked? As in, are you assigned specific hours per task? Are you just given deadlines for a task to be done by? How small are tasks broken up into, etc?

Comments
  • 0
    I have to track how long I have worked on a story or task by myself. Based on an initial estimation after the specify phase, we will then evaluate the gap during, or at least after the implementation phase to have a good cost tracking.

    task or stories are ideally not bigger than two to three ideal working days.
  • 6
    - Hours aren't tracked, I can work 40 hours or 60 hours per week, it's all the same.

    - assigned tasks need to be completed in the 2 week sprint, however assignment is flexible and negotiated prior, in the sense you're not handed 20 tickets and told "do them" it's going through a back log and quantifying the amount of work needed for a task and either grabbing it now, or pushing it back for another sprint.

    - deadlines... see above (generally)

    - tasks aren't broken up much unless there's multiple changes to be made across systems, could be a bug fix, a new feature or a list of adjustment(s) for single feature.
  • 1
    Im working as consultan and to date everywhere its, make your 40 hours a week and it's fine. I can work one day 10 hours and the other 6. Or I can move an hour to Saturday (not preferred, since it's weekend and you shouldn't do work)
    Time tracking per task costs more than it can earn back unless your devs are a bunch of shitty people not willing to put in effort.
  • 0
    I have a fixed 40 hour week but report a rough estimate of time spent on top level epics, not per task or story.

    And its assumed some time every week get consumed by meanings, emails and similar so any left over is reported as other.
  • 1
    I am salary, so no tracked hours. I work roughly 40 hours a week (at least I am in the office that much) give or take depending on the project.

    I have deadlines but normally finish in plenty of time.

    I break things up and plan out my tasks on my own for the project and knock them out to meet requirements. I pretty much manage myself in this respect. As long as I make my deadlines it's pretty cushy but I have to deal with a lot of corporate BS and have little to no say on user needs.
  • 1
    We just ask our 1099's for a general number of hours for that week. As for our salaried employees, I really don't give a shit. Just give me your 40 hours week on average. For both, I don't care what times you want to work or where you want to work. We don't want pew warmers, that's a waste for everyone. All I really care about is getting the work done, and done properly. Companies that want you to track your time in fucking 15 minute increments are goddamn batshit crazy. Now I'm just rambling.
  • 1
    Thanks for the responses. Trying to get an idea if I should get used to it or if my company is not the norm. plasticnova hit it on the nail with my company, every task, small or big, has hours associated with it down to 15 minute intervals and all 40 of my weekly hours need to be assigned to a task (im a salary employee). No time is given for emails or items not given a task (like QAs asking for records to be inserted into a table for testing purposes, seeing why a UI is behaving like it is, etc) .
    And these tasks have a projected estimated hours associated with them , usually given by a PM. It's really killed my joy of programming
  • 1
    @shoogknight they sound like they think they can run development like they would an IT helpdesk.
    no bueno
  • 2
    @shoogknight the only time in my career I've had an employer track my every working hour, is the only business I've worked for that is no longer in existence.

    I'm not saying these are connected, but 🙃
  • 1
    They ask for how much time I need, negotiate a deadline from it.
    Once it's accepted by the team, we do whatever the fuck we want. We just need to deliver what we promised.

    I will refuse any offer that doesn't let me free schedule. (Only exception being a client meeting)
  • 0
    In Jira tickets
  • 2
    @Plasticnova I actually applied to a job and at the end of the first interview they told that detailed time registration every 15 minutes was mandatory.

    I politely declined when they were about to do me an offer later on.
  • 1
    @linuxxx I would have done the same
  • 0
    OH, and screw places that think documentation means explaining each line of code... I'm not here to educate you on how to build the program Dave, just how to use it
Add Comment