Wellthy's engineering team got its ceremonies and its Jira hygiene back

Wellthy's engineering team is small, engaged in Slack, and had the same Jira problem as much larger organisations.Jira was not always current and did not give the full picture of project progress. The director of engineering wanted better visibility, and the only levers available were asking people to update Jira more often and asking people for status directly. Both make the manager the mechanism, and neither scales past a certain point of goodwill.Small teams feel this more acutely than large ones. There is no programme manager to absorb the gap.

Wellthy moved its ceremonies and its Jira maintenance into Slack with Troopr.Engineering teams run scrum ceremonies asynchronously, which saves time for a team that cannot afford to lose an hour a day to meetings. They discuss and act on Jira issue updates from Slack rather than going to find them.Managers set the team up with Troopr's reminders and nudges, so the prompt to update a stale issue comes from the system rather than from a person.

More efficient ceremonies and better Jira hygiene mean everyone at Wellthy stays on the same page about project progress while spending less time getting there.The change that matters most for a team this size is that the director of engineering stopped being the chasing mechanism.