• Save

Loading…

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Like this presentation? Why not share!

Like this? Share it with your network

Share

Open Source in Big Business (OSDC 2010)

  • 1,013 views
Uploaded on

My OSDC 2010 presentation regarding my personal experience in working with Open Source in big corporations.

My OSDC 2010 presentation regarding my personal experience in working with Open Source in big corporations.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
1,013
On Slideshare
1,005
From Embeds
8
Number of Embeds
7

Actions

Shares
Downloads
0
Comments
0
Likes
0

Embeds 8

http://www.slideshare.net 2
http://ganocafeobrhayan.blogspot.com 1
http://atwork.settlement.org 1
http://www.koleksisoalan.blogspot.com 1
http://dattatecblog.com 1
http://www.informatik.uni-leipzig.de 1
https://www.linkedin.com 1

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • * Work with a bunch of big-name clients * Shine is NOT an Open Source company. * Much of what I say today reflects Shine values … * Also contributed to CPython et al.
  • Our experience: clients “know” what they want. Exception to the rule: requests for tender, sometimes Where they don't know what they want, often open to suggestion on the provision we'll support it. Of course, if the solution is open source, we can support it. We rely on long-term business relationships with our clients.
  • Consultants provide expert advice. Clients pay because they want your opinion. They believe your opinion will provide value. You thus have an obligation to deliver this value.
  • Strive to deliver value over all else. “Value” -> security, efficiency, productivity, money. Unsure what your client wants? Ask! Do not recommend a second-rate OS solution: * Your client might lose money. * You could lose a client. * Tarnish the image of OS Consider all options. Provide the client with multiple options.
  • Avoid vendor lock-in. Reduce initial outlay. Proprietary solutions bad for consultants too: * Support somebody else's solution?
  • Avoid vendor lock-in. Reduce initial outlay. Proprietary solutions bad for consultants too: * Support somebody else's solution?
  • Our experience: clients “know” what they want. Exception to the rule: requests for tender, sometimes Where they don't know what they want, often open to suggestion on the provision we'll support it. Of course, if the solution is open source, we can support it. We rely on long-term business relationships with our clients.
  • “ Oh, open source has a higher TCO” Completely irrelevant, even for averages Solutions deserve independent scrutiny. Advocating either was is doing clients a disservice.

Transcript

  • 1. Open Source in Big Business: A Consulting Perspective Tom Lee Shine Technologies
  • 2. Overview
    • Who am I?
    • 3. Shine's Clients
    • 4. What is a Consultant?
    • 5. Disregard Dogmatism, Acquire Value
    • 6. Why Open Source for Your Clients?
    • 7. On Total Cost of Ownership
    • 8. Selling Big Business on Open Source
    • 9. Convincing Big Business to “Give Back”
  • 10. Who am I?
    • Consultant for Shine Technologies
      • Software consultancy with offices in Melbourne and Brisbane
      • 11. http://www.shinetech.com
    • Open source contributor
      • (C)Python, Node, Rails, ...
  • 12. Shine's Clients
  • 17. What is a Consultant? “ A consultant is a professional who provides professional or expert advice in a particular area of expertise.” – Wikipedia People pay consultants for our opinions . They pay consultants because they believe our advice will translate to tangible value.
  • 18. Disregard Dogmatism, Acquire Value Your primary consideration as a consultant should be to deliver optimum value to your client . The best solution for your client may not be open source.
  • 19. Why Open Source for Your Clients? Proprietary solutions often limit your client's options for support. Falling-out with a proprietary vendor will leave a client facing difficult, expensive decisions . Initial outlay for open source is typically less than for proprietary solutions. Benefit from features and bug-fixes delivered for free by the community.
  • 20. Why Open Source for Your Clients? (cont.) Only the license and (lack of) access to the source code prevents your consultancy from supporting proprietary solutions. Is a vendor of proprietary software really more technically capable than anybody else with access to the source?
  • 21. Selling Big Business on Open Source Most of the time they ask, or they're already using it! Usually specific, proven Open Source solutions that are tried and tested . Prove that you can support these solutions.
  • 22. Selling Big Business on Open Source (cont.) Big business is generally conservative: Opportunities on the bleeding-edge are rare. Prefer good business relationships to proprietary lock-in.
  • 23. Convincing Big Business to “Give Back” Your clients may be a little nervous about you contributing fixes upstream . Convince them of the benefits of “giving back”. Go ahead and create useful open source for your clients. e.g. jazz – node template engine http://github.com/shinetech/jazz (In active use by the CitySearch team at Sensis)
  • 24. Convincing Big Business to “Give Back” (cont.) Convincing your clients to give back benefits everyone. The Open Source project continues to improve . Simplifies the upgrade path for your client. Gets your consultancy's name “ out there ”.
  • 25. On Total Cost of Ownership Lots of talk regarding Open Source vs. proprietary on TCO, but it's pointless to generalize. For any given problem, the difference between the TCO of open source and proprietary solutions can and will differ due to any number of factors. Do your homework!
  • 26. Summary
    • Focus on delivering value to your clients.
    • 27. Be understanding of corporate technological conservatism.
    • 28. This is RL: don't get caught up in dogma.
  • 29. Questions? Tom Lee http://tomlee.co Shine Technologies http://www.shinetech.com [email_address]