Explore how organizational structure impacts software development in this 51-minute conference talk from Philly ETE 2016. Delve into the often-overlooked aspects of team and organizational architecture, and their profound effects on product outcomes. Learn strategies to prevent organizational pitfalls from undermining your software projects, and discover ways each team member can contribute to improvement. Examine topics such as time dilation, technical debt, rewriting challenges, team composition, complexity vs. flexibility, consensus-building, and the role of product management. Gain insights on optimizing team size, specialization, code duplication avoidance, and the importance of architects. Understand the implications of open-source development and how to balance organizational needs with software architecture for more effective product development.
How Your Organization Is Killing Your Software - Improving Team and Product Architecture
Overview
Syllabus
Intro
Time dilation
Raffis background
How to make your team go faster
How to make sure things dont take longer than you think
The first thing that an org usually does
Technical debt
Rewriting
The 5 stages of rewrite
Do you have the right team
Compilers
Complexity vs Flexibility
Small Teams
Reaching Consensus
Making Product a dictatorship
Asynchronous Mode Transfer Networking
Product needs to be a dictatorship
Recap
Would Twitter be better if everything was still on Ruby
Teams and making smaller
Breaking into specialized teams
Avoiding code duplication
How big is a team
Single products
Architects
Open Source
Taught by
ChariotSolutions
