Professional Documents
Culture Documents
Dave West
Chief Product Officer Tasktop
X Product Manager for the RUP
Author Head First OOAD
Former Forrester Analyst
@DavidJWest | dwest@Tasktop.com
Lots of similar
yet different
points of view
Microsoft approach
HP
dev2Ops.org
But cant we all get along ?
Balance
Breakage
We need to Points What do you
use that app
server ! mean we are
going to
Planning release that ?
Process
People Release
Collaboration Automation
Measurement Virtualization
Flow Architecture
Two different sorts of artifacts
The things that are worked on
Examples include specs, code, binaries, builds,
Asset
deployments, etc..
Treated like an investment, incurs debt, has a life
Tasks /
Software Lifecycle
Management
QM
PPM RM Dev ITSM APM
Security
Operations
Classic Agile
Assets
Assets/
Automation
Build Automation Release Automation
Require
ments
Develop
Test
ment
But Agile has changed that
Water-Scrum-Fall
Traditional
planning and
release
approach Require
ments
Lean Startup
Develop Ideas
Test
ment
Team level
Scrum process
But 30-70% of software projects fail
Ops
Business Silo focus is breaking
Analysts the value stream
Testers
Project
Managers Developers
Tool and Process Silos
Healthcare,
Fortune 50
Two Examples
Defects
Tickets
Disconnected Defects
QM
PPM RM Dev ITSM APM
Security
Linked
Spec Code Build Test Deploy
Automated
Build Automation Release Automation
Summary
To deliver higher value software faster you need to break down the
barriers between operations and development
But focusing on release automation only fixes one problem
Think holistically about Development and operations including
planning, support and release processes
Appreciate both work and assets
And look to automate them