saas in the eyes of an offshore provider
DESCRIPTION
This lecture was given during Software 07 - the larget event for Hi-Tech/ISV companies in Israel. It describes the pros and cons of SaaS - Software As A Service from our perspective. This case study was done on Lighthouse - a SaaS-based PLM we, at Ignite, use to manage offshore software development projectsTRANSCRIPT
1Wednesday, March 28th, 2007
SaaS in the eyes of SaaS in the eyes of the userthe user
Aviram EisenbergAviram EisenbergCEO, IgniteCEO, Ignite
2
PLM/SDM Objectives
Single View of all Software Development project life cycle aspects
Effective onsite-offshore communication Keep in control of project
budget/schedule/metrics Transparent to the customer Highly accessible Support for Agile Development
3
Why SaaS?
Web based – highly accessible No hosting overhead No administration overhead Low cost – standard version is free of charge! Free upgrades Pay as you grow model
4
A Lighthouse in the mist
Dashboard Project/Tasks management Resource management Requirement management Issue tracking Change management Test management Defect management Document management Time management Customized Reporting Module
5
Dashboard
6
Project Management
7
Requirements Management
8
Tests Management
9
Defect Management
10
Time Management
11
Customized Reports
12
Security
Limited control over security measures The corporate data is co-located with our
competitors’ data! Who is viewing the corporate data? On the other hand, it’s only psychological fear
13
Customization
Generic product vs. customized product Change requests that are not popular receive
low priority New features requests
– Integration with version control systems– Bidirectional Links to wiki– Audit trail
Customized work flow
14
Interfaces To External Platforms
Interface to and from MS Project Export R&D metrics to external Data
Warehouse Integration with IDE Integration with version control systems Integration with defect management systems
15
Backup & Recovery
Limited control over backup measures Where are the backup sets? Who is responsible for the recovery?
16
Upgrades
Downtime during upgrades vs. seamless upgrades
Limited control over downtime periods
17
Support
A product oriented company may have difficulties providing effective service– Online support– 24X7 Support– Knowledge base– User Manuals– Training
18
Performance & Usability
The communication is over the WAN Web-based application
– Use of Ajax– Integration with MS Project, Word, Excel
19
Branding
Logo Corporate look & feel Terminology
20
Wednesday, March 28th, 2007
Aviram EisenbergAviram EisenbergCEO, IgniteCEO, [email protected]
The outcome of a cooperation is not by sharing the limited opportunities exist but creating a new abundance where it was not previously showed.
Q&AQ&A