enterprise drupal

Enterprise Drupal

Balázs Dianiska - Acquia

[email protected]://twitter.com/thesnufkin

Saturday, 17 August 13

mailto:[email protected]

mailto:[email protected]

http://twitter.com/thesnufkin

http://twitter.com/thesnufkin

About me

• Technical Consultant EMEA - Acquia

• Architecture design, audits (security, performance), trainings

• Fortune 500 companies, governments, non-profits, higher ed


About this talk

• This is not a tech talk

• The power of “product”

• Processes

• How Drupal fits into this mess


What the hell is “enterprise”

• Large clients (NBC, Warner Music, Disney)

• They love processes


Example products?

• Product on your desktop

• Windows

• Lotus Notes (lol)

• Word, Pages, Keynote

• Products on the web

• Salesforce

• Gmail


How does a big company see at Drupal?

• Developers playground, lack of enterprisey features

• What do they see?

• LEGO vs product

• Distributions

• Drupal as a brand

• Internal initiative is important


Drupal as a product

• Drupal Commerce Kickstart, Drupal Commons, Scald Galaxy

• Drupal for Web Experience Management

• “Just works”


Processes

• Failure happens. Get over it.

• Testing (unit test, functional test)

• Deployment

• Development, Quality Assurance (Staging), Production

• Version tracking

• Sustainable development, project transferable


What the hell is “WEM”?

• Buzzword

• Web Experience Manager

• Analytics

• Email marketing

• Spam filtering

• Media/document management

• And by the way its also a CMS


The ingredients

• Content

• Structure/architecture

• Media

• Deployment


Content workflow

• Company content workflow implemented in Drupal

• Workbench, workflow modules

• Simpler is better


Digital asset management

• Reuse of media across the site(s)

• Images, videos

• Text

• Even across different sites


Configuration management

• UGC - User Generated Content

• Content

• Files

• Configuration

• Views, Display Suite

• Variables

• Drupal 8


Multivariate testing

• Which version gives better sales

• Not entirely solved in Drupal

• There are modules (Views, Panels, Context) but they can only do so much


Interacting with client

• Selling through a demo

• Build trust and relationships with the customer

• Help them with what they need, not what they want

• Strong brand, marketing

• Documented processes of development

• Transfer of knowledge

• Human failover (shit happens, the question is how you clean it up)


So how to enter this market?

• Partner with us (Acquia, Wunderkraut, CapGemini etc)

• Partner with design agencies

• Understand the risks, give value to the client in the long run and make that clear

• Big company - big bureaucracy

• Sales, stakeholder, dev leads, project managers, developers


Basic structure of an enterprise project

• “What do you really want?” - Discovery Workshop

• “Plan the build” - Architecture Workshop

• “Build it” - technical lead, architecture lead

• “Will it work” - Testing, launch validation

• “Keep it working” - Maintenance, support


External audits

• Reviewing the application for security, performance

• Third party perspective gives validation


Why do companies like Drupal?

• Low entry costs

• They are (more) in charge

• Solid architecture

• Off the shelf functionality for free

• There are companies who can service large clients (SaaS, PaaS, LSD)


The shift to open source

• Unforeseen consequences: building in house, inexperienced dev shops

• Organizations become product owners

• “Since we can do everything, we want everything!”

• The cost of “free”


Drupal 8 is coming

• Open source is doing well

• Configuration management

• Better architecture, easier to work with (IDEs)

• Services

• Distributions will mature


Thanks you!

Balázs Dianiska

[email protected]@thesnufkindrupal.org/user/58645


enterprise drupal

Technology

dianiskaacquia

saturday

drupal

testing

partner

work

companies

hell