This document compares a license-based software delivery model versus a SaaS model. It discusses challenges large enterprises face with scattered infrastructure and tools. It then introduces Deveo as a centralized platform that can be installed behind a corporate firewall, offering unified practices and tools to allow developers to focus on high-value tasks. Key considerations for on-premises versus SaaS implementations include customization options, support requirements, upgrade cycles, costs, security, and integrations.

1. Last modified: 20. Mar. 2015Confidential
License based software delivery vs.
Saas model
Ilmari Kontulainen
@kontulai

2. About Ilmari Kontulainen

3. About Ilmari Kontulainen
10 years in IT industry
Different roles
Business & Technology
Sports, reading, coaching

4. About Deveo

5. Challenges in large enterprises
Lack of unified tools or methodologies
Infrastructure is scattered across the organization
Time is wasted to tasks that don’t bring business value
Weak or nonexistent visibility upward

6. Problem field

7. traditional permission workflow
TEAM MEMBER
PROJECT MANAGER
IT ORGANIZATION
REQUESTACCESS
CONFIRM
ENSURE
GRANTACCESS
= 1 week

8. Solution
Centralized platform behind corporate firewall
Offering unified practices and tools
Allows developers to focus on tasks that really matter for the
business
Control and visibility throughout whole software development
lifecycle

9. Solution

10. VERSION CONTROL
TASK MANAGEMENT
DOCUMENTATION
COLLABORATION
ACCESS CONTROL
SCALABILITY
FILE MANAGEMENT
EXTENSIBILITY
Deveo features

11. On-premises vs. Saas

12. On-premises vs. Saas
Implementation
Customization
Support & maintenance
Upgrade cycles
Cost
Security
Integrations
Scalability

13. Learnings

14. How we do things at Deveo
Roadmap available for next year
Releases once per month
Plan only next release in detail
Take three kinds of tasks: Customer requests, Bug fixes and
Internal improvement tasks

15. Learnings
Aim to be predictable, not fast.
Don’t aim for external continuous delivery.
Replace A/B testing with betas.
Know your key customers cadence.
Keep close to customers end users.

16. Questions?
Follow me in twitter:
@kontulai