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

Amazing Apps - learn how to build agile Dynamics 365 and Power Platform business apps using Scrum

Neil Benson에서 제공하는 콘텐츠입니다. 에피소드, 그래픽, 팟캐스트 설명을 포함한 모든 팟캐스트 콘텐츠는 Neil Benson 또는 해당 팟캐스트 플랫폼 파트너가 직접 업로드하고 제공합니다. 누군가가 귀하의 허락 없이 귀하의 저작물을 사용하고 있다고 생각되는 경우 여기에 설명된 절차를 따르실 수 있습니다 https://ko.player.fm/legal.

1+ y ago 13:02

MP3•에피소드 홈

#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

156 에피소드

#Business #Agile #Scrum #Neil Benson #MBA #Enterprise Resource Planning #Scrum Master #Software #Microsoft #Tech #Programming #Software Development #Industries #Podcasting Education #CRM #ERP #Customer Relationships Management #Development #DevOps