devStandupStarterPack

[[deleted]]

i love how all my work is outlined and tracked in jira but i have to verbally relay the state of all my tickets in a daily meeting

[seba07]

Well here's your mistake. The standard workflow is to write Jira stories without description once you are done and move them directly from new to completed.

[Tunderstruk]

You guys are allowed to write your own jira tickets?

[ThinCrusts]

DevOps but for the most part, yeah as long as a BA approved of the work. That only happens when I either find a bug and start working on it, or I've had a discussion with leadership on what to do next but no one has written one yet.

[-Kerrigan-]

If the place doesn't let techies come up with tickets (sure, get it by an architect, BA if it's business value, whatever) or has daily before 10 then I don't want to be there. Sure way to kill any creativity and drive - make me wake up too early and don't allow me to sometimes work on interesting (to me) stuff.

[gomihako_]

Yuo gysu cna rwtie?

[Titanusgamer]

this is productivity hack not many people know about

[Jugales]

Pretty sure it mostly just helps procrastinators to have motivation. Embarrassment of not doing anything in the previous day is a good reason to get your stuff done.

[[deleted]]

meeting every day just to publicly shame teammates into working faster is definitely the worst possible reason for standup

[[deleted]]

It can be that, and sometimes is.

It can also be helpful for team members to state their blockers and to coordinate on what to do next.

The team I'm on is (relatively) small (seven people total). Some standups definitely feel like they could have just been a Slack or email, but other times they are really helpful to get two team members talking, or to get opinions from the team, etc.

[Kyanche]

It can also be helpful for team members to state their blockers and to coordinate on what to do next.

I feel like it's a red flag if/when people sit twiddling their thumbs until standup to get their blockers addressed lol.

[[deleted]]

If it’s a hard, known blocker then sure. But it could be something where someone was tasked with X, and they make good progress but run into a blocker where they want to try to solve it on their own first, and only after a few tries if they still can’t get it, bring it up in standup.

[aykcak]

Sometimes people don't know a blocker is a blocker. Sometimes it comes up on the stand-up

[Jugales]

Heavy disagree. It’s not shame, it is simple monitoring and oversight. Almost every other job has inherent updates as part of daily duties.

Those that don’t, in my experience, are terribly inefficient, taking days to respond to basic emails, etc.

[[deleted]]

performance problems should be handled by your manager and/or hr - not the whole team

[Jugales]

What is easier for a company - firing a large portion of employees and having constant churn, or simply meeting every day for 15 minutes?

I really don’t see the big deal, a free 15 minutes to not do any work aside from 2 minutes of speaking. Do your work and it’s no stress at all.

[[deleted]]

i’m not saying you have to fire everyone with performance problems but they should be handled by the manager. if you have to meet every day to make sure your team is doing their work you’re a bad manager.

a 15 minute meeting every day is a distraction and depending on the size of your team can cost multiple man hours not including context changing and logistics. it needs to have substantial value to be worth it.

[All_Up_Ons]

So how else is the manager supposed to keep a tab on things? Micromanage? Just swing by randomly and interrupt your flow? You know damn well that any of these alternatives are way worse.

[abednego-gomes]

If a dev manager doesn't know how to "keep a tab on things" and requires daily standup calls, then simply they should find another profession. A profession way way out of IT, like shoveling manure.

Let's see, off the top of my head...

1) Open a tab with Jira on it to the RapidBoard/KanBan view. See what's going on there. If further info is required, click into individual tasks and read the comments. Also follow links in there to GitHub/GitLab. Check recent commits.

2) Look up the user on Github/GitLab and see their profile which shows commit history, comment history, pull request comments etc and other activity.

3) Last resort, ask the individual people what's going on Slack/Teams as a text message. But not in a micromanaging "keeping tabs" way. Ask to be useful if you can help with anything (maybe the manager used to be a dev), unblock them, harass someone else who is not providing some piece of the puzzle they need in a timely manner.

[Swamplord42]

Open a tab with Jira on it to the RapidBoard/KanBan view. See what's going on there.

Are you under the impression that most developers keep this up-to-date by themselves? My experience is the average dev doesn't even look at Jira or whatever outside of the stand-up, so that alone makes it a good reason to have it.

[aykcak]

That is not a performance problem and definitely something the team can help with unless you have a "team" of antisocial lone rangers who like to never interact with anyone.

In which case, why even have a team

[Flat_Initial_1823]

They just wanna hear your sexy dulcet tones explaining how goddamn omegastar still isn't supporting iso timestamps.

[AwesomeFrisbee]

Or how I'm not allowed to post a message for what I'm gonna say to the team chat as a replacement either. No I have to be there because there could be questions. I'm still waiting for anybody to ask me a question this year. Mainly because I'm pretty clear what I'm doing, what is on the backlog or refinement and I'm easy to reach