Anand Rathi adopted agile without changing how anyone works

Product teams at Anand Rathi manage projects in Jira, and their engineers had the reaction engineers usually have to being asked to leave their work and go update a ticket.The result was poor data quality in Jira, which is a polite way of saying the board could not be trusted.Daily standups had the same shape of problem. The team treated them as time consuming, because they were: leave the work, join a call, deliver a status update, return to the work and spend ten minutes finding your place again.

Anand Rathi brought both into Slack with Troopr.Teams stay current on the latest Jira issue updates and act on them directly from Slack when needed. Troopr reminds people about critical project issues in the channel, and each reminder carries a suggested action that is resolved in a few clicks.Daily standups moved to Slack and became asynchronous. Troopr pulls the relevant issue context and recent Jira activity into the report automatically, so the update is grounded in the work rather than in recall.

Anand Rathi adopted agile processes that saved time instead of adding to the day, and did it without changing the workflows the team already had.That combination is what makes adoption stick. Process changes fail when they cost the team something up front.