How to attract more attendees to Atlassian Demo Meetings

[Alex Gay]

Case: 

After every sprint we have our 'Demo meeting' for our team. (sequence of 2 weeks)

We manage multiple applications like ITSM tools and Testing tools, but also Jira and Confluence.

We invited over 120 members and have an attendance of 30 persons during the meeting.

But none of them are there for the Jira and Confluence topics.

We have over 3800 Jira users and invited the entire scrum master community.

We show some results 'live' on what we did during the previous sprint.

We show our planning for the next sprints (in Plans) 

Question: 

How can we make more stakeholders / users attend our Demo meetings?

Do you have some tips and tricks to make it interesting for the users?

[Fabian Lim]

Hi @Alex Gay

I wouldn't focus too much on numbers. It would be more important to ensure that when you deliver something the stakeholders who requested that feature are there to provide feedback. 

It's also possible that the meeting time conflicts with something else. We do our demos on ms teams and record them and post them in confluence sprint x demo page for people to view later.

The only tip I have is to send out and agenda of what you will be demoing so people would attend based on their interests.  

Regards

[Christine P. Dela Rosa]

I agree with @Fabian Lim , @Alex Gay . Are there questions from those who do attend or good follow-up actions taken as a result? If so, that seems like a really good engagement rate for 25% of an invite list.

Also, as a recruitment tool, you could try asking those who don't attend what they're looking for. Is there something they want that's not being offered? If the time isn't accessible, would a recording help? Or perhaps a sense of social community is what they're looking for, and other elements outside of demos might bring in the crowds. The answer to your question could be a matter of better understanding what people want.

[Sedera Randria]

Does it make sense to try a Lean Coffee once? You can list expectations and ask people to vote before the next meeting. Then you can build an agenda based on the most voted topics.

[Alex Gay]

Thx for the feedback.

We record the demo's in Teams and make them available.

What I don't like about the demo's in Teams is (in our case) that there is no feedback from the attendees during the demo.

Maybe because we are recording?

We have a new scrum master since this month, this will be a topic in one of the future retro's ;-)

[Christine P. Dela Rosa]

Oh. It would be interesting to share the recorded demo and prompt a question from it. Like: "what do you want to see done differently for the next demo?" Or, "what's one thing you learned or didn't realize after watching this?" A little gamification for rewarding those who engage couldn't hurt either ;)