48
Deleted (programming.dev)
submitted 10 months ago* (last edited 1 week ago) by stembolts@programming.dev to c/programming@programming.dev

.

you are viewing a single comment's thread
view the rest of the comments
[-] stembolts@programming.dev 2 points 10 months ago

Alright, I never thought about the daily meetings like that, probably because of the context with which they started. It started because the guy who manages the points doesn't develop or understand software, he just reports progress of the team via points to the contract-host-company (we're all contractors on my team).

I'm not involved in any planning, I just get assigned stuff. As far as estimating how large the bugs are, that would be me, but I've only arrived working on this new code base three months ago so my estimates would be random guesses since I don't understand the larger context of any of the jobs, nor how the moving parts fit together. So what I do is take a job, then just add two points every day, one of my tasks is well over thirty points at this time.

I'm not sure how task difficulty is determined or if it is at all? It seems to be more that they chose these bugs just because they make sense for a new team member to get working on something, but that's just a guess.

this post was submitted on 01 Mar 2024
48 points (100.0% liked)

Programming

17765 readers
334 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS