Drupal for Project Managers, Part 4: Maintenance
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
1,005
On Slideshare
977
From Embeds
28
Number of Embeds
4

Actions

Shares
Downloads
17
Comments
0
Likes
2

Embeds 28

http://www.acquia.com 17
http://newsblur.com 5
http://acquia.talentlms.com 5
http://cloud.feedly.com 1

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Drupal for ProjectManagers - Part 4Maintenanceacquia.com1Wednesday, June 19, 2013
  • 2. HELLO!Heather JamesJenn Sramek@learningdrupal@Ideaseed2Wednesday, June 19, 2013
  • 3. ?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 19, 2013
  • 4. 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 19, 2013
  • 5. Introducing Jenn5Wednesday, June 19, 2013
  • 6. CLOSING ANDMAINTENANCEPHASE6Wednesday, June 19, 2013
  • 7. How to have asuccessful projectclosing meeting?7Wednesday, June 19, 2013
  • 8. What are therisks in theclosing phase?Mitigate the risks8Wednesday, June 19, 2013
  • 9. Goals for closing• Establish early on:• What will happen at hand-off.• Where is documentation going to bestored?• What information needs to be documentedand delivered?• Gather your documentation and deliver it.9Wednesday, June 19, 2013
  • 10. Transition10Wednesday, June 19, 2013
  • 11. Hand-off• What gets delivered to client in hand-off?• Who will be taking over?11Wednesday, June 19, 2013
  • 12. Done during development• Code commenting (done as an on-going partof dev process)• Documenting assumptions - why decisionswere made• Documentation of features12Wednesday, June 19, 2013
  • 13. What ismaintenance?13Wednesday, June 19, 2013
  • 14. Maintenance is important“The moment it ceases towork due to maintenanceissue, users go elsewhere.”- Jenn!14Wednesday, June 19, 2013
  • 15. What is maintenance?• Simplification• Maintenance planning• Upgrading - upgrade paths• Compatibility• Ongoing complications• Getting users involved15Wednesday, June 19, 2013
  • 16. What to expect• Clients will want to squeeze in last minutefeatures.• There will be a tendency to ignore key tasksin maintenance.• New “features” and “needs” will arise asusers first interact with the system.16Wednesday, June 19, 2013
  • 17. Required maintenance• Minimal required maintenance.• Updating installed modules and themes.• Backing up code and data.• User, spam and content moderation.• Analytics• Advertising• User training17Wednesday, June 19, 2013
  • 18. Updating v upgrading?• Update: Is a minor change, 7.12 > 7.15• Upgrade: A major version 6.x > 7.x• Main principle: “We can break peoples code,but not peoples data.”• Drupal is not backward compatible. Modulesbuilt for 7 will not work on 6.18Wednesday, June 19, 2013
  • 19. Upgrading• Research first!19Wednesday, June 19, 2013
  • 20. Ways to say no• Build in parallel tracks in development.• Client needs to know that it takes away frommaintenance.20Wednesday, June 19, 2013
  • 21. Plan to celebrate andshare21Wednesday, June 19, 2013
  • 22. Contribute and celebrate• Blog, tweet, share on LinkedIn or Facebook.• Share a case study, post on a showcase.• Propose DrupalCamp session with yourclient.22Wednesday, June 19, 2013
  • 23. 23Wednesday, June 19, 2013
  • 24. 24Wednesday, June 19, 2013
  • 25. /drupalgivehttps://drupal.org/drupalgive25Wednesday, June 19, 2013
  • 26. Support contracts?26Wednesday, June 19, 2013
  • 27. Not factored in...“People think ‘I built it, anddidn’t change anything. Howcould bugs happen?’ ...The degredation of codedoesn’t compute”- Jenn27Wednesday, June 19, 2013
  • 28. Who?• Stepping out of the project?• Who is doing what and when?• Transitioning an internal team?• External?28Wednesday, June 19, 2013
  • 29. Support contracts?• Warranty: provide a standard warranty periodof 90 days after delivery of the project.• Offer purchase of a support contract after.• Clients need to understand what ismaintanence is, what new development is.• What business goals indicate on-goingdevelopment required?• “Standard” is that people ignore this issue.29Wednesday, June 19, 2013
  • 30. Examples• X amount of hours per month• Y length• Clarify expectation• Example:5 hours of support in 30 day launch period• Purchase additional hours?30Wednesday, June 19, 2013
  • 31. Security31Wednesday, June 19, 2013
  • 32. Security• Many problems are introduced through:• Poor configuration of user permissions.• Input text filter configuration.• The theme layer.• Custom code.• Also contributed modules and core.32Wednesday, June 19, 2013
  • 33. Keeping Drupal Secure• https://www.acquia.com/blog/keeping-drupal-secureDrupal securityAdvisoriesdrupal.org/security All security announcements are posted to an email listas well. Once logged in, go to your and subscribe to thesecurity newsletter on the Edit » My newsletters tab.Hacked! module drupal.org/project/hacked This module scans your core and contributed modulesand determines if the code has been changed.Drupal Scout drupalscout.com/ Drupal Scouts Knowledgebase has a number of usefularticles and checklists about security.Acquia Insight j.mp/insightdemo This service analyzes your Drupal site against a seriesof standards and best practices, including Security.Insight provides some clear indicators around sitehealth and best practicesSecurity modules j.mp/securitymodules There are a number of security modules to improvesecurity and assist in analysis and monitoring of yoursite.33Wednesday, June 19, 2013
  • 34. 34Wednesday, June 19, 2013
  • 35. 35Wednesday, June 19, 2013
  • 36. ANY QUESTIONS?For those watching therecording, ask questions here:bit.ly/d4pm436Wednesday, June 19, 2013
  • 37. Sign up for next session!37Wednesday, June 19, 2013
  • 38. Contact us!acquia.com/training/contact38Wednesday, June 19, 2013