ProgrammerHumor
pleaseCompilerGod
Discussion
You do work before standup?
My current "standup" is near the end of my workday. Combination of timezone issues for a distributed team, and a boss who has a whole other slate of projects to manage in the mornings. (And yes, my boss is in the "standup", which part of the reason I'm putting it in quotes)
I had something similar to that for a while and hated it with passion. "Stand up and leave for home"
Anyone can be in the stand-up. Bosses are generally not allowed in retros for maintaining psychological security but stand-ups are fair game. In fact, they can often provide useful context which may make them desirable to be in a stand-up and show their commitment to the success of the team. If a boss is disruptive it is the job of the scrum master to communicate that to the boss and either coach them or convince them not to come. If the boys doesn't listen to that, then you've got a bigger problem than what agile says.
That depends on whether your morning calls are go-around-the-horn stand ups or actual scrums. With the former in some kind of Kanban system then yeah a PM or PO may want to be at a status call to get an idea of what's being worked on. With the latter however, if your boss isn't a developer on the team then they really shouldn't be there. The daily scrum is for developers to formulate a plan of action for the day and PMs and POs shouldn't be there. Heck, the Scum Master doesn't even need to be there if they're not a developer.
Yes that is what it is for. But for both the PO and the scrum master to attend is considered a positive. If you're not batching the acceptance of all the stories to the end then it's an opportunity to coordinate with the PO to get early validation of features, to get clarification on any confusion or product direction decisions needed to be made. It's not a requirement and you need to train the PO to not compromise psychological safety but it isn't a bad thing by default.
Scrum alliance reference What Is the Daily Scrum? | A Guide to the Daily Event | Scrum Alliance https://share.google/w5dzRp4kFiH38ksv8
Scrum inc article https://share.google/qUNE4CfT6jwSlOe5j
If a boss is disruptive it is the job of the scrum master to communicate that to the boss and either coach them or convince them not to come.
That's just it --we don't have dedicated scrum masters, so the boss fills that role.
The call is coming from inside the house!!1!
Well, if the boys doesn't know what they're supposed to do then yeah that makes sense
My favourite thing to say in stand-up is "I'm clocking out in a couple of hours".
I wake right before standup
I do work during my standup
just say you cant comment, the build hasnt finished yet
Why would you want the build to finish before standup? You can just say âbuild is in progress, no other status at this timeâ.
Said that so many times I started to feel like a Woody doll with a pull-string.
"No, not yet. Yes, I am still on it. Yeah, I know it only had 3 story points, but I am still not done. Yeah, I will probably be finished today"
Bonus points if you give this update for a week straight.
be me, gets a 6 hours ticket, proceeds to spend 40 hours of work on it and acts like nothing happened.
it's actually better if it doesn't
I share screen for 3 seconds showing the compilation process, and I'm off
Why? As long as it builds it is a normal part of the process
Release happens in 2hrs, you have a simple bug on hand, u have fixed it and fix is in PR, u inform team all good and fix can go in before release, Jenkins bot mails pops up unit test failure, you login into Jenkins, it is slow af due too many pr ci pipelines. You finally manage to get to the test failure from a 10k line log file. You run the test locally it passes. You look at the clock deadline in 10min. You pray and rerun Jenkins build and hope for the best
just say it's done during standups. hahahaha. if it doesnt work after, just say you overlooked some bugs đ
Wouldnt it be better? You can say that "compilation is taking longer than expected, but in theory if it works, <insert jargons here>", ergo, good work done
Your Scrum master and/or boss must be pretty nosy if youâre trying to get stuff done before standup lol. Iâd just say your team is working on the build and you plan on troubleshooting any issues, no blockers
Y'all mfs don't build on local before you push? Moreso you don't run your shit on local for a smoke test too?
Why would I want to run such buggy and possibly destructive code on my machine? I have to work on my machine!
The soul of the Machine God surrounds thee.
The power of the Machine God invests thee.
The hate of the Machine God drives thee.
The Machine God endows thee with life.
Live!
lol
What are they gonna do, go check on the deployment?
Me looking at my DTS test suites running during the meeting
God bless theminutehour
Where is this meme template from
Why wouldnât you want your update to be that youâre waiting for the build to finish?
just for the CI pipeline to tell you to go fuck yourself last minute
Jesus, how long do your builds take?
"I can surely leave early today and just complete this task before the stand-up tomorrow", I tell myself way too frequently.
Wait dont you want it to be building during standup so you can shirk all responsibility?
why do you need a finished build to say "no blockers"?
What if a test fails? That's a blocker!
no, it's not. a blocker is when something is waiting on something from another team. or something from another team member.
I'm enjoying the idea however of somebody enthusiastically embracing TDD and contributing to a stand-up by enumerating their failing not-yet-implemented test cases as "blockers".
Not at the time you said no blockers.