10 tips on how to prevent business value risk
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
Presentation
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Recorded at:
Facebook: Moving Fast at Scale
How would you like to view the presentation?
In case you are having issues watching this video, please follow these simple steps to help us investigate the issue:
1. Right click on the video player and select Copy log
2. Paste the copied information in an email to video-issue@infoq.com (clicking this link will fill in the default details in most email clients).
Note: in case your email client hasn't automatically picked up the email subject, please include in your email the URL of the video too.
3. Done.
We will investigate the issue and get back to you as soon as possible. Thanks for helping us improve our site!
1. Right click on the video player and select Copy log
2. Paste the copied information in an email to video-issue@infoq.com (clicking this link will fill in the default details in most email clients).
Note: in case your email client hasn't automatically picked up the email subject, please include in your email the URL of the video too.
3. Done.
We will investigate the issue and get back to you as soon as possible. Thanks for helping us improve our site!
Summary
Robert Johnson discusses Facebook’s approach to scalability issues resulting from a large growth of the user base. He talks about: why one needs to prepare for horizontal and not vertical scalability, very short release cycles which are better because they introduce fewer bugs, the need to streamline to deploying process for short release cycles, and making the entire process faster every day.
Bio
Robert Johnson is Director of Engineering at Facebook, where he leads the software development efforts. He was previously at ActiveVideo Networks, leading the distributed systems and set-top software development teams. He received a B.S. In Engineering and Applied Science from Caltech.
About the conference
Starting in 1986, OOPSLA Conference has proven to be the cradle of many techniques and methodologies that have become mainstream over the years: OOP, Patterns, AOP, XP, Unit Testing, UML, Wiki, and Refactoring. Gaining its prestige with 3 academic tracks, OOPSLA Conference has managed to attract researchers, educators and developers every year. The event is sponsored by ACM.
Robert Johnson discusses Facebook’s approach to scalability issues resulting from a large growth of the user base. He talks about: why one needs to prepare for horizontal and not vertical scalability, very short release cycles which are better because they introduce fewer bugs, the need to streamline to deploying process for short release cycles, and making the entire process faster every day.
Bio
Robert Johnson is Director of Engineering at Facebook, where he leads the software development efforts. He was previously at ActiveVideo Networks, leading the distributed systems and set-top software development teams. He received a B.S. In Engineering and Applied Science from Caltech.
About the conference
Starting in 1986, OOPSLA Conference has proven to be the cradle of many techniques and methodologies that have become mainstream over the years: OOP, Patterns, AOP, XP, Unit Testing, UML, Wiki, and Refactoring. Gaining its prestige with 3 academic tracks, OOPSLA Conference has managed to attract researchers, educators and developers every year. The event is sponsored by ACM.
RelatedVendorContent
Getting Started with Stratos - an Open Source Cloud Platform
Why NoSQL? A primer on Managing the Transition from RDBMS to NoSQL
18 agile and lean practices for effective software development governance
Organizational Challenges
by
Bernie Barbour
Posted
Who owns the product?
by
Joseph Taylor
Posted
-
Excellent presentation, thank you.
I was wondering if you could speak or touch on your challenges of scaling organizationally so at 1.1M users per 1 engineer where are all your engineers located?
Are you experiences challenges in ownership of code?
Are you able to scale development across timezones and geographies? -
Thanks for giving us insights into your software engineering processes. It very similar to small agencies where a developer is also a designer and an operations engineer.
Can you give us a little insight on who owns the product or product features? What's the percentage split of engineers vs product owners/managers vs architects?
2 comments
Watch Thread Reply