Scrum Master Engagement Patterns: The Development Team

TL; DR: Scrum Master Engagement Patterns

Last year, I ran a (non-representative) survey on how Scrum Masters are allocating their time when working with a single Scrum Team. Much to the surprise of many readers, the direct Scrum Master engagement with a single Scrum Team of average size and a typical 2-week Sprint turned out to be about 12 hours per week.

This result immediately prompted two additional questions: What are Scrum Masters doing during the rest of the week, and in what way does a Scrum Master’s work manifest itself over time? While answering the above question requires additional research and data collection, the latter can be answered to a certain grade by focusing on a few common scenarios.

The first article of this series will address the Scrum Master engagement with the Development Team.

Scrum Master Engagement Patterns: The Development Team — Age-of-Product.com

Continue reading Scrum Master Engagement Patterns: The Development Team