this post was submitted on 02 Oct 2024
654 points (97.0% liked)

Programmer Humor

32831 readers
688 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] funkless_eck@sh.itjust.works 99 points 3 months ago (3 children)

The purpose of stand up is to not listen to anything and say a sentence that no one listens to. It's like a Buddhist meditation.

[–] hannesh93@feddit.org 28 points 3 months ago

Yeah - it's an art to find the perfect mix between "sounds complicated enough that they zone out", "sounds like stuff gets done" and "not making people ask if you need help with that".

[–] frezik@midwest.social 11 points 3 months ago

Lemmy keeps it real.

[–] snek_boi@lemmy.ml 1 points 3 months ago* (last edited 3 months ago) (2 children)

lol I hope your standups are not actually like this! The purpose is to, as a team, plan what the team will do today to achieve the Sprint goal

[–] funkless_eck@sh.itjust.works 5 points 3 months ago

I'm not actually a programmer (/engineer) I'm just a hobbyist. I work in supply chain, have worked at 4 companies in 8 years - all had stand ups, all of them are like this.

[–] thanks_shakey_snake@lemmy.ca 2 points 3 months ago (1 children)

Err... Is your team doing planning during standup? I've never heard of that, from either people who are on teams that use standups, or from any of the Agile/Scrum literature that I've seen. In my experience, standups are typically about either a) coordinating the execution of work that has already been committed to, or b) whoops just a status meeting and everybody's tuned out.

[–] snek_boi@lemmy.ml 1 points 3 months ago

Ah, I see how my wording was confusing. I mean planning in the sense of “How will we complete the work that we already committed to?” and “What will we do today to achieve our Sprint goal?”

I arrived at the word planning because Scrum is sometimes described as a planning-planning-feedback-feedback cycle. You plan the Sprint, you plan daily (Daily Scrums), you get feedback on your work (Sprint Review), and you get feedback on your process (Sprint Retrospective).