In this session we'll discuss how agile analysis and project management processes can be applied to Drupal implementation. We'll discuss the setting of expectations for stakeholders when planning and executing a Drupal project, and how to avoid the typical pitfalls. You'll also learn how a multi-disciplined project team can smooth your project execution, and increase your chance for overall success.

1. [MM.DD..YY] [PRESENTER] Planning and Executing a Successful Drupal Implementation 2010 PLANNING AND IMPLEMENTING A SUCCESSFUL DRUPAL WEBSITE Brent Bice [email_address] Twitter: #ocdplanning

3. Complex site structures SEO Video Email PPC Directed Content CRM Automated Marketing Systems Content Delivery Networks Digital Asset Management Online Media Kits Media Room Blog Wiki Forum PDFs Workflow Multiple Languages User Permissions

4. 2009 Project Success was Rare Average cost overrun: 45% Time overrun: 63% Functionality delivered on average: 67% 32% 44% 24% Chaos Report by The Standish Group: Application Delivery

8. How we manage our projects

9. From Waterfall to Agile Project Lifecycle 2 week cycles

10. Scrum 24 hours 2-4 weeks

11. Strategy and Planning

15. User Role Modeling potential customer 5 job seeker content editor

16. User Stories 5 As a content editor, I can add, edit and remove content.

17. User Stories 5 As a job seeker, I can search for available positions close to where I live.

18. User Stories 5 As a potential customer, I can view a list of services on the website and learn more about them.

19. User Stories create the product backlog 24 hours 2-4 weeks User Stories Prioritized by importance (MSCW)

21. Tasks to complete story 5 As a potential customer, I can view a list of services on the website and learn more about them. Create “services” content type with title, body, image upload. Create a list view of services that displays title, teaser, image, and link to product page. Configure user permissions to allow unauthenticated users to view services content. We assign points to Stories We assign hours to Tasks

22. User Stories create the product backlog 24 hours 2-4 weeks User Stories and associated Tasks are estimated by the entire team and added to the Sprint Backlog

23. Development and Testing Site Building and Verification

24. Production environment setup: SVN Development Int. testing Content Client testing

25. Daily Scrum Meeting Stories | Tasks | Impeded | In Progress | To Verify | Done

27. User Stories create the product backlog 24 hours 2-4 weeks Goal of sprint is to provide client with a potentially releasable feature. We review feature with client, gather feedback and make decision based on that feedback.

28. Creative Creative Briefs to Concepts

34. Brent Bice [email_address] Twitter.com/brentbice Thank You!

35. Experience Counts

36. Content Management Framework Standards Compliant Accessible Modular Stable Customizable Open-Source Facts: Tens of thousands of developers are involved in developing, testing, debugging and maintaining the framework and modules. Drupal falls under GPL licensing meaning that everyone/anyone can use code and contribute freely. There are over 4,000 contributed modules. Tektronix developers are already learning Drupal.

37. Who’s Using Drupal For Knowledge Management

38. What Businesses Are Saying Rackspace "The new site was designed to give our customers immediate access to the support documentation they need. We took our existing support information, re-wrote it, organized it into categories and subcategories, and built a new search system so you can find your answers in a hurry ..." “ We considered using Clearspace to be our CMS of choice but by early 2008 the absence of certain features and other issues made us consider other options. We had a front-end developer working on adding more blogs to blogs.zappos.com and a new hire, Geoff, who we assigned to about.zappos.com . The idea was to let each work on their projects and occasionally switch places and work on the other CMS so they could compare and contrast the features and development time. Drupal ended up being superior in terms of templating and development as well as adding new features and ease of use for the end user .” Zappos Associated Press - Obama Administration Source “ The White House has ditched the proprietary content management system that had been in place since the days of the Bush Administration in favor of the latest version of the open-source Drupal software …”