Is there a way to use JIRA for daily standup meeting?

[Rafal Sroka]

Our daily stand up meeting

Most developers make notes about what they will talk about, simple text list with done and to-do section. Tickets they worked on are listed there.

Is there a way to simplify this, drop the notes and use JIRA for daily standup meeting?

Requirements:

Developers want to see tasks they worked on grouped in done and to-do sections. This is a problem because a task assigned to a tester does not have a developer that worked on it as an assignee anymore.

Any ideas or feedback how to use JIRA for a daily standup meeting are super welcomed!!

[Mohamad Khalife · Accepted solution]

You should create custom field named "Developer" and capture its value before the development start. Then developers can build filters (reports) based on this field

[MeghnaP_LogicLemur Labs]

this can be one of the way @Mohamad Khalife but you'll not able to get details of the reason why standups are conducted, viz. Active blockers for the sprint to deliver desired results. 

We've identified the these user pains and created Daily Standup Governance for Jira which will list all active blockers to facilitator and govern it better way. 

Try this out and let me know your view on it. 

[Doug Swartz]

JIRA supports the JQL clause "Assignee was someUserId" . You could use this capability to build quick filters on your board by developer which would include all stories the developer worked on.

[MeghnaP_LogicLemur Labs]

This comes up a lot, and yes, you can absolutely use Jira without turning standup into a note-taking exercise @Rafal Sroka 

This is exactly what Daily Standup Governance for Jira does.

Instead of developers writing “done / to-do” notes, the app auto-builds the standup from Jira itself:

Done = issues the developer actually worked on since the last standup
To-do = what they’re expected to pick up next

It does not rely only on current assignee,  so even if a ticket moves to QA, the developer still sees it under their “done”.

Standup becomes a quick review of real work, not a memory test.
Nothing disappears after 15 minutes, and no extra process for the team.

If you want Jira to be the standup, this works really well.

[emily]

Spinach.io allows teams to flex between live and async standups, and has a Jira integration.

Prep in Slack
Pull in (and link to) specific Jira tickets
Share updates in half the time live (or async)
Instant summary to reference throughout the day in Slack

Try at Spinach.io

[Ivan Hanák]

Hi, for all of the people who are still looking for an option to run the scrum standups directly in Jira, we developed the addon exactly for that purpose: https://marketplace.atlassian.com/apps/1222836/daily-standups-for-jira and some teams using are using also "management standups" to check up on objectives.

Supports also Slack notifications.

[Magdalena Zacharczuk]

Hi Rafal,

Here's my (better late than never) 10 cents. The fact that most developers prefer to work with paper notes during standups seems to reflect the concept that Joel Bancroft-Connors presented in his blogpost on why physical task boards still matter.

Would you be open to considering a scenario where JIRA and the developers' notes on a physical board coexist and can easily be synced? The Agile Cards for JIRA add-on can facilitate this. Your developers could print their tasks from JIRA as paper cards, with a specific card color assigned to each developer. With such a color-coded physical board it would be easy to track which task belonged to whom originally, no matter the stage in the workflow. After each standup your board in JIRA and the one on the wall could easily be synced by using the Agile Cards scanner feature.

Would this work for you?

Kind regards,

Magdalena from Spartez 

[Dennis Poort]

Maybe you could create a seperate issue (sub-task or related issue) to assign to the tester, seperating development and testing. This way you keep the assignee of the developer in tact.