Главная
Study mode:
on
1
Intro
2
Time dilation
3
Raffis background
4
How to make your team go faster
5
How to make sure things dont take longer than you think
6
The first thing that an org usually does
7
Technical debt
8
Rewriting
9
The 5 stages of rewrite
10
Do you have the right team
11
Compilers
12
Complexity vs Flexibility
13
Small Teams
14
Reaching Consensus
15
Making Product a dictatorship
16
Asynchronous Mode Transfer Networking
17
Product needs to be a dictatorship
18
Recap
19
Would Twitter be better if everything was still on Ruby
20
Teams and making smaller
21
Breaking into specialized teams
22
Avoiding code duplication
23
How big is a team
24
Single products
25
Architects
26
Open Source
Description:
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

ChariotSolutions
Add to list
0:00 / 0:00