606
(page 2) 33 comments
sorted by: hot top controversial new old
[-] Underwire@lemmy.world 7 points 5 days ago

When I started working for my current company there were really few meetings and I didn't know that it was possible. Everywhere I worked we had all the Scrum meetings and tech discussions meetings. At that time it was relatively a small company but not that small.

Now the company is getting bigger and some persons try to bring all the scrum shit. Even for small features, we do meetings to discuss them and last for hours. Some meetings have a big agenda that we always only tackle half of it. Sometimes we decide to do something with big impact and then someone suggests to include a person from another that doesn't even know our scope. And then we get "maybe we shouldn't do this as it will maybe have some negative impacts", "maybe we should add an exception" without even giving data to support their claim.

[-] someoneelse@lemmy.ml 6 points 5 days ago

Going against the current for a couple of things, I guess, but there are two points there that I actually like, but probably not in the way they are usually implemented.

  • 4 hours planning is bad if it's 4 hours sprint plannig. Then somebody should be sacrificed for the greater good, but for the love of god, can somebody take their time to plan features and architecture carefully before dumping stories for development? Smaller group and whole long term system overview. Let them spend 4 hours to make something coherent and elimitate tech-debt creation.
  • 1 point = 1 hour is fine if you don't think that it's set in stone, but it allows for very easy sprint planning. If your ballpark estimate for the sprint is more than 20 hours/developer for the week, you are overplanning. Normalize creating tasks for thinking how to solve a fucking problem instead of saying it's complex.
[-] thedeadwalking4242@lemmy.world 2 points 4 days ago

I feel this. No one actually architect’s anymore. They just shit out their first thought and call it a day

[-] CanadaPlus@lemmy.sdf.org 2 points 4 days ago* (last edited 4 days ago)

So what's the actual error margin for estimating feature implementation time? It's going to be nearly the whole thing, right?

load more comments (4 replies)
[-] makuus@pawb.social 4 points 5 days ago
[-] Pika@sh.itjust.works 2 points 5 days ago

are you sure it's not blackout? lmao

[-] smeg@feddit.uk 3 points 4 days ago

Is "blackout" a bingo term for filling every box, or just falling unconscious from overwork?

[-] Pika@sh.itjust.works 2 points 4 days ago

I was meaning filling every slot but that works too!

[-] pyre@lemmy.world 3 points 4 days ago
[-] spongebue@lemmy.world 3 points 4 days ago* (last edited 4 days ago)

Bing (or I guess to keep up with the song, _ingo)

[-] LovableSidekick@lemmy.world 1 points 4 days ago* (last edited 4 days ago)

All-day "Sprint Grooming" meeting

[-] thatradomguy@lemmy.world 1 points 4 days ago

Might as well put the whole Agile/Scrum crap on there while you're at it...

load more comments (3 replies)
[-] exchange12rocks@lemm.ee 2 points 5 days ago

Nah, time tracking is often needed for tax purposes: companies can write off R&D expenses

[-] smeg@feddit.uk 3 points 4 days ago

Yeah but that can be done after you're finished, definitely shouldn't be part of planning!

load more comments (1 replies)
[-] dumbass@leminal.space 1 points 4 days ago

Do people not know how bingo cards work anymore?

load more comments
view more: ‹ prev next ›
this post was submitted on 28 Mar 2025
606 points (99.0% liked)

Programmer Humor

22134 readers
2650 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS