�ݺ�ߣ

Editor's Notes

• #2: How many people here already know what Scrum is – a show of hands? We're transforming The Economist online using Scrum on a couple of different levels – we're using Scrum to transform The Economist online (the website) from what it once was to what we need it to be, and we're transforming The Economist online (the company) from what it once was to what we need *it* to be as well
• #7: New issue of the print publication hits news stands/is delivered to subscribers every Friday All articles from print publication are published on/imported into The Economist online every Thursday There's also some "web-only content" - articles posted on The Economist online that do not appear in the print publication; a dozen or so blogs (right now, with more to come); a dozen "channels" where editors "curate" content from The Economist online and from around the Web We have more than 3 million registered users on the site Average time spent on the site per visit is more than 20 minutes Average (commenting) user posts 3.6 comments per month
• #8: Increasing ad revenues is all about increasing page views Increasing print subscriptions through the website is, for me, more complex – that's about the science of customer acquisition, which I won't be touching on in this presentation So, we're trying to increase page views on the site I'm not an expert in content strategy like a lot of you are But I called Kristina Halvorson last week to bounce these next few slides off her and she said my points *may be* "components" of a content strategy
• #9: I mentioned that our average user spends more than 20 minutes on the site per visit (which I think is an incredible amount of time) We've done a bunch of user testing and learned that many of our readers would read more content (and spend more time) on the site if there *was* more content on the site More content would then = more page views, which is what we need to increase our ad revenues We've added more content ourselves via blogs and channel pages although this has (I'm speculating) increased our production costs We want to find ways to increase the volume of content on the site without increasing the cost of producing it
• #10: We want to draw on the intelligence of our editors, our readers and guest journalists We want to give our readers the tools they need to very actively discuss and debate the global agenda If we do this well, we believe our readers will help us increase the volume of content on the site without increasing the cost of producing it *while* increasing page views simply by virtue of the fact that there will be more content
• #11: We also want to involve our editors in the "curation" of content on channel pages, etc. "Curation is the new black" - @deburka So – we know we want to increase page views and we have a strategy for doing so, but what challenges do we face in executing on our strategy?
• #12: The Economist online was initially managed through a custom CMS built with ColdFusion, Oracle and a bunch of bolt on third part applications Functionality was added over the years, but the system became inflexible – we couldn't extend it in the ways that we needed to execute our content strategy Moreover, we were paying interest on the technical debt we'd accrued due to immature engineering practices, which prevented us from focusing fully on the task at hand
• #13: We practiced the waterfall method of software development Requests for new features were bundled together and managed as projects that took months to deliver (and very often did not deliver what our internal customers wanted)
• #14: Read Daniel Pink's most recent book "Drive" There is a large gap between what science knows about human motivation and what business seems to know about human motivation (and that we need to close that gap) High performance teams need autonomy – they need to direct themselves, they want mastery – they want to get better and better at what they do, and they want purpose – they want to feel like their work is about something bigger than themselves Technical debt, outdated development practices and outdated management practices had led to unmotivated teams All of these things were impeding us in our attempts respond to our situation, which were (and are) to increase our online ad revenues and print subscriptions through the site
• #15: Drupal was a fit with our content strategy – to give readers the tools they need to engage in discussion and debate and to give our editors the tools they need to curate content on the site We were excited by the promise of open source – the potential for zero time-to-market where features are developed by the community We were excited by the strength of Drupal community – we wanted to be part of something bigger than ourselves
• #16: Scrum is a learning system If software development were a sport, Scrum would be the rules – Scrum doesn't tell teams HOW to build software, it simply frames the software development game Scrum works by having small , self-organizing , cross-functional teams work in time-boxed iterations to deliver potentially shippable code based on a commonly-understood definition of DONE "Hey I don't tell you how to tell me what to do, so don't tell me how to do what you tell me to do! I know what I'm doing!"