Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. Time logging... why?

Time logging... why?

Scheduled Pinned Locked Moved The Lounge
collaborationhelpphpdesignbusiness
31 Posts 28 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • L Lost User

    I'm a programmer working in a small 7-man team of developers for a web design studio. We work in PHP/Symfony2 (rant for another day) and use Atlassian's JIRA ticket system for tracking issues. We also use it for logging time. :( This being the first job I've had in which time logging has been mandatory (log all work, log 7.5 hours per day) I'm finding it to be a huge obstacle to my productivity. A train of thought is a fragile thing, and stopping after every little thing (sending an e-mail, making a Git commit) to log the time I've spent on it and what I did is proving to be very effective at derailing it. Couple this with the pressure to get 7.5 hours logged on something or other every single day and I'm actually starting to dread coming to work in the morning. Not only this, we now have a completely redundant physical whiteboard full of sticky-notes representing JIRA tickets/issues that must be kept in-sync with the digital system. By hand. We're such a small team, we're all in the same room. But every time we want to fix an issue we need to:

    1. Go to JIRA, mark the issue as 'In Progress'.
    2. Stand up, walk over the the whiteboard and move the sticky-note to the 'In Progress' column.
    3. Sit back down, fix the issue.
    4. Go to JIRA, log the time spent on the issue and write a short description of what has been changed.
    5. Mark the issue as 'Ready for Review'.
    6. Stand up again, :| walk over to the whiteboard and move the sticky-note to the 'Ready for Review' column.
    7. Go back to JIRA again and message the QA guys that there's a new sticky note in the 'Ready for Review' column.

    I stress again, we're a 7-man web development team trying to be time-efficient, fast and agile. Everyone's practically going crazy about how everything takes too long. Part of it's to do with the bulky toolset we're using, but it baffles me that we can't slim down the ridiculous admin and let the developers do what they do best without having to watch the clock all the time. So what's the verdict? Am I a crybaby or is this genuinely as silly as it all seems? :(

    P Offline
    P Offline
    Pete OHanlon
    wrote on last edited by
    #3

    That is all fouled up. Seriously? The board o doom is not meant to be such a chore. Ditching the manual board will be a great start.

    1 Reply Last reply
    0
    • L Lost User

      I'm a programmer working in a small 7-man team of developers for a web design studio. We work in PHP/Symfony2 (rant for another day) and use Atlassian's JIRA ticket system for tracking issues. We also use it for logging time. :( This being the first job I've had in which time logging has been mandatory (log all work, log 7.5 hours per day) I'm finding it to be a huge obstacle to my productivity. A train of thought is a fragile thing, and stopping after every little thing (sending an e-mail, making a Git commit) to log the time I've spent on it and what I did is proving to be very effective at derailing it. Couple this with the pressure to get 7.5 hours logged on something or other every single day and I'm actually starting to dread coming to work in the morning. Not only this, we now have a completely redundant physical whiteboard full of sticky-notes representing JIRA tickets/issues that must be kept in-sync with the digital system. By hand. We're such a small team, we're all in the same room. But every time we want to fix an issue we need to:

      1. Go to JIRA, mark the issue as 'In Progress'.
      2. Stand up, walk over the the whiteboard and move the sticky-note to the 'In Progress' column.
      3. Sit back down, fix the issue.
      4. Go to JIRA, log the time spent on the issue and write a short description of what has been changed.
      5. Mark the issue as 'Ready for Review'.
      6. Stand up again, :| walk over to the whiteboard and move the sticky-note to the 'Ready for Review' column.
      7. Go back to JIRA again and message the QA guys that there's a new sticky note in the 'Ready for Review' column.

      I stress again, we're a 7-man web development team trying to be time-efficient, fast and agile. Everyone's practically going crazy about how everything takes too long. Part of it's to do with the bulky toolset we're using, but it baffles me that we can't slim down the ridiculous admin and let the developers do what they do best without having to watch the clock all the time. So what's the verdict? Am I a crybaby or is this genuinely as silly as it all seems? :(

      M Offline
      M Offline
      Mike Hankey
      wrote on last edited by
      #4

      Sounds like a real PITA. What you might do is estimate the time spent doing the BS as opposed to actual work and submit it to the bosses. I would imagine if the time spent on BS is large enough they will find a way to slim it down?

      Have you ever just looked at someone and knew the wheel was turning but the hamster was dead? Trying to understand the behavior of some people is like trying to smell the color 9.

      L 1 Reply Last reply
      0
      • L Lost User

        I'm a programmer working in a small 7-man team of developers for a web design studio. We work in PHP/Symfony2 (rant for another day) and use Atlassian's JIRA ticket system for tracking issues. We also use it for logging time. :( This being the first job I've had in which time logging has been mandatory (log all work, log 7.5 hours per day) I'm finding it to be a huge obstacle to my productivity. A train of thought is a fragile thing, and stopping after every little thing (sending an e-mail, making a Git commit) to log the time I've spent on it and what I did is proving to be very effective at derailing it. Couple this with the pressure to get 7.5 hours logged on something or other every single day and I'm actually starting to dread coming to work in the morning. Not only this, we now have a completely redundant physical whiteboard full of sticky-notes representing JIRA tickets/issues that must be kept in-sync with the digital system. By hand. We're such a small team, we're all in the same room. But every time we want to fix an issue we need to:

        1. Go to JIRA, mark the issue as 'In Progress'.
        2. Stand up, walk over the the whiteboard and move the sticky-note to the 'In Progress' column.
        3. Sit back down, fix the issue.
        4. Go to JIRA, log the time spent on the issue and write a short description of what has been changed.
        5. Mark the issue as 'Ready for Review'.
        6. Stand up again, :| walk over to the whiteboard and move the sticky-note to the 'Ready for Review' column.
        7. Go back to JIRA again and message the QA guys that there's a new sticky note in the 'Ready for Review' column.

        I stress again, we're a 7-man web development team trying to be time-efficient, fast and agile. Everyone's practically going crazy about how everything takes too long. Part of it's to do with the bulky toolset we're using, but it baffles me that we can't slim down the ridiculous admin and let the developers do what they do best without having to watch the clock all the time. So what's the verdict? Am I a crybaby or is this genuinely as silly as it all seems? :(

        D Offline
        D Offline
        Deflinek
        wrote on last edited by
        #5

        The board is just plain stupid. If someone (manager?) wants to see what everyone is working on when he enters the room he can but large TV and hook it up with agile JIRA dashboard - should be cheaper in a month or two considering all your trips to the board. As for the JIRA itself.. well.. there have to be some kind of tracking where the money goes. The problem may start if client can see it as it may be sometimes hard to explain why what they see (!) as simple change took 3 days.

        -- "My software never has bugs. It just develops random features."

        H 1 Reply Last reply
        0
        • L Lost User

          I'm a programmer working in a small 7-man team of developers for a web design studio. We work in PHP/Symfony2 (rant for another day) and use Atlassian's JIRA ticket system for tracking issues. We also use it for logging time. :( This being the first job I've had in which time logging has been mandatory (log all work, log 7.5 hours per day) I'm finding it to be a huge obstacle to my productivity. A train of thought is a fragile thing, and stopping after every little thing (sending an e-mail, making a Git commit) to log the time I've spent on it and what I did is proving to be very effective at derailing it. Couple this with the pressure to get 7.5 hours logged on something or other every single day and I'm actually starting to dread coming to work in the morning. Not only this, we now have a completely redundant physical whiteboard full of sticky-notes representing JIRA tickets/issues that must be kept in-sync with the digital system. By hand. We're such a small team, we're all in the same room. But every time we want to fix an issue we need to:

          1. Go to JIRA, mark the issue as 'In Progress'.
          2. Stand up, walk over the the whiteboard and move the sticky-note to the 'In Progress' column.
          3. Sit back down, fix the issue.
          4. Go to JIRA, log the time spent on the issue and write a short description of what has been changed.
          5. Mark the issue as 'Ready for Review'.
          6. Stand up again, :| walk over to the whiteboard and move the sticky-note to the 'Ready for Review' column.
          7. Go back to JIRA again and message the QA guys that there's a new sticky note in the 'Ready for Review' column.

          I stress again, we're a 7-man web development team trying to be time-efficient, fast and agile. Everyone's practically going crazy about how everything takes too long. Part of it's to do with the bulky toolset we're using, but it baffles me that we can't slim down the ridiculous admin and let the developers do what they do best without having to watch the clock all the time. So what's the verdict? Am I a crybaby or is this genuinely as silly as it all seems? :(

          D Offline
          D Offline
          Dr Walt Fair PE
          wrote on last edited by
          #6

          I once worked for a company that briefly wanted me to log everything in 15 minute increments and submit the log weekly. After the first week I turned my log in and my boss appeared in my office shortly thereafter. Seems he wanted to know why I had 4 hours logged as "logging time" for the week. I asked if he actually knew how long it took to check your watch every few minutes to see if 15 minutes had gone by, then write down what you did for that 15 minutes, then transcribe and summarize it at the end of a week. They trashed the time logging after I explained the process to a few coworkers.

          CQ de W5ALT

          Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software

          C 1 Reply Last reply
          0
          • L Lost User

            I'm a programmer working in a small 7-man team of developers for a web design studio. We work in PHP/Symfony2 (rant for another day) and use Atlassian's JIRA ticket system for tracking issues. We also use it for logging time. :( This being the first job I've had in which time logging has been mandatory (log all work, log 7.5 hours per day) I'm finding it to be a huge obstacle to my productivity. A train of thought is a fragile thing, and stopping after every little thing (sending an e-mail, making a Git commit) to log the time I've spent on it and what I did is proving to be very effective at derailing it. Couple this with the pressure to get 7.5 hours logged on something or other every single day and I'm actually starting to dread coming to work in the morning. Not only this, we now have a completely redundant physical whiteboard full of sticky-notes representing JIRA tickets/issues that must be kept in-sync with the digital system. By hand. We're such a small team, we're all in the same room. But every time we want to fix an issue we need to:

            1. Go to JIRA, mark the issue as 'In Progress'.
            2. Stand up, walk over the the whiteboard and move the sticky-note to the 'In Progress' column.
            3. Sit back down, fix the issue.
            4. Go to JIRA, log the time spent on the issue and write a short description of what has been changed.
            5. Mark the issue as 'Ready for Review'.
            6. Stand up again, :| walk over to the whiteboard and move the sticky-note to the 'Ready for Review' column.
            7. Go back to JIRA again and message the QA guys that there's a new sticky note in the 'Ready for Review' column.

            I stress again, we're a 7-man web development team trying to be time-efficient, fast and agile. Everyone's practically going crazy about how everything takes too long. Part of it's to do with the bulky toolset we're using, but it baffles me that we can't slim down the ridiculous admin and let the developers do what they do best without having to watch the clock all the time. So what's the verdict? Am I a crybaby or is this genuinely as silly as it all seems? :(

            T Offline
            T Offline
            Tim Carmichael
            wrote on last edited by
            #7

            Songshu Xinxu wrote:

            I stress again, we're a 7-man web development team

            And therein lies the problem; men do not multi-task well.. you need a woman on the team to truly get multitasking done...

            Sander RosselS 1 Reply Last reply
            0
            • T Tim Carmichael

              Songshu Xinxu wrote:

              I stress again, we're a 7-man web development team

              And therein lies the problem; men do not multi-task well.. you need a woman on the team to truly get multitasking done...

              Sander RosselS Offline
              Sander RosselS Offline
              Sander Rossel
              wrote on last edited by
              #8

              But with women on the team the men won't do any (productive) work at all anymore :)

              It's an OO world.

              public class SanderRossel : Lazy<Person>
              {
              public void DoWork()
              {
              throw new NotSupportedException();
              }
              }

              R 1 Reply Last reply
              0
              • L Lost User

                I'm a programmer working in a small 7-man team of developers for a web design studio. We work in PHP/Symfony2 (rant for another day) and use Atlassian's JIRA ticket system for tracking issues. We also use it for logging time. :( This being the first job I've had in which time logging has been mandatory (log all work, log 7.5 hours per day) I'm finding it to be a huge obstacle to my productivity. A train of thought is a fragile thing, and stopping after every little thing (sending an e-mail, making a Git commit) to log the time I've spent on it and what I did is proving to be very effective at derailing it. Couple this with the pressure to get 7.5 hours logged on something or other every single day and I'm actually starting to dread coming to work in the morning. Not only this, we now have a completely redundant physical whiteboard full of sticky-notes representing JIRA tickets/issues that must be kept in-sync with the digital system. By hand. We're such a small team, we're all in the same room. But every time we want to fix an issue we need to:

                1. Go to JIRA, mark the issue as 'In Progress'.
                2. Stand up, walk over the the whiteboard and move the sticky-note to the 'In Progress' column.
                3. Sit back down, fix the issue.
                4. Go to JIRA, log the time spent on the issue and write a short description of what has been changed.
                5. Mark the issue as 'Ready for Review'.
                6. Stand up again, :| walk over to the whiteboard and move the sticky-note to the 'Ready for Review' column.
                7. Go back to JIRA again and message the QA guys that there's a new sticky note in the 'Ready for Review' column.

                I stress again, we're a 7-man web development team trying to be time-efficient, fast and agile. Everyone's practically going crazy about how everything takes too long. Part of it's to do with the bulky toolset we're using, but it baffles me that we can't slim down the ridiculous admin and let the developers do what they do best without having to watch the clock all the time. So what's the verdict? Am I a crybaby or is this genuinely as silly as it all seems? :(

                P Offline
                P Offline
                Paul M Watt
                wrote on last edited by
                #9

                The manual board is seriously stupid if there is a digital system. However, I work for a defense contractor and we must log our work to 6 minute increments. This must be logged daily for accounting and auditing purposes. We are billing the government after all. I just keep notes when I change a task, mark the time, and continue working. At the end of the day I fill out the reporting, which takes about 5 minutes, and I'm done. It didn't take long to get the hang of it and now it's not all that disruptive. I'm sure there is a way to streamline your process so it seems less disruptive. As others have said, whoever is funding the effort probably would like to see how the money is spent. I wouldn't get too caught up in the process, and just make sure you do solid work.

                1 Reply Last reply
                0
                • L Lost User

                  I'm a programmer working in a small 7-man team of developers for a web design studio. We work in PHP/Symfony2 (rant for another day) and use Atlassian's JIRA ticket system for tracking issues. We also use it for logging time. :( This being the first job I've had in which time logging has been mandatory (log all work, log 7.5 hours per day) I'm finding it to be a huge obstacle to my productivity. A train of thought is a fragile thing, and stopping after every little thing (sending an e-mail, making a Git commit) to log the time I've spent on it and what I did is proving to be very effective at derailing it. Couple this with the pressure to get 7.5 hours logged on something or other every single day and I'm actually starting to dread coming to work in the morning. Not only this, we now have a completely redundant physical whiteboard full of sticky-notes representing JIRA tickets/issues that must be kept in-sync with the digital system. By hand. We're such a small team, we're all in the same room. But every time we want to fix an issue we need to:

                  1. Go to JIRA, mark the issue as 'In Progress'.
                  2. Stand up, walk over the the whiteboard and move the sticky-note to the 'In Progress' column.
                  3. Sit back down, fix the issue.
                  4. Go to JIRA, log the time spent on the issue and write a short description of what has been changed.
                  5. Mark the issue as 'Ready for Review'.
                  6. Stand up again, :| walk over to the whiteboard and move the sticky-note to the 'Ready for Review' column.
                  7. Go back to JIRA again and message the QA guys that there's a new sticky note in the 'Ready for Review' column.

                  I stress again, we're a 7-man web development team trying to be time-efficient, fast and agile. Everyone's practically going crazy about how everything takes too long. Part of it's to do with the bulky toolset we're using, but it baffles me that we can't slim down the ridiculous admin and let the developers do what they do best without having to watch the clock all the time. So what's the verdict? Am I a crybaby or is this genuinely as silly as it all seems? :(

                  J Offline
                  J Offline
                  Jeremy Falcon
                  wrote on last edited by
                  #10

                  Welcome to corporate life. They just want to see where the money is being spent. It's not too bad if they don't get really anal about it, but then again most bean counters do. That being said, I still don't like doing it. It's retarded, but I understand why it's done.

                  Jeremy Falcon

                  1 Reply Last reply
                  0
                  • L Lost User

                    I'm a programmer working in a small 7-man team of developers for a web design studio. We work in PHP/Symfony2 (rant for another day) and use Atlassian's JIRA ticket system for tracking issues. We also use it for logging time. :( This being the first job I've had in which time logging has been mandatory (log all work, log 7.5 hours per day) I'm finding it to be a huge obstacle to my productivity. A train of thought is a fragile thing, and stopping after every little thing (sending an e-mail, making a Git commit) to log the time I've spent on it and what I did is proving to be very effective at derailing it. Couple this with the pressure to get 7.5 hours logged on something or other every single day and I'm actually starting to dread coming to work in the morning. Not only this, we now have a completely redundant physical whiteboard full of sticky-notes representing JIRA tickets/issues that must be kept in-sync with the digital system. By hand. We're such a small team, we're all in the same room. But every time we want to fix an issue we need to:

                    1. Go to JIRA, mark the issue as 'In Progress'.
                    2. Stand up, walk over the the whiteboard and move the sticky-note to the 'In Progress' column.
                    3. Sit back down, fix the issue.
                    4. Go to JIRA, log the time spent on the issue and write a short description of what has been changed.
                    5. Mark the issue as 'Ready for Review'.
                    6. Stand up again, :| walk over to the whiteboard and move the sticky-note to the 'Ready for Review' column.
                    7. Go back to JIRA again and message the QA guys that there's a new sticky note in the 'Ready for Review' column.

                    I stress again, we're a 7-man web development team trying to be time-efficient, fast and agile. Everyone's practically going crazy about how everything takes too long. Part of it's to do with the bulky toolset we're using, but it baffles me that we can't slim down the ridiculous admin and let the developers do what they do best without having to watch the clock all the time. So what's the verdict? Am I a crybaby or is this genuinely as silly as it all seems? :(

                    R Offline
                    R Offline
                    Ron Nicholson
                    wrote on last edited by
                    #11

                    I used Tiddlywiki, slightly modified, with the TaskTimer plugin. Bascially I click the button type a sentence then go on. Worked pretty well but I wasn't trying to track for billing purposes.

                    Jack of all trades, master of none, though often times better than master of one.

                    1 Reply Last reply
                    0
                    • L Lost User

                      I'm a programmer working in a small 7-man team of developers for a web design studio. We work in PHP/Symfony2 (rant for another day) and use Atlassian's JIRA ticket system for tracking issues. We also use it for logging time. :( This being the first job I've had in which time logging has been mandatory (log all work, log 7.5 hours per day) I'm finding it to be a huge obstacle to my productivity. A train of thought is a fragile thing, and stopping after every little thing (sending an e-mail, making a Git commit) to log the time I've spent on it and what I did is proving to be very effective at derailing it. Couple this with the pressure to get 7.5 hours logged on something or other every single day and I'm actually starting to dread coming to work in the morning. Not only this, we now have a completely redundant physical whiteboard full of sticky-notes representing JIRA tickets/issues that must be kept in-sync with the digital system. By hand. We're such a small team, we're all in the same room. But every time we want to fix an issue we need to:

                      1. Go to JIRA, mark the issue as 'In Progress'.
                      2. Stand up, walk over the the whiteboard and move the sticky-note to the 'In Progress' column.
                      3. Sit back down, fix the issue.
                      4. Go to JIRA, log the time spent on the issue and write a short description of what has been changed.
                      5. Mark the issue as 'Ready for Review'.
                      6. Stand up again, :| walk over to the whiteboard and move the sticky-note to the 'Ready for Review' column.
                      7. Go back to JIRA again and message the QA guys that there's a new sticky note in the 'Ready for Review' column.

                      I stress again, we're a 7-man web development team trying to be time-efficient, fast and agile. Everyone's practically going crazy about how everything takes too long. Part of it's to do with the bulky toolset we're using, but it baffles me that we can't slim down the ridiculous admin and let the developers do what they do best without having to watch the clock all the time. So what's the verdict? Am I a crybaby or is this genuinely as silly as it all seems? :(

                      L Offline
                      L Offline
                      Lost User
                      wrote on last edited by
                      #12

                      Songshu Xinxu wrote:

                      By hand.

                      :laugh:

                      Songshu Xinxu wrote:

                      Am I a crybaby or is this genuinely as silly as it all seems?

                      Silly would be a nice understatement.

                      Songshu Xinxu wrote:

                      let the developers do what they do best without having to watch the clock all the time.

                      Ehr.. when done right, planning time is something that is beneficial. Using it against your developers means you're not making friends.

                      Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]

                      1 Reply Last reply
                      0
                      • L Lost User

                        I'm a programmer working in a small 7-man team of developers for a web design studio. We work in PHP/Symfony2 (rant for another day) and use Atlassian's JIRA ticket system for tracking issues. We also use it for logging time. :( This being the first job I've had in which time logging has been mandatory (log all work, log 7.5 hours per day) I'm finding it to be a huge obstacle to my productivity. A train of thought is a fragile thing, and stopping after every little thing (sending an e-mail, making a Git commit) to log the time I've spent on it and what I did is proving to be very effective at derailing it. Couple this with the pressure to get 7.5 hours logged on something or other every single day and I'm actually starting to dread coming to work in the morning. Not only this, we now have a completely redundant physical whiteboard full of sticky-notes representing JIRA tickets/issues that must be kept in-sync with the digital system. By hand. We're such a small team, we're all in the same room. But every time we want to fix an issue we need to:

                        1. Go to JIRA, mark the issue as 'In Progress'.
                        2. Stand up, walk over the the whiteboard and move the sticky-note to the 'In Progress' column.
                        3. Sit back down, fix the issue.
                        4. Go to JIRA, log the time spent on the issue and write a short description of what has been changed.
                        5. Mark the issue as 'Ready for Review'.
                        6. Stand up again, :| walk over to the whiteboard and move the sticky-note to the 'Ready for Review' column.
                        7. Go back to JIRA again and message the QA guys that there's a new sticky note in the 'Ready for Review' column.

                        I stress again, we're a 7-man web development team trying to be time-efficient, fast and agile. Everyone's practically going crazy about how everything takes too long. Part of it's to do with the bulky toolset we're using, but it baffles me that we can't slim down the ridiculous admin and let the developers do what they do best without having to watch the clock all the time. So what's the verdict? Am I a crybaby or is this genuinely as silly as it all seems? :(

                        L Offline
                        L Offline
                        Lost User
                        wrote on last edited by
                        #13

                        I've worked in a number of places that try to do time logging - and usually have fought against it for its entire lack of usefulness. First thing I did was write a small proggy (what we used to call Apps back in the day!) to log my time so I could click a button every time I did anything, type in some text, and then display it at the end of the day/week. When I went to log my time, I had millionis of entries - 2 minutes going to the loo, time spent getting coffee or tea, talking to someone, having a meeting, responding to an email from the boss asking if I had updated my times etc. etc. They soon had so much data it was entirely unmanageable. There is, though, a very good reason for logging the approximate time spend on tasks - and that is to improve processes and estimation. If a task was estimated as 1/2 day and actually takes significantly longer, it's useful to know why to prevent under-estimation in future.

                        PooperPig - Coming Soon

                        1 Reply Last reply
                        0
                        • L Lost User

                          I'm a programmer working in a small 7-man team of developers for a web design studio. We work in PHP/Symfony2 (rant for another day) and use Atlassian's JIRA ticket system for tracking issues. We also use it for logging time. :( This being the first job I've had in which time logging has been mandatory (log all work, log 7.5 hours per day) I'm finding it to be a huge obstacle to my productivity. A train of thought is a fragile thing, and stopping after every little thing (sending an e-mail, making a Git commit) to log the time I've spent on it and what I did is proving to be very effective at derailing it. Couple this with the pressure to get 7.5 hours logged on something or other every single day and I'm actually starting to dread coming to work in the morning. Not only this, we now have a completely redundant physical whiteboard full of sticky-notes representing JIRA tickets/issues that must be kept in-sync with the digital system. By hand. We're such a small team, we're all in the same room. But every time we want to fix an issue we need to:

                          1. Go to JIRA, mark the issue as 'In Progress'.
                          2. Stand up, walk over the the whiteboard and move the sticky-note to the 'In Progress' column.
                          3. Sit back down, fix the issue.
                          4. Go to JIRA, log the time spent on the issue and write a short description of what has been changed.
                          5. Mark the issue as 'Ready for Review'.
                          6. Stand up again, :| walk over to the whiteboard and move the sticky-note to the 'Ready for Review' column.
                          7. Go back to JIRA again and message the QA guys that there's a new sticky note in the 'Ready for Review' column.

                          I stress again, we're a 7-man web development team trying to be time-efficient, fast and agile. Everyone's practically going crazy about how everything takes too long. Part of it's to do with the bulky toolset we're using, but it baffles me that we can't slim down the ridiculous admin and let the developers do what they do best without having to watch the clock all the time. So what's the verdict? Am I a crybaby or is this genuinely as silly as it all seems? :(

                          M Offline
                          M Offline
                          Mark_Wallace
                          wrote on last edited by
                          #14

                          Jira is about time management and project costs. The sticky notes are about communicating with other people. Hmm. I think I might see why developers think both are a waste of time.

                          I wanna be a eunuchs developer! Pass me a bread knife!

                          1 Reply Last reply
                          0
                          • D Deflinek

                            The board is just plain stupid. If someone (manager?) wants to see what everyone is working on when he enters the room he can but large TV and hook it up with agile JIRA dashboard - should be cheaper in a month or two considering all your trips to the board. As for the JIRA itself.. well.. there have to be some kind of tracking where the money goes. The problem may start if client can see it as it may be sometimes hard to explain why what they see (!) as simple change took 3 days.

                            -- "My software never has bugs. It just develops random features."

                            H Offline
                            H Offline
                            Herbie Mountjoy
                            wrote on last edited by
                            #15

                            Seems like a terrible waste of time and effort. Have you considered logging the time spent on logging? That may result in a one way trip to the ext door or it may communicate that this is an inefficient process.

                            I may not last forever but the mess I leave behind certainly will.

                            1 Reply Last reply
                            0
                            • L Lost User

                              I'm a programmer working in a small 7-man team of developers for a web design studio. We work in PHP/Symfony2 (rant for another day) and use Atlassian's JIRA ticket system for tracking issues. We also use it for logging time. :( This being the first job I've had in which time logging has been mandatory (log all work, log 7.5 hours per day) I'm finding it to be a huge obstacle to my productivity. A train of thought is a fragile thing, and stopping after every little thing (sending an e-mail, making a Git commit) to log the time I've spent on it and what I did is proving to be very effective at derailing it. Couple this with the pressure to get 7.5 hours logged on something or other every single day and I'm actually starting to dread coming to work in the morning. Not only this, we now have a completely redundant physical whiteboard full of sticky-notes representing JIRA tickets/issues that must be kept in-sync with the digital system. By hand. We're such a small team, we're all in the same room. But every time we want to fix an issue we need to:

                              1. Go to JIRA, mark the issue as 'In Progress'.
                              2. Stand up, walk over the the whiteboard and move the sticky-note to the 'In Progress' column.
                              3. Sit back down, fix the issue.
                              4. Go to JIRA, log the time spent on the issue and write a short description of what has been changed.
                              5. Mark the issue as 'Ready for Review'.
                              6. Stand up again, :| walk over to the whiteboard and move the sticky-note to the 'Ready for Review' column.
                              7. Go back to JIRA again and message the QA guys that there's a new sticky note in the 'Ready for Review' column.

                              I stress again, we're a 7-man web development team trying to be time-efficient, fast and agile. Everyone's practically going crazy about how everything takes too long. Part of it's to do with the bulky toolset we're using, but it baffles me that we can't slim down the ridiculous admin and let the developers do what they do best without having to watch the clock all the time. So what's the verdict? Am I a crybaby or is this genuinely as silly as it all seems? :(

                              S Offline
                              S Offline
                              Stefan_Lang
                              wrote on last edited by
                              #16

                              The process is sound, but you shouldn't be doing it by hand! There are plenty of programs that would do a much better job of keeping track of bug fixes and similar. We use the Mantis bugtracker software. We haven't installed it ourselves, so I can't provide a link, but I'm sure it's not hard to look up. It does require some effort (and a server) to install, but it's much less painfull to use, works remotely without additional effort, and even lets you view the entire history of a given issue, in case it keeps popping up. There are other systems that may be commercial, may focus on other capabilities, and may be easier or harder to use or install. You just need to find the one that does the best job for you.

                              GOTOs are a bit like wire coat hangers: they tend to breed in the darkness, such that where there once were few, eventually there are many, and the program's architecture collapses beneath them. (Fran Poretto)

                              1 Reply Last reply
                              0
                              • L Lost User

                                I'm a programmer working in a small 7-man team of developers for a web design studio. We work in PHP/Symfony2 (rant for another day) and use Atlassian's JIRA ticket system for tracking issues. We also use it for logging time. :( This being the first job I've had in which time logging has been mandatory (log all work, log 7.5 hours per day) I'm finding it to be a huge obstacle to my productivity. A train of thought is a fragile thing, and stopping after every little thing (sending an e-mail, making a Git commit) to log the time I've spent on it and what I did is proving to be very effective at derailing it. Couple this with the pressure to get 7.5 hours logged on something or other every single day and I'm actually starting to dread coming to work in the morning. Not only this, we now have a completely redundant physical whiteboard full of sticky-notes representing JIRA tickets/issues that must be kept in-sync with the digital system. By hand. We're such a small team, we're all in the same room. But every time we want to fix an issue we need to:

                                1. Go to JIRA, mark the issue as 'In Progress'.
                                2. Stand up, walk over the the whiteboard and move the sticky-note to the 'In Progress' column.
                                3. Sit back down, fix the issue.
                                4. Go to JIRA, log the time spent on the issue and write a short description of what has been changed.
                                5. Mark the issue as 'Ready for Review'.
                                6. Stand up again, :| walk over to the whiteboard and move the sticky-note to the 'Ready for Review' column.
                                7. Go back to JIRA again and message the QA guys that there's a new sticky note in the 'Ready for Review' column.

                                I stress again, we're a 7-man web development team trying to be time-efficient, fast and agile. Everyone's practically going crazy about how everything takes too long. Part of it's to do with the bulky toolset we're using, but it baffles me that we can't slim down the ridiculous admin and let the developers do what they do best without having to watch the clock all the time. So what's the verdict? Am I a crybaby or is this genuinely as silly as it all seems? :(

                                S Offline
                                S Offline
                                Simon Lee Shugar
                                wrote on last edited by
                                #17

                                I think they're asking you to waste your time. I can see the advantages of measuring the metrics however they must realise that pointless admin takes time. I do record what I work on in a spreadsheet, however I do not include hours spent on a task. I record the tasks I work on for my own benefit as I am constantly switching and need to keep track of what types of work I do overall.

                                Simon Lee Shugar (Software Developer) www.simonshugar.co.uk "If something goes by a false name, would it mean that thing is fake? False by nature?" By Gilbert Durandil

                                1 Reply Last reply
                                0
                                • L Lost User

                                  I'm a programmer working in a small 7-man team of developers for a web design studio. We work in PHP/Symfony2 (rant for another day) and use Atlassian's JIRA ticket system for tracking issues. We also use it for logging time. :( This being the first job I've had in which time logging has been mandatory (log all work, log 7.5 hours per day) I'm finding it to be a huge obstacle to my productivity. A train of thought is a fragile thing, and stopping after every little thing (sending an e-mail, making a Git commit) to log the time I've spent on it and what I did is proving to be very effective at derailing it. Couple this with the pressure to get 7.5 hours logged on something or other every single day and I'm actually starting to dread coming to work in the morning. Not only this, we now have a completely redundant physical whiteboard full of sticky-notes representing JIRA tickets/issues that must be kept in-sync with the digital system. By hand. We're such a small team, we're all in the same room. But every time we want to fix an issue we need to:

                                  1. Go to JIRA, mark the issue as 'In Progress'.
                                  2. Stand up, walk over the the whiteboard and move the sticky-note to the 'In Progress' column.
                                  3. Sit back down, fix the issue.
                                  4. Go to JIRA, log the time spent on the issue and write a short description of what has been changed.
                                  5. Mark the issue as 'Ready for Review'.
                                  6. Stand up again, :| walk over to the whiteboard and move the sticky-note to the 'Ready for Review' column.
                                  7. Go back to JIRA again and message the QA guys that there's a new sticky note in the 'Ready for Review' column.

                                  I stress again, we're a 7-man web development team trying to be time-efficient, fast and agile. Everyone's practically going crazy about how everything takes too long. Part of it's to do with the bulky toolset we're using, but it baffles me that we can't slim down the ridiculous admin and let the developers do what they do best without having to watch the clock all the time. So what's the verdict? Am I a crybaby or is this genuinely as silly as it all seems? :(

                                  M Offline
                                  M Offline
                                  Merlin87
                                  wrote on last edited by
                                  #18

                                  Pardon my comment, i am retired now... But I would never give a work to do to an enterprise wasting so much time doing things by HAND! Are U an IT firm?

                                  1 Reply Last reply
                                  0
                                  • L Lost User

                                    I'm a programmer working in a small 7-man team of developers for a web design studio. We work in PHP/Symfony2 (rant for another day) and use Atlassian's JIRA ticket system for tracking issues. We also use it for logging time. :( This being the first job I've had in which time logging has been mandatory (log all work, log 7.5 hours per day) I'm finding it to be a huge obstacle to my productivity. A train of thought is a fragile thing, and stopping after every little thing (sending an e-mail, making a Git commit) to log the time I've spent on it and what I did is proving to be very effective at derailing it. Couple this with the pressure to get 7.5 hours logged on something or other every single day and I'm actually starting to dread coming to work in the morning. Not only this, we now have a completely redundant physical whiteboard full of sticky-notes representing JIRA tickets/issues that must be kept in-sync with the digital system. By hand. We're such a small team, we're all in the same room. But every time we want to fix an issue we need to:

                                    1. Go to JIRA, mark the issue as 'In Progress'.
                                    2. Stand up, walk over the the whiteboard and move the sticky-note to the 'In Progress' column.
                                    3. Sit back down, fix the issue.
                                    4. Go to JIRA, log the time spent on the issue and write a short description of what has been changed.
                                    5. Mark the issue as 'Ready for Review'.
                                    6. Stand up again, :| walk over to the whiteboard and move the sticky-note to the 'Ready for Review' column.
                                    7. Go back to JIRA again and message the QA guys that there's a new sticky note in the 'Ready for Review' column.

                                    I stress again, we're a 7-man web development team trying to be time-efficient, fast and agile. Everyone's practically going crazy about how everything takes too long. Part of it's to do with the bulky toolset we're using, but it baffles me that we can't slim down the ridiculous admin and let the developers do what they do best without having to watch the clock all the time. So what's the verdict? Am I a crybaby or is this genuinely as silly as it all seems? :(

                                    A Offline
                                    A Offline
                                    aayawa
                                    wrote on last edited by
                                    #19

                                    We did some time logging on one sprint but developers estimated how much time was spent on tasks like email, meetings, support, etc. We found that development took up about 35% of the week. Since then the number of meetings has shrunk dramatically and everyone manages email better. I estimate that some 70% of the time is now spent in development and the team ( about the same size as yours) have become far more productive. I try to note at the end of the day what I have done, since it will be needed for my performance review, but I try to ensure it takes no more than a minute or two. And then summarise ( again in 5 minutes) at the end of the month.

                                    1 Reply Last reply
                                    0
                                    • L Lost User

                                      I'm a programmer working in a small 7-man team of developers for a web design studio. We work in PHP/Symfony2 (rant for another day) and use Atlassian's JIRA ticket system for tracking issues. We also use it for logging time. :( This being the first job I've had in which time logging has been mandatory (log all work, log 7.5 hours per day) I'm finding it to be a huge obstacle to my productivity. A train of thought is a fragile thing, and stopping after every little thing (sending an e-mail, making a Git commit) to log the time I've spent on it and what I did is proving to be very effective at derailing it. Couple this with the pressure to get 7.5 hours logged on something or other every single day and I'm actually starting to dread coming to work in the morning. Not only this, we now have a completely redundant physical whiteboard full of sticky-notes representing JIRA tickets/issues that must be kept in-sync with the digital system. By hand. We're such a small team, we're all in the same room. But every time we want to fix an issue we need to:

                                      1. Go to JIRA, mark the issue as 'In Progress'.
                                      2. Stand up, walk over the the whiteboard and move the sticky-note to the 'In Progress' column.
                                      3. Sit back down, fix the issue.
                                      4. Go to JIRA, log the time spent on the issue and write a short description of what has been changed.
                                      5. Mark the issue as 'Ready for Review'.
                                      6. Stand up again, :| walk over to the whiteboard and move the sticky-note to the 'Ready for Review' column.
                                      7. Go back to JIRA again and message the QA guys that there's a new sticky note in the 'Ready for Review' column.

                                      I stress again, we're a 7-man web development team trying to be time-efficient, fast and agile. Everyone's practically going crazy about how everything takes too long. Part of it's to do with the bulky toolset we're using, but it baffles me that we can't slim down the ridiculous admin and let the developers do what they do best without having to watch the clock all the time. So what's the verdict? Am I a crybaby or is this genuinely as silly as it all seems? :(

                                      G Offline
                                      G Offline
                                      Gary Wheeler
                                      wrote on last edited by
                                      #20

                                      That's asinine. Chuck the whiteboard.

                                      Software Zen: delete this;

                                      1 Reply Last reply
                                      0
                                      • L Lost User

                                        I'm a programmer working in a small 7-man team of developers for a web design studio. We work in PHP/Symfony2 (rant for another day) and use Atlassian's JIRA ticket system for tracking issues. We also use it for logging time. :( This being the first job I've had in which time logging has been mandatory (log all work, log 7.5 hours per day) I'm finding it to be a huge obstacle to my productivity. A train of thought is a fragile thing, and stopping after every little thing (sending an e-mail, making a Git commit) to log the time I've spent on it and what I did is proving to be very effective at derailing it. Couple this with the pressure to get 7.5 hours logged on something or other every single day and I'm actually starting to dread coming to work in the morning. Not only this, we now have a completely redundant physical whiteboard full of sticky-notes representing JIRA tickets/issues that must be kept in-sync with the digital system. By hand. We're such a small team, we're all in the same room. But every time we want to fix an issue we need to:

                                        1. Go to JIRA, mark the issue as 'In Progress'.
                                        2. Stand up, walk over the the whiteboard and move the sticky-note to the 'In Progress' column.
                                        3. Sit back down, fix the issue.
                                        4. Go to JIRA, log the time spent on the issue and write a short description of what has been changed.
                                        5. Mark the issue as 'Ready for Review'.
                                        6. Stand up again, :| walk over to the whiteboard and move the sticky-note to the 'Ready for Review' column.
                                        7. Go back to JIRA again and message the QA guys that there's a new sticky note in the 'Ready for Review' column.

                                        I stress again, we're a 7-man web development team trying to be time-efficient, fast and agile. Everyone's practically going crazy about how everything takes too long. Part of it's to do with the bulky toolset we're using, but it baffles me that we can't slim down the ridiculous admin and let the developers do what they do best without having to watch the clock all the time. So what's the verdict? Am I a crybaby or is this genuinely as silly as it all seems? :(

                                        T Offline
                                        T Offline
                                        Tomz_KV
                                        wrote on last edited by
                                        #21

                                        In consulting industry, accurately logging time is a part of the business. Sometimes, in the case of payment dispute, a client may ask for a detailed log of hours spent on its project. In your case, writing note in both system and on whiteboard might not be for billing purpose only.

                                        TOMZ_KV

                                        1 Reply Last reply
                                        0
                                        • L Lost User

                                          I'm a programmer working in a small 7-man team of developers for a web design studio. We work in PHP/Symfony2 (rant for another day) and use Atlassian's JIRA ticket system for tracking issues. We also use it for logging time. :( This being the first job I've had in which time logging has been mandatory (log all work, log 7.5 hours per day) I'm finding it to be a huge obstacle to my productivity. A train of thought is a fragile thing, and stopping after every little thing (sending an e-mail, making a Git commit) to log the time I've spent on it and what I did is proving to be very effective at derailing it. Couple this with the pressure to get 7.5 hours logged on something or other every single day and I'm actually starting to dread coming to work in the morning. Not only this, we now have a completely redundant physical whiteboard full of sticky-notes representing JIRA tickets/issues that must be kept in-sync with the digital system. By hand. We're such a small team, we're all in the same room. But every time we want to fix an issue we need to:

                                          1. Go to JIRA, mark the issue as 'In Progress'.
                                          2. Stand up, walk over the the whiteboard and move the sticky-note to the 'In Progress' column.
                                          3. Sit back down, fix the issue.
                                          4. Go to JIRA, log the time spent on the issue and write a short description of what has been changed.
                                          5. Mark the issue as 'Ready for Review'.
                                          6. Stand up again, :| walk over to the whiteboard and move the sticky-note to the 'Ready for Review' column.
                                          7. Go back to JIRA again and message the QA guys that there's a new sticky note in the 'Ready for Review' column.

                                          I stress again, we're a 7-man web development team trying to be time-efficient, fast and agile. Everyone's practically going crazy about how everything takes too long. Part of it's to do with the bulky toolset we're using, but it baffles me that we can't slim down the ridiculous admin and let the developers do what they do best without having to watch the clock all the time. So what's the verdict? Am I a crybaby or is this genuinely as silly as it all seems? :(

                                          R Offline
                                          R Offline
                                          Roger165
                                          wrote on last edited by
                                          #22

                                          Purchase a 70 inch TV mount it where the sticky notes are and bring up the time management site. Make sure its touch enabled.

                                          1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • World
                                          • Users
                                          • Groups