Artwork

Content provided by Neil Benson. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Neil Benson or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.
Player FM - Podcast App
Go offline with the Player FM app!

Smaller Teams, Bigger Wins: how to split your enterprise apps teams

13:02
 
Share
 

Manage episode 365072968 series 2521928
Content provided by Neil Benson. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Neil Benson or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

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


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.

Support the show

CONNECT
🌏 Amazing Apps website
🟦 Customery on LinkedIn
🟦 Neil Benson on LinkedIn
MY ONLINE COURSES
🚀 Agile Foundations for Microsoft Business Apps
🏉 Scrum for Microsoft Business Apps
📐 Estimating Business Apps
Keep experimenting 🧪
-Neil

  continue reading

155 episodes

Artwork
iconShare
 
Manage episode 365072968 series 2521928
Content provided by Neil Benson. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Neil Benson or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://player.fm/legal.

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


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.

Support the show

CONNECT
🌏 Amazing Apps website
🟦 Customery on LinkedIn
🟦 Neil Benson on LinkedIn
MY ONLINE COURSES
🚀 Agile Foundations for Microsoft Business Apps
🏉 Scrum for Microsoft Business Apps
📐 Estimating Business Apps
Keep experimenting 🧪
-Neil

  continue reading

155 episodes

All episodes

×
 
Loading …

Welcome to Player FM!

Player FM is scanning the web for high-quality podcasts for you to enjoy right now. It's the best podcast app and works on Android, iPhone, and the web. Signup to sync subscriptions across devices.

 

Quick Reference Guide