When we adopted this in my team, we started by agreeing to a timeline in which we would evaluate if we wanted to use it or not. By giving people "an out" after 2 months, it reduces the risk they have to accept initially. We rolled it into our agile ceremonies to make scheduling simpler, and had the loudmouth (me) on the team lead it as it forced them to shut up and listen to the others more. Everyone actually really loved it and felt it helped the team deliver the tool we built.
Put an hour on your team's calendar and drop the project team health monitor link (or whichever health monitor you're looking at) in the meeting details. So long as everyone shows up ready to share honestly and discuss with the intention of getting to a better place, there doesn't need to be a ton of prep. The sessions will adjust to your team's style over time.
For a deeper dive, take a look at "Everything you wanted to know about the Health Monitor (but were afraid to ask)" on the Atlassian Blog.
Teamistry, Atlassian’s first podcast (launched March 16th), looks past the front page headlines to discover incredible untold stories of teams behind the scenes who joined together to do what no...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events