insert date - drupalcon...insert date page 3 | how technical should a drupal pm be? matthew...
TRANSCRIPT
Page 1 | How Technical Should A Drupal PM Be?
Insert Date
Page 2 | How Technical Should A Drupal PM Be?
How Technical Should a Drupal PM Be?
Insert Date
Page 3 | How Technical Should A Drupal PM Be?
Matthew O’BryantDirector of Strategy
Here’s a little about my background in technology:● Started by selling computers at Sears● Worked as a helpdesk Technician at Filene’s● Windows NT 4.0 MCSE● Worked as Network Admin for Mortgage
Originator● Worked 10+ at Web Agency as Project Manager
401-228-7660
72 Clifford Street,
Providence, RI 02903
oomphinc.com
oomph.is/jmobryant
Page 4 | Presentation Title Goes Here
”I think in 1’s and 0’s but I speak in English.
MYSELF
Page 5 | How Technical Should A Drupal PM Be?
Does it even matter?
September 1, 2016
Page 6 | How Technical Should A Drupal PM Be?
Does It Even Matter?
The main role of a Digital Project manager is to:
● Hit Deadlines: Deliver a project on time
● Manage the Budget: Make money for the company
● Client Satisfaction: Happy clients keep coming back
● Quality Control: Ensure a defect-free product
● Resource Coordination: Manage internal and external resources
Page 7 | How Technical Should A Drupal PM Be?
Does It Even Matter?
Yes! If you were building a new
home, would you hire a general
contractor that has never picked up
a hammer before?
Page 8 | How Technical Should A Drupal PM Be?
Why Does It Matter?
● When building a new home,
this may be a once in a lifetime
event.
● When building a website, it’s
not an everyday occurrence
either.
Page 9 | How Technical Should A Drupal PM Be?
So here’s my answer!
September 1, 2016
Page 10 | How Technical Should A Drupal PM Be?
How Technical Should a Drupal PM Be?
It Depends...
Upon the complexity of the project!
Page 11 | How Technical Should A Drupal PM Be?
Ecommerce
3rd Party IntegrationsCustom Module Development Performance SLA
Encryption
It Depends!
Complex Views CRM Integration
MultilingualSmall Marketing Website
Page 12 | How Technical Should A Drupal PM Be?
It Depends!
Page 13 | How Technical Should A Drupal PM Be?
What does a Drupal PM need to know?
September 1, 2016
Page 14 | How Technical Should A Drupal PM Be?
The Basics
Understand the Drupal CMS
● Adding Content (using CK Editor)
● Updating Menus
● Basic HTML & CSS Editing
● Managing Taxonomies
● Know the terminology (nodes, entities, content types, etc.)
Page 15 | How Technical Should A Drupal PM Be?
Intermediate Skills
● Basic understanding of views
● How the block system functions
● Basic understanding of most commonly used modules:
● Creating and configuring contact/webforms
● Basic site building ability
Page 16 | How Technical Should A Drupal PM Be?
Intermediate Skills
● Paragraphs● Pathauto● Admin Toolbar● Responsive Menu● Menu Trail by Path● IMCE● Video Embed Field● Focal Point
● External links● Recreate Block
Content● View Unpublished● Recaptcha● Contact Storage● Config Split● Rabbit Hole
● Better Exposed Filters
● GA / Tag Manager● Xmlsitemap● Metatag● Domain Access● Redirect● Groups
Page 17 | How Technical Should A Drupal PM Be?
Advanced Knowledge
● Drupal Permissions
● Views Config
● Configuration Management
● Commerce Features
● Module Config
Page 18 | How Technical Should A Drupal PM Be?
Advanced Knowledge
● How to use git○ Create Branches○ Good commit messages○ Merging○ Pull requests
● Local Development Tools○ Drupal VM○ Acquia dev desktop
Page 19 | How Technical Should A Drupal PM Be?
But wait, there’s more!
September 1, 2016
Page 20 | How Technical Should A Drupal PM Be?
Drupal & Beyond!
● Information Architecture
● QA & Cross Browser Testing & Tools
● UX Design & Web Accessibility Best Practices
● Google Analytics & SEO Basics
● 3rd Party Applications
Page 21 | How Technical Should A Drupal PM Be?
Information Architecture
● Content Inventory
● Tree Testing, Card Sorting, Click Testing
● Conversion Paths
● Journey Mapping Exercises
Page 22 | How Technical Should A Drupal PM Be?
UX & Design
● Wireframe tools
● Understanding of responsive design principles
● Have an opinion on good design
Page 23 | How Technical Should A Drupal PM Be?
Web Accessibility
● Perceivable Information & UI
● Understandable Information & UI
● Operable User Interface & Navigation
● Robust Content and Reliable Interpretation
Page 24 | How Technical Should A Drupal PM Be?
QA Testing
● Peer Code Review
● Security & Penetration Testing
● Performance Testing
● Cross Browser Testing
Page 25 | How Technical Should A Drupal PM Be?
Analytics & SEO
● Google Analytics
● Heat Mapping Tools
● Google Tag Manager
● Core SEO Principles
● CRM & Email Marketing Tools
Page 26 | How Technical Should A Drupal PM Be?
3rd Party Applications
● Marketing Automation
● Personalization
● CRM Tools
● Split Testing Tools
● Translation Services
Page 27 | How Technical Should A Drupal PM Be?
What should I do?
September 1, 2016
Page 28 | How Technical Should A Drupal PM Be?
Improve Your Skills & Deepen Your Knowledge
● Build your own website, and use Drupal!
● Educate yourself
● Annoy your engineers
Page 29 | How Technical Should A Drupal PM Be?
In Summary
September 1, 2016
Page 30 | How Technical Should A Drupal PM Be?
How Technical Should a Drupal PM Be?
● Does it Matter? YES!
● A Digital PM’s technical abilities and understanding should be commensurate with the complexity of the project.
Page 31 | How Technical Should A Drupal PM Be?
How Technical Should a Drupal PM Be?
In the end, you’re only helping your project team to:
● Hit Deadlines: Deliver a project on time
● Manage the Budget: Make money for the company
● Client Satisfaction: Happy clients keep coming back
● Quality Control: Ensure a defect-free product
● Resource Coordination: Manage internal and external resources
Page 32 | How Technical Should A Drupal PM Be?
Questions?
September 1, 2016
Page 33 | How Technical Should A Drupal PM Be?© 2018 Oomph, Inc. All rights reserved.
Thank You
September 1, 2016
oomphinc.com
401-228-7660 | 72 Clifford Street, Providence, RI 02903