“You have an issue in the sprint without any story points. Why doesn’t it have any story points?All sprint issues must be pointed.”
Well fuck, Janice, I don’t know. All I’ve done so far is click “Assign to me”. There’s no evaluation yet! I have no idea what the root cause is or how long it will take to fix.Let me cook goddammit.
As someone who works as a software engineer for a smaller company without any of that noise, that sounds like complete hell. I have no clue how devs are getting anything useful done while having to context switch constantly during the day for asinine meetings and corporate progress tracking bullshit.
I literally would not work for a company if they made me do story points.
We do have a scope rule which is intentionally ambiguous, but the idea is a ticket ought not take more than 3 days, and some can be quicker. We expect the average time to meet our velocity and prioritize accordingly. If an effort seems like it will take longer we try to divide it into smaller tickets.
There may be like 5 tickets a year where this doesn’t hold true and we are ok with it. Nothing to be religious about.
The other issue is the amount of points it is totally depends on who does the work! It’s a garbage system to estimate work. Makes people think they have some sort of idea that is more misleading and harmful than just saying “I don’t know exactly but you can expect it to get done promptly because we’ve taken proper steps to analyze and break down the work to be bite sized and delivered consistently.”
@CountVon@soloner In our company every person in the team (dev, qa, doc writer, po) is estimating the story points in secret, then we reveal them and mostly take the average. Our experience is that we all are mostly in the same range.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programmerhumor@lemmy.ml
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.
Slack DM, three minutes after I pick up an issue.
“You have an issue in the sprint without any story points. Why doesn’t it have any story points? All sprint issues must be pointed.”
Well fuck, Janice, I don’t know. All I’ve done so far is click “Assign to me”. There’s no evaluation yet! I have no idea what the root cause is or how long it will take to fix. Let me cook goddammit.
As someone who works as a software engineer for a smaller company without any of that noise, that sounds like complete hell. I have no clue how devs are getting anything useful done while having to context switch constantly during the day for asinine meetings and corporate progress tracking bullshit.
I literally would not work for a company if they made me do story points.
We do have a scope rule which is intentionally ambiguous, but the idea is a ticket ought not take more than 3 days, and some can be quicker. We expect the average time to meet our velocity and prioritize accordingly. If an effort seems like it will take longer we try to divide it into smaller tickets.
There may be like 5 tickets a year where this doesn’t hold true and we are ok with it. Nothing to be religious about.
The other issue is the amount of points it is totally depends on who does the work! It’s a garbage system to estimate work. Makes people think they have some sort of idea that is more misleading and harmful than just saying “I don’t know exactly but you can expect it to get done promptly because we’ve taken proper steps to analyze and break down the work to be bite sized and delivered consistently.”
@CountVon @soloner In our company every person in the team (dev, qa, doc writer, po) is estimating the story points in secret, then we reveal them and mostly take the average. Our experience is that we all are mostly in the same range.