Hacker News new | ask | show | jobs
by byoung2 2368 days ago
Meetings / stand ups

We have recently automated stand ups, so the what I did yesterday/what I will do today/blockers are all pulled from Jira so now we only discuss major sprint goals and how to unblock any blockers...this reduces the meeting to just the important stuff

3 comments

Doesn't that completely negate the point of a stand up?

A stand up is already short and down to "the important stuff" and it is a key part of the process that the people attending express themselves and listen.

How often is Jira up to date for you? I've often seen that standup can be a chance for folks to realize they didn't update a task. We'd have Jira open and just do live updates to sync it.
We use git hooks to tie issues and commits together. I think Azure DevOps and some other PM software also does this without hooks.

Basically our team can't complete an issue without a commit, and a commit message won't be accepted without an issue tag.

(Issues can also be closed as "won't fix" without a commit of course.)

nice

Does this mean keeping all status up to date in Jira? would you mind sharing how you do this?

> would you mind sharing how you do this?

Not GP and not my personal experience, but I have a friend whose company has a non-developer do this as part of their full-time responsibilities. They privately check in with every developer at the end of every day.

We have really pushed the "Jira as the source of truth" mantra. Git commit hooks keep Jira up to date as far as moving tickets into "ready for review" when the PR is submitted, and into test when the PR is approved. The only manual cases are when a ticket is moved into "in progress" or blocked, otherwise it is assumed yesterday you worked on the last ticket you had in progress, and today you will continue it