Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

The Horrors of Enterprise software

264 views

Published on

Even in the most agile of organisations, Enterprise software is still the first choice for third parties. However, most are unwieldy, unfit for purpose, and basically everything we don't need as well as a few things we do. Why and how should we change this?

When working on any large project, the need to use 3rd party applications is inevitable. In companies of all shapes and sizes, from two-man startups to internationally recognised names, there's a reason that Enterprise software continues to be a successful, profitable business model. They're seen as the only way forward, and once you're locked into a licence agreement, it's very hard to extricate the business from it and onto a new platform. However, when Red Badger investigate potential 3rd parties, it can be a never-ending stream of options that becomes quite overwhelming. More often than not we will champion the David over the Goliath. We'll fight for open source even when working with huge multi-national organisations. So why do this, instead of signing up for packages tied in a neat little bow?

Published in: Software
  • Be the first to comment

  • Be the first to like this

The Horrors of Enterprise software

  1. 1. The Horrors of Enterprise Software @roisiproven
  2. 2. Roisi Proven Project Manager at Red Badger @roisiproven
  3. 3. Why is Enterprise software used? @roisiproven
  4. 4. Enterprise Software @roisiproven
  5. 5. Why Change? • Enterprise software is too big to be truly agile • Jack of all trades, master of none • If you aren’t in the 1%, you aren’t considered important @roisiproven
  6. 6. Standard ERP • Of those features on the right, only a third are necessary • Some of the necessary features are only available as an “add on purchase” • $1000+ base licence p/m plus $100+ per user licence p/m plus “add ons” @roisiproven
  7. 7. There is another way! @roisiproven
  8. 8. Case Study • Red Badger worked on a website replatforming project for a well-known heritage retailer. • Already started replacement process - Open Source storefront • Needed something to connect this to ERP system • Originally went for a service-based architecture option from 3rd party @roisiproven
  9. 9. Case Study ERP @roisiproven
  10. 10. The Wombat Problem • Wombat - “iPaaS” Integration Platform as a Service • used to connect Open Source storefront to Enterprise ERP system • Parent company bought by First Data @roisiproven
  11. 11. Potential solutions 1. Use the Wombat source code 2. Buy a new solution 3. Build a new solution from scratch @roisiproven
  12. 12. The Solution - Shepherd • Built using high availability services in AWS for reliable scalability • Used deployable infrastructure for complete flexibility • ROI break even point of 10 months @roisiproven
  13. 13. Risks around leaving the Enterprise • Excessive red tape within an organisation • Little companies being swallowed by Enterprise orgs • Nervousness around up front spend • Support concerns @roisiproven
  14. 14. Conclusion • Don’t be afraid to push for custom builds • Keep it simple • A shout out to Enterprise companies @roisiproven
  15. 15. • http://red-badger.com/blog/2016/02/04/the-horrors- of-enterprise-software/ • https://red-badger.com/ideas/five-ways-to-become- more-agile/ @roisiproven PS: We’re Hiring! jobs@red-badger.com
  16. 16. Thanks! @roisiproven

×