Mission adopted scrum across time zones without adopting more meetings

Mission's engineering team was being introduced to agile and working to adopt scrum ceremonies properly.Adopting a new process is hard enough when everyone is in one place. Mission's engineers are spread across time zones, so every ceremony carried a scheduling problem on top of the process change. Finding a suitable time was a challenge, and a ceremony that is hard to attend is a ceremony that quietly stops happening.Keeping Jira current was the other open problem, and the two were related. Ceremonies are where Jira usually gets corrected, so a ceremony that does not happen reliably means a board that does not get corrected reliably.

Mission's teams already collaborated in Slack channels, so the ceremonies went there.With Troopr, scrum ceremonies run asynchronously. The team participates at whatever time works for them, and the report assembles itself. There is no slot to negotiate, which means the ceremony actually happens.Alongside it, engineers receive actionable alerts about specific Jira issue updates in Slack and take action from the channel without leaving it.

Mission saves roughly 20 minutes a day per person on the daily scrum, and Jira accuracy improved without a separate effort to make it improve.Adopting agile succeeded because the ceremonies were made easy to attend rather than mandatory to attend.