• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Drupal for Project Managers, Part 3: Launching
 

Drupal for Project Managers, Part 3: Launching

on

  • 801 views

 

Statistics

Views

Total Views
801
Views on SlideShare
784
Embed Views
17

Actions

Likes
3
Downloads
0
Comments
0

3 Embeds 17

http://www.acquia.com 12
http://acquia.talentlms.com 4
http://newsblur.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Drupal for Project Managers, Part 3: Launching Drupal for Project Managers, Part 3: Launching Presentation Transcript

    • Drupal for ProjectManagers - Part 3Launch!acquia.com1Wednesday, June 12, 2013
    • HELLO!Heather JamesAmye Scavarda@learningdrupal@amye2Wednesday, June 12, 2013
    • ?You and the project lifecycleDeploymentand LaunchDesignDiscoveryContentstagingInformationArchitectureDevelopment/ImplementationQualityAssuranceMaintenanceFrom “Planning and Managing a Drupal Project” by Amye Scavarda in Definitive Guide to DrupalWhat definessuccessWhat risks in eachphase?How can you affectall phases?3Wednesday, June 12, 2013
    • This is based on...• Case studies and real-life examples• Shared expertise and knowledge• Growing group of project managers in Drupal• DrupalCon and DrupalCamp presentations• Learning from your peers!4Wednesday, June 12, 2013
    • Introducing Amye5Wednesday, June 12, 2013
    • DEPLOYMENT /LAUNCH6Wednesday, June 12, 2013
    • Planning for launch7Wednesday, June 12, 2013
    • Launch meeting• Discuss contingencies for going live• Who• Project manager• Developers• Client stakeholder8Wednesday, June 12, 2013
    • What do you thinkare the risksin the deployment orlaunch phase?Mitigate the risks9Wednesday, June 12, 2013
    • Testing before launch• Testing• Functional Testing.• Mobile Testing• Testing with Drupal Modules: SimpleTest• Migration of the system to the productionservers. (mitigate with same environment)• Detailed launch plan (cutover and rollback)10Wednesday, June 12, 2013
    • Planning for traffic• Load testing and goals• Users• Test patterns - ordering? video? sharing?• What can your site handle?11Wednesday, June 12, 2013
    • Neccessary planningCutoverIdentify timeframe.Document steps, assignstakeholders and tasks.Validate - test once ortwice to documentissues and timings.RollbackClear tasks in case ofrollbackTest the rollback planWho is responsible foreach step?12Wednesday, June 12, 2013
    • Deployment13Wednesday, June 12, 2013
    • Why is this risky?CodePHP, JS, CSSDataFilesCodePHP, JS, CSSDataFilesLocal ProductionCopy downlatest data?FTP uplatest code?Make livechanges inconfiguration14Wednesday, June 12, 2013
    • The deployment problemCodePHP, JS, CSSDataFilesCodePHP, JS, CSSDataFilesLocal Development Staging Production15Wednesday, June 12, 2013
    • Code OK (version control)Local Development Staging ProductionAddedchange to athemeFilesData changedCode changedPHP, JS, CSSCodePHP, JS, CSSFilesAdded a newViewCodePHP, JS, CSSDataFiles16Wednesday, June 12, 2013
    • Data conflictsLocal Development Staging ProductionFilesData changedCode changedPHP, JS, CSSFilesNew useradded anarticle!CodePHP, JS, CSSDataFilesCodePHP, JS, CSS17Wednesday, June 12, 2013
    • Configuration to codeLocal Development Staging ProductionFilesData changedCode changedPHP, JS, CSSFilesExportconfigurationto codeCodePHP, JS, CSSDataFilesCodePHP, JS, CSSCodePHP, JS, CSS18Wednesday, June 12, 2013
    • Export to code?• Think “Features” such as an image gallery.• Contains: Config, content, code, files.• What can be exported:• Views, content types, settings, etc.• Eliminates hazards of rebuilding onproduction sites.• Does not: Manage data export.• Modules: Features, Strongarm, custom.19Wednesday, June 12, 2013
    • Staging for testingLocal Development Staging ProductionFilesData changedCode changedPHP, JS, CSSCodePHP, JS, CSSFiles FilesCodePHP, JS, CSSDataFilesCodePHP, JS, CSSFilesData DataRun scripts fromcode that updatethe database withnew configuration.20Wednesday, June 12, 2013
    • Environments neededDevelopmentDeveloperscollaborating andtesting.Code should beversion controlled.Multiple devenvironments(local and online).Staging/QATest updates fromdevelopment.Should be exactsame environmentas production.Sync content andfiles fromproduction.Production/LiveLive, stable versionof site.Tested.This is where userslogin and addcontent (usually).21Wednesday, June 12, 2013
    • Consider• Why is important that QA and Productionmimic each other?Screenshot of Acquiaʼs hosting UI.22Wednesday, June 12, 2013
    • Acquia Insight testing23Wednesday, June 12, 2013
    • Hosting24Wednesday, June 12, 2013
    • The ***P stack• Drupal is flexible, but most tested on...• Linux: But works on other OSs• Apache: But works on other servers• MySQL: But works on other databases.• PHP: This is a requirement.http://drupal.org/requirements25Wednesday, June 12, 2013
    • Hosting considerationsPerformanceHow fast can thissoftware respond?How long does ittake to process arequest and outputa page to thebrowser?ScalabilityHow fast can thissystem respond?How manyrequests can thesystem handle atonce?ImprovementsOptimize databasequeries.Cache (save aprocessed copy) foranonymous visitors.Use a CDN (contentdelivery network) forfiles or media.26Wednesday, June 12, 2013
    • Cloud is scalable27Wednesday, June 12, 2013
    • Multisite in Drupal28Wednesday, June 12, 2013
    • Hosting a single siteContributedmoduleContributedmoduleContributedthemesCoreDBWeb SiteDrupal sitehttp://www.acquia.com/resources/collateral/drupal-powered-enterprise29Wednesday, June 12, 2013
    • MultisiteContributedmoduleContributedmoduleContributedthemesCoreDBWebexperienceWebexperienceWebexperienceDrupal sitehttp://www.acquia.com/resources/collateral/drupal-powered-enterprise30Wednesday, June 12, 2013
    • Three models• Multi-tenant: One database, one Drupal installation.• Hybrid: Multiple databases, one Drupal installation.• Multi-instance: Multiple databases, multiple Drupalinstallations.http://www.acquia.com/resources/collateral/drupal-powered-enterprise31Wednesday, June 12, 2013
    • • Increases complexity with multisiteconfigurationMultisite managementScreenshot of Acquiaʼs hosting UI.32Wednesday, June 12, 2013
    • Acquiaʼs hosting33Wednesday, June 12, 2013
    • Easy win• Option 1:• Buy the right hardware, install loadbalancers, setup MySQL servers in master-slave mode, setup static file servers, setup webservers, get PHP working with an opcode cache, tie ina distributed memory object caching system like memcached,integrate with a content delivery network, watch security advisoriesfor every component in your system and configure and tune the hell out of everything.• Option 2:• Choose optimized Drupal-tuned hosting.34Wednesday, June 12, 2013
    • Acquia Network• Operate sites moreeffectively– Drupal site monitoring– SEO Grader– In-the-wild software testing– Self-service load testing– Performance monitoring• Extend site capabilitiesefficiently– Faceted search andnavigation– Content recommendations– Automated spam protection– Mobile interface design– A/B, multivariate testing35Wednesday, June 12, 2013
    • Application management• Checks 80+ Drupalspecific settings• On-demand scoring• Personalized real-time notifications• Best practicerecommendations36Wednesday, June 12, 2013
    • Training & Adoption37Wednesday, June 12, 2013
    • Build in training• Demo functionality to stakeholders• Record demos at key milestone meetings.• Get content editors involved at the earlieststages so they learn incrementally.• Testing and learning at the same time.38Wednesday, June 12, 2013
    • Documentation• Create a central repository for projectdocumentation, gather as you go along.• Improve inline documentation.• Content entry screen “help text”.39Wednesday, June 12, 2013
    • Drupal for Content editors!• June 26th - check the webinar schedule• https://acquia.com/resources/webinars• How Drupal works• Content administration• Typical customizations• Key terminology40Wednesday, June 12, 2013
    • ANY QUESTIONS?For those watching therecording, ask questions here:http://bit.ly/d4pm341Wednesday, June 12, 2013
    • Useful resources• Launch checklists• http://www.zivtech.com/blog/impending-drupal-site-launch-use-list• http://www.microserveltd.co.uk/blogs/drupal-development/going-live-drupal-checklist• More resources will be posted atbit.ly/d4pm342Wednesday, June 12, 2013
    • Contact us!acquia.com/training/contact43Wednesday, June 12, 2013
    • Sign up for next sessions!44Wednesday, June 12, 2013