data driven software development

13
10.20.2005 The need for Data-driven Software Development St Mary Axe, February 2015

Upload: james-governor

Post on 16-Jul-2015

214 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: Data Driven Software Development

10.20.2005

The need for Data-driven Software Development

St Mary Axe, February 2015

Page 2: Data Driven Software Development

10.20.2005

Software is Eating the World

Page 3: Data Driven Software Development

3

Tech is Fragmenting

Page 4: Data Driven Software Development

4

The CIO is the Last To Know

Page 5: Data Driven Software Development

5

Language Rankings

Page 6: Data Driven Software Development

6

Forking as a Good

Page 7: Data Driven Software Development

7

Social Coding as Public Utility

Page 8: Data Driven Software Development

8

Agile and Continuous Deployment

Page 9: Data Driven Software Development

9

“The lumber industry sells what used to be waste — sawdust, chips, and shredded wood — for a pretty profit. Today you’ll find these by-products in synthetic fireplace logs, concrete, mulch, particle board, fuel, livestock and pet bedding, winter road traction, weed killing and more.”

Jason Fried, 37signals

Page 10: Data Driven Software Development

10

“In contrast to most traditional survey methods, search data are collected as a by-product of normal activity”

- the Bank of England

Page 11: Data Driven Software Development

11

Borrow from Web Companies

Page 12: Data Driven Software Development

12

Data, Teams and Competitive Advantage

Page 13: Data Driven Software Development

13

Wrapping Up

The business is demanding that you deliver more products to market faster.

response: Agile, DevOps, and Continuous Integration/Deployment

The War for Talent hasn't even started yet - use data for resource allocation and human resources.

Software development is an art but also science – data is a bridge.

Let developers do their jobs and make infrastructure choices, but measure the results.

Watch, don’t ask.

Agile wins, precisely because it is data-driven. Developers thrive on good data.

Break big problems and projects into smaller pieces run by smaller, more responsible, teams.

(At Netflix) the Developer is responsible if they break the build.

With large, legacy code bases, data allows you to find the best likely fix(er).

Use data to reduce organisational disagreements.

Open source is central to good software development engineering practice

Higher quality apps lower support costs.