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.
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 E.com’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.