Software 2.0 - Transformation of Software Services

Software 2.0 - Transformation of Software Services

• 1.
  Software 2.0 -Transformation of Software Services by Abhishek Rungta Founder / CEO Indus Net Technologies
• 2.
  Why do weneed transformation? “ On an average, $8 out of every $10 spent in IT is “dead money” – not contributing directly” - Gartner Research Source: Richard Heeks. 2003. “ Most e-Government-for-Development Projects Fail: How Can Risks be Reduced ?”. e-Government initiatives in Developing Countries Partial Failures 50% Total Failures 35% Successes 15%
• 3.
  Nobody likes tofail. Then.. Source: http://www.arraspeople.co.uk – 2010 Project Management Benchmark Report
• 4.
  Why projects fail?Lack of Commitment Communication Resources from – stake holders, users and / or vendors!
• 5.
  The Software /Web 2.0 fix Cloud computing / Software as a Service (SaaS) The ‘hard’ or ‘technology’ fix using the network Provides flexibility / makes iterative development feasible Social communities The ‘soft’ fix Engages people / empowers them Open alternate channel of communication
• 6.
  So what isSoftware 2.0? Platform independent centralized deployment of application, with open standard clients i.e. browsers Anytime, Anywhere access in the connected world Totally modular, extensible architecture based on open standards, giving high level of flexibility in terms of development and deployment, hence making iterative development feasible Pay-as-you go system ensuring higher success rate of software deployment, since the onus of success is now on to the vendor
• 7.
  Software 2.0 =IaaS, PaaS and SaaS Don’t forget: Private Cloud!
• 8.
  Centralized control Efficientdeployment - It is centrally deployed (generally using single code base) and globally used. Therefore it can be easily and quickly deployed. Quick updates – Upgrades, bug fixes and patches are centrally managed and rapidly deployed without any additional cost, making iterative development feasible. Shared infrastructure across applications and departments help in managing peak usage well
• 9.
  Lower Infrastructure /Manpower Cost Low infrastructure cost – Only worry about the centralized infrastructure, it’s upgrade, upkeep, backup, disaster planning, data security, etc Low manpower cost – Need to higher fewer experts in centralized locations to manage and support the application, hence reducing the manpower cost greatly.
• 10.
  Open Standards /Platforms Browsers are available for all platforms and devices (built as per open framework) Windows, Unix, Linux, MacOS, iPhoneOS, Android, Symbian and .. Devices to come in future! Build for one platform and access / use on all platforms, giving ultimate flexibility to users Built on open standards allowing easy data portability using XML
• 11.
  Pay As YouGo Licensing can be flexible Pay for what you use! Depends upon the level of usage of IaaS, PaaS and the SaaS contract with your vendor (Public cloud to private cloud) Software can be purchased as a service, therefore reduce the up-front cost Onus of the success of the system is on the vendor. Vendor not only has to deliver properly, but has to keep the system up to date at a regular basis. The real “service” steps in!
• 12.
  Social Software Transparent,Always connected Engaging users of the system to get real input Real needs, Real feedback They think it is “their” system! Internal / External stakeholders are served Crowd sourcing and harnessing collective intelligence
• 13.
  Thank You [email_address]Blog: www.abhishekrungta.com Twitter: @abhishekrungta Facebook: www.facebook.com/abhishekrungta Mobile: 098311 51614