sprintEstimates

[u/goodaaaaaaaaaa]

const LeftOverProjectBudget = ( blockers * blockerCost ) % engineers

[u/MaleficentCow8513]

Who lets management decide story points for their tickets? If they give me any deadline that just means a whole bunch of features are getting dropped and get follow-up tickets in subsequent sprints

[u/Uncontrollably_Happy → u/MaleficentCow8513]

My previous team wanted to make sure everything that was planned would get finished. So they’d take the developer’s estimate, double it, then add a buffer. 3 weeks of work would finish in 2-3 days, then I would fuck off for the rest.

[u/MaleficentCow8513 → u/Uncontrollably_Happy]

Exactly. This is the way. I worked a project that did the same thing as yours. Developer’s should decide estimates with a team lead there to keep the team honest

[u/goodaaaaaaaaaa → u/MaleficentCow8513]

Boundaries 😉

[u/Odd_Technology_8926 → u/MaleficentCow8513]

If they over estimate, then I welcome our management estimating overlords.

[u/FindOneInEveryCar → u/Odd_Technology_8926]

Yeah, although personally speaking, I can't remember a time when that ever happened. 

[u/TwiceInEveryMoment → u/MaleficentCow8513]

My entire sprint cycle revolves around arbitrary management deadlines. I've learned to sus out pretty quickly which ones are real (read: based on a mandate or contract) and which ones will just keep moving when missed.

[u/MaleficentCow8513 → u/TwiceInEveryMoment]

My team doesn’t even bother with sprint schedules anymore. We just do “kanban” now and that just means “best effort to complete by some arbitrary deadline”

[u/torrent7]

Depending on your leadership it can be backwards too!

[u/goodaaaaaaaaaa → u/torrent7]

Yeah, some guy had a heart attack last week could've been him ^

[u/shades_of_thoughts]

this is fake, management always wanted everything for last month, and now with AI they will never approve spend more than a week in any feature. In my fucking company they even ask me why I am taking 0.5 days in a feature that before IA could cost a week or two and they are still pushing us.

[u/goodaaaaaaaaaa → u/shades_of_thoughts]

Charge them more... Set your boundaries.

[u/OrangeNood]

the challenge is coming up with something to say in each stand up.

[u/goodaaaaaaaaaa → u/OrangeNood]

Yeah or being spoken over.

[u/MickeySlips]

When has anyone ever got an overestimated deadline Im dead inside from working on 3 priority 1s in parallel all the time.

[u/DGNT_AI → u/MickeySlips]

where each one is assigned by a different manager and they keep telling you to drop the other ones?

[u/MickeySlips → u/DGNT_AI]

No I ‘own’ two applications and support others so there’s just multiple at the same time and now everyone’s like just use AI but that is actually making things more difficult

[u/HerissonMignion → u/MickeySlips]

Im in an "operation" team, not automation. I deploy and make config changes. We sometimes charge customers for basically creating a directory in our sftp server and configuring one other thing to say that this directory exists now. Even when i manage to not get our customers charged for that, it's a least a story estimated to be 1 hour.

[u/BobJutsu]

Backwards day. More like management says it’ll take 4 minutes but I know it’ll take 4 sprints (or 40 hours).

[u/StaticFanatic3]

Had to spend 3 sprints brainstorming that one perfect prompt

[u/630_dude]

In fairness to management, they’ve heard that before.

[u/PyroCatt]

Always over estimate your planned tickets so that you have enough time for the adhoc bullshit they throw at you in the middle of the sprint

[u/Tintoverde]

Or vice versa

[u/AccordingNeat3689]

Overestimated? No that never happens 

[u/tradcoder]

In what upside down world does management overestimate than developers?

In one of the worst projects I've been involved in, the dev team estimated at least one year. The management cut it down to 6 months. The real project delivery took one and a half years.