“...the handbook for developing tomorrow's software as a service!” Author: Jeff Sussna

1. IT as Conversational
Medium - DevOps -
Design Thinking

2. Serving as a medium for
digital conversation is
IT’s new mandate
Large-scale IT projects generally failed for
three reasons:
• The project plan failed to accurately
predict or account for the challenges that
inevitably accompany complicated system
implementations
• The requirements failed to accurately
model users’ real needs
• Over the course of a lengthy
implementation project, users’ needs
changed
IT has traditionally taken an industrial
approach to building and operating systems.
It has concentrated on implementing large-
scale solutions with high upfront costs and
an equally large presumed return on
investment.
Development has proceeded in linear
phases, from initial conception, through
design, development and testing, to
completion.
2

3. DevOps
3

4. Develop - Operate
▪ The software was done when it had been designed, developed,
tested, and burned onto a CD
▪ Installing the software from that CD onto a server, adding
memory or upgrading operating systems in order to be able to run
it, and figuring out what had gone wrong when it failed were all
left to the customer
4

5. Software-as-a-Service (SaaS)
means that the same company
that builds an application also
operates it on their customers’
behalf. Functionality and
operability become inseparable
in customers’ minds 5

6. Developing
Companies pay developers to
write code
Develop - Operate
Operating
operations subspecialties such as
networking, database
management, and security did as
well
6
functionality and operability required navigating multiple layers
of separation. Each layer added time, e€ort, and
misunderstanding.

7. SaaS drives a
similar focus on
speed into
operations. New
applications require
new infrastructure.
As a
Software Service
7