• 0 Posts
  • 6 Comments
Joined 2 months ago
cake
Cake day: February 13th, 2025

help-circle

  • That’s a great way to handle it.

    I like to pass them the ticket and schedule the next open hour on their calendar for them to teach me how to do it, if they’re a developer. Sometimes they do, because I was genuinely missing something easy. Usually they get to awkwardly discuss why they don’t have it done yet, either.

    When the person isn’t even a developer, I’ll explain the usual process between developers, and give them a chance to beg their way out of it.

    If they don’t beg off, I schedule them anyway and see if they can actually at least “rubber duck” me through the problem. (Sometimes it even works.)

    I’ve had a couple peers discover (or rekindle) their love for development this way. Most just make up a reason not to make the meeting, though.


  • They worked well for us

    Yeah. I used story points successfully for years.

    After learning about the above data, I asked my team to trial just counting tickets for velocity, and it also works fine.

    The outcomes weren’t noticably different, so now we just don’t spend the couple hours each sprint that estimating story sizes was costing us.

    My team was hesitant to give up story point estimation, because they didn’t want to give up the communication with leadership about which stories were XXL.

    So we kept using the XXL issue tag, but dropped the rest of the estimation process.