Damn! Team Just do it!!!

  • oleorun@lemmy.fanEnglish
    56·
    1 year ago

    Belle! Stop saying “I do declare” for your constants! It’s not valid syntax!

    • normalmighty@lemmy.world
      10·
      1 year ago

      My team has being trying an approach where instead of story pointing, we break everything down into the smallest incremental tasks we reasonably can and use number of tasks overall as the metric instead of story points.

      In theory it’s meant to be just as accurate on larger projects because the larger than normal and smaller than normal tasks all average out, and it save the whole headache of sitting around and arbitrarily setting points on everything based mostly on gut feeling.

      • Doc Avid Mornington@midwest.socialEnglish
        5·
        1 year ago

        I remember reading a study done across some large organizations that showed this approach was more accurate than other estimation techniques. Makes sense to me.

      • zalgotext@sh.itjust.works
        3·
        1 year ago

        Huh. That’s such a simple and obvious approach, I’m kinda mad I’ve never thought of it lmao. It seems like you’re essentially breaking everything down to a 1 (or as close as you can get it), which is probably a more accurate measurement anyways. Neat.

      • PixelProf@lemmy.ca
        1·
        1 year ago

        When I teach story points (not in an official Agile Scrum capacity, just as part of a larger course) I emphasize that the points are for conversation and consensus more than actual estimates.

        Saying this story is bigger than that one, and why, and seeing people in something like planning poker give drastically differing estimates is a great way to signal that people don’t really get the story or some major area wasn’t considered. It’s a great discussion tool. Then it also gives a really rough ballpark to help the PO reprioritize the next two sprints before planning, but I don’t think they should ever be taken too seriously (or else you probably wasted a ton of time trying to be accurate on something you’re not going to be accurate on).

        Students usually start by using task-hours as their metric, and naturally get pretty granular with tasks. This is for smaller projects - in larger ones, amortizing to just number of tasks is effectively the same as long as it’s not chewing away way more time in planning.

        • NotSteve_@lemmy.ca
          13·
          1 year ago

          Haha they’re just different ways of estimating the difficulty of a work task. Story points are a kind of estimate that are represented by a number. The larger the number the more difficult the task.

          My company uses WAG (wild ass guess) time estimates where we have to actually say how long we think a task is going to take in a matter of days or weeks. It sounds fine but programming tasks are notoriously hard to estimate since you have to consider so many different factors. I’m especially bad at it so I’d much prefer just saying “this task is an 8 because it seems hard”

          • JonEFive@midwest.social
            7·
            1 year ago

            It’ll take 20 hours. Unless it’s harder than I thought. Or it’s easier than I thought. Or it’s exactly as hard as I thought except there’s one little thing that I get stuck on for 5 hours.

            • NotSteve_@lemmy.ca
              2·
              1 year ago

              I recently estimated a task to take a couple hours but it ended up taking a week. Hadn’t considered having to update a bunch of other teams services with new proto schemas and making sure they were deployed before our own service 🙃

  • Steeve@lemmy.ca
    9·
    1 year ago

    Let’s also have you do a master rank codewars kata… on the whiteboard. You have 30 minutes.

  • spez@sh.itjust.worksEnglish
    1·
    1 year ago

    We have been getting pressure from customers whether or not this substring is a palindrome