Professional Drupal Development The Economis


Published on

The Economist has embraced Drupal. This publication gave brief details of the agile project management, the approach to keeping and hiring talent and how in general we approached the project.

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Competitors where widespread, Escenic, Nstein, Joomla e.t..c Narrowed down to Escenic, Drupal. Chose Drupal because of openness, belief that the social aspects of the product were better. Community innovation is key as everybody goes their own way with shared products.
  • TDD Scrum is really needy when it comes to planning and accounting Adopted TDD as a way to improve ability to change products, not build them. Drupal isn’t very good at letting you check the whole project into source control because it stores a lot of config in the database. We launched EC2 cloud servers with an approach that says everything must be done in code to be promoted. Got install profile API module to help with upgrades and changes which run within HUDSON, Simpletest and Drush. SimpleTest SimpleTest is a Drupal module and part of core Drupal 7. We write SimpleTests and we are aiming for a high percentage code coverage. Selenium Record tests in Firefox, play them back as part of Simpletest Jmeter Not much to say, we keep jmeter jmx files with each module and then Hudson knows how to run them,
  • Basic scrum set up The project breakdown UX ahead doing work we anticipate we will need. For instance Sprint 1 UX designed the comment history page, Sprint 2 the devs went and built that design HAVE to go live. That’s just’s way but it makes sure you focus on thin vertical slices of functionality. Clean the branch rather than track your code and merge out
  • People ahead of contracts and deadlines. Philosophy of public work demoing successes rather than sales guys. Gives higher chance of success, along with Scrum which will allow us to see how consultants do in 3 weeks chunks. We get commitments in hours rather than products. Spot failures early Hire from the community 20% time to grow the product.
  • Be nice and repeat questions asked!
  • Professional Drupal Development The Economis

    1. 1. Professional Drupal Development How The Economist is building a Drupal website Stewart Robinson @stewsnooze 30th June 2009
    2. 2. Why we moved to Drupal <ul><ul><li>Being a part of a Community improves your quality. </li></ul></ul><ul><ul><li>Unlock innovation at a fraction of the cost. </li></ul></ul><ul><ul><li>Old site is publishing based rather than socially based. </li></ul></ul>
    3. 3. Environment & Practices <ul><ul><li>Test Driven Development (TDD) </li></ul></ul><ul><ul><li>Manage TDD with Hudson CI on Amazon EC2. </li></ul></ul><ul><ul><li>Unit test with Simpletest. </li></ul></ul><ul><ul><li>Browser test with Selenium. </li></ul></ul><ul><ul><li>Load test with JMeter. </li></ul></ul>
    4. 4. Scrum <ul><ul><li>7 with +2 or -2 on a team. </li></ul></ul><ul><ul><li>3 week sprints 3 teams. </li></ul></ul><ul><ul><li>UX work in current ahead of next sprints. </li></ul></ul><ul><ul><li>Go live at the end of the sprint. </li></ul></ul><ul><ul><li>Development branch has to be clean. </li></ul></ul>
    5. 5. Operations <ul><ul><li>Use swatch to collate errors. </li></ul></ul><ul><ul><li>Use ELOG to make production changes. </li></ul></ul><ul><ul><li>Acquia support. </li></ul></ul><ul><ul><li>Managed service hosting. </li></ul></ul><ul><ul><li>ITIL </li></ul></ul><ul><ul><ul><li>Problem management. </li></ul></ul></ul><ul><ul><ul><li>Incident management. </li></ul></ul></ul>
    6. 6. Team structure and philosophy <ul><ul><li>Talent focussed. </li></ul></ul><ul><ul><li>ColdFusion developers cross trained into PHP/Drupal. </li></ul></ul><ul><ul><li>Consultants hired, only from presenting at DrupalCon or from following work at </li></ul></ul><ul><ul><li>New Drupal developers hired. </li></ul></ul>
    7. 7. Questions <ul><ul><li>Why we moved to Drupal </li></ul></ul><ul><ul><li>Environment & Practices </li></ul></ul><ul><ul><li>Scrum </li></ul></ul><ul><ul><li>Operations </li></ul></ul><ul><ul><li>Team structure and philosophy </li></ul></ul>