No, no, and no. A 15-minute standing meeting is much more efficient. Mandating daily email check-ins means developer time would be wasted writing these emails, and everyone's time is then wasted reading these emails and then participating in the ensuing off-topic discussion threads spawned from each email.
A scrum-master's job is remove impediments, and thereby allowing developers to concentrate on development. Mandating that developers generate and then participate in a lot of email noise is counterproductive.
I can read faster than you can speak. I can probably even write faster than I can speak. And most importantly, I can defer both activities to a time when I'm not focusing on something. It's standups that are the impediment.
Comments
No, no, and no. A 15-minute standing meeting is much more efficient. Mandating daily email check-ins means developer time would be wasted writing these emails, and everyone's time is then wasted reading these emails and then participating in the ensuing off-topic discussion threads spawned from each email.
A scrum-master's job is remove impediments, and thereby allowing developers to concentrate on development. Mandating that developers generate and then participate in a lot of email noise is counterproductive.
I can read faster than you can speak. I can probably even write faster than I can speak. And most importantly, I can defer both activities to a time when I'm not focusing on something. It's standups that are the impediment.