#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.


(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.

Support the show

๐ŸŒ Amazing Apps website
๐ŸŸฆ Customery on LinkedIn
๐ŸŸฆ Neil Benson on LinkedIn

๐Ÿš€ Agile Foundations for Microsoft Business Apps
๐Ÿ‰ Scrum for Microsoft Business Apps
๐Ÿ“ Estimating Business Apps

Keep experimenting ๐Ÿงช