#142. Neil Benson discusses the challenges of organizing a large Scrum team to maximize efficiency. He suggests rotating developers between teams and organizing teams around specific components or external systems they need to integrate with. Neil also recommends self-organizing teams and coaches teams to create their own code of conduct and establish expected behaviors. He shares his experience of organizing teams by components in the past at RACQ and why it wasn’t the best approach.

TIMESTAMPS
02:52 Large team split into component-based teams for Scrum framework.
04:49 Organizing teams by component creates interdependencies and hinders productivity; a Better approach is having a team with all the necessary skills.
08:27 Allowing developers to form their own teams empowers and trusts them to be accountable for their work, rather than having a manager organize teams.
11:16 Amazing Apps Retrospective: behind the scenes.

RESOURCES

ESTIMATING BUSINESS APPS PODCAST

🎧 Estimating Business Apps is a five-part podcast mini-series that will help you quickly, accurately and confidently estimate complex Power Platform and Dynamics 365 apps.

SUPPORT AMAZING APPS

Buy Me a Coffee
Rate This Podcast
🟥 Subscribe on YouTube

MY ONLINE WORKSHOP & COURSES

3️⃣ Secrets for Building Amazing Business Apps with Scrum (FREE)
🚀 Agile Foundations for Microsoft Business Apps (FREE)
🏉 Scrum for Microsoft Business Apps
📐 Estimating Business Apps

CONNECT

🟦 Customery on LinkedIn
🟦 Amazing Apps group on LinkedIn
🟦 Neil Benson on LinkedIn

Keep experimenting 🧪