Regular updates on the bug/task tracking systems together with notification and Q&A on a more stream based async system like Slack work well for us. Lack of activity is usually a sign of an issue, usually someone being stuck, a bit down or on a roll. All need a check-in, even the on-a-roll person as sometimes they get carried away without letting people know about changes. We tend to have weekly in-person synchronisations meetings.
This does really vary hugely from team to team and even project to project though. I fear "agile" methods have forgotten the meaning of the word they are based on at times. Regular re-factoring also applies to development and operational models I find.
Comments
Regular updates on the bug/task tracking systems together with notification and Q&A on a more stream based async system like Slack work well for us. Lack of activity is usually a sign of an issue, usually someone being stuck, a bit down or on a roll. All need a check-in, even the on-a-roll person as sometimes they get carried away without letting people know about changes. We tend to have weekly in-person synchronisations meetings.
This does really vary hugely from team to team and even project to project though. I fear "agile" methods have forgotten the meaning of the word they are based on at times. Regular re-factoring also applies to development and operational models I find.