filmov
tv
Moving Fast At Scale • Randy Shoup • GOTO 2019
![preview_player](https://i.ytimg.com/vi/suOjtOFfyZg/maxresdefault.jpg)
Показать описание
This presentation was recorded at GOTO Berlin 2019. #GOTOcon #GOTOber
Randy Shoup - Consulting CTO specializing in building distributed systems and high performing teams
ABSTRACT
Most companies slow down as they get larger, but some actually get faster. This talk will discuss the speaker's experiences leading high-performing engineering teams at Google, eBay, and Stitch Fix, and will discuss the organization, the processes, and the culture that can help a company move fast -- and even accelerate -- as it grows.
Modern software-service models take advantage of the great benefits in having the same team both build the software as well as operate it in production -- we call this DevOps, or simply "You Build It; You Run It". What does this mean in practice?
Organizationally, it means small teams with well-defined areas of responsibility, directly aligned with the business. The teams are cross-functional, meaning that each team has all the skill sets it requires to do its job, while at the same time relying on other teams for supporting services, tools, and libraries.
Process-wise, it means doubling down on practices like test-driven development and continuous delivery. Using continuous delivery practices, high-performing teams can and do release their applications and services multiple times a day. This enables them to iterate rapidly, experiment courageously, and fail more quickly.
Culturally, it means end-to-end ownership. Each team owns its software end-to-end, from design to development to deployment to retirement. The same engineers who are responsible for the features are responsible for quality, performance, operations, and maintenance. This ownership puts incentives in the right place to encourage building maintainable, observable, and operable systems from the start.
All these techniques and approaches are available to everyone, and practical examples [...]
Download slides and read the full abstract here:
TIMECODES
00:00 Introduction
00:27 Background
01:36 Organizational Culture
03:08 Theory X vs. Theory Y
04:57 Psychological Safety
06:12 Cross-functional Collaboration
07:47 Google App Engine Reliability Fixit
11:23 Traditional Organizations
12:37 Full-Stack Teams
13:17 Business Alignment
16:23 Engineering Discipline
18:16 The Curse of Knowledge
19:53 Lean Software Development
26:03 Iterative Development
32:26 Minimal Viable Feature
34:10 Definition of Done
37:52 Moving Fast at Scale
#DevOps #HumanFactor #DeveloperProductivity #TDD #ContinuousDelivery #CD
Looking for a unique learning experience?
SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.
Randy Shoup - Consulting CTO specializing in building distributed systems and high performing teams
ABSTRACT
Most companies slow down as they get larger, but some actually get faster. This talk will discuss the speaker's experiences leading high-performing engineering teams at Google, eBay, and Stitch Fix, and will discuss the organization, the processes, and the culture that can help a company move fast -- and even accelerate -- as it grows.
Modern software-service models take advantage of the great benefits in having the same team both build the software as well as operate it in production -- we call this DevOps, or simply "You Build It; You Run It". What does this mean in practice?
Organizationally, it means small teams with well-defined areas of responsibility, directly aligned with the business. The teams are cross-functional, meaning that each team has all the skill sets it requires to do its job, while at the same time relying on other teams for supporting services, tools, and libraries.
Process-wise, it means doubling down on practices like test-driven development and continuous delivery. Using continuous delivery practices, high-performing teams can and do release their applications and services multiple times a day. This enables them to iterate rapidly, experiment courageously, and fail more quickly.
Culturally, it means end-to-end ownership. Each team owns its software end-to-end, from design to development to deployment to retirement. The same engineers who are responsible for the features are responsible for quality, performance, operations, and maintenance. This ownership puts incentives in the right place to encourage building maintainable, observable, and operable systems from the start.
All these techniques and approaches are available to everyone, and practical examples [...]
Download slides and read the full abstract here:
TIMECODES
00:00 Introduction
00:27 Background
01:36 Organizational Culture
03:08 Theory X vs. Theory Y
04:57 Psychological Safety
06:12 Cross-functional Collaboration
07:47 Google App Engine Reliability Fixit
11:23 Traditional Organizations
12:37 Full-Stack Teams
13:17 Business Alignment
16:23 Engineering Discipline
18:16 The Curse of Knowledge
19:53 Lean Software Development
26:03 Iterative Development
32:26 Minimal Viable Feature
34:10 Definition of Done
37:52 Moving Fast at Scale
#DevOps #HumanFactor #DeveloperProductivity #TDD #ContinuousDelivery #CD
Looking for a unique learning experience?
SUBSCRIBE TO OUR CHANNEL - new videos posted almost daily.
Комментарии