april 11, 2019 - how... · page 3 | how technical should a drupal pm be? matthew o’bryant...
TRANSCRIPT
Page 1 | How Technical Should A Drupal PM Be?
April 11, 2019
Page 2 | How Technical Should A Drupal PM Be?
How Technical Should a Drupal PM Be?
April 11, 2019
Page 3 | How Technical Should A Drupal PM Be?
Matthew O’BryantDirector of Strategy - Oomph, Inc.
401-228-766072 Clifford Street, Providence, RI 02903
oomphinc.comoomph.is/[email protected]
Page 4 | How Technical Should A Drupal PM Be?
Does it even matter?
September 1, 2016
Page 5 | 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 6 | 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 and nails before?
Page 7 | 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 8 | How Technical Should A Drupal PM Be?
So here’s my answer!
September 1, 2016
Page 9 | How Technical Should A Drupal PM Be?
How Technical Should a Drupal PM Be?
It Depends...
Upon the complexity of the project!
Page 10 | How Technical Should A Drupal PM Be?
Would You Be Comfortable?
Managing the build of a comfy dog house for Scout.
Page 11 | How Technical Should A Drupal PM Be?
Would You Be Comfortable?
Managing the build of a new shed for your backyard.
Page 12 | How Technical Should A Drupal PM Be?
Would You Be Comfortable?
Being the general contractor overseeing the build of your dream house.
Page 13 | How Technical Should A Drupal PM Be?
Would You Be Comfortable?
Overseeing the construction of an engineering marvel such as the Space Needle.
Page 14 | How Technical Should A Drupal PM Be?
Ecommerce
3rd Party IntegrationsCustom Module Development Performance SLA
Multilingual
It Depends!
Complex Views CRM Integration
SOLRSmall Marketing Website
Page 15 | How Technical Should A Drupal PM Be?
What does a Drupal PM need to know?
September 1, 2016
Page 16 | 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 17 | 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 18 | How Technical Should A Drupal PM Be?
Intermediate Skills
● Layout Builder● Pathauto● Search API● Responsive Menu● Menu Trail by Path● IMCE● Video Embed Field● Focal Point
● External links● Recreate Block
Content● View Unpublished● Recaptcha● Contact Storage● Config Split● Paragraphs
● Better Exposed Filters
● GA / Tag Manager● Xmlsitemap● Metatag● Domain Access● Redirect● Groups
Page 19 | How Technical Should A Drupal PM Be?
Advanced Knowledge
● Drupal Roles & Permissions
● Views Config
● Configuration Management
● Commerce Features
● Module Configuration
Page 20 | How Technical Should A Drupal PM Be?
Advanced Knowledge
● How to use git○ Create Branches○ Good commit messages○ Pull requests○ Merging
● Local Development Tools○ Drupal VM○ Acquia dev desktop○ Lando
Page 21 | How Technical Should A Drupal PM Be?
But wait, there’s more!
September 1, 2016
Page 22 | 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 23 | How Technical Should A Drupal PM Be?
Information Architecture
● Content Inventory
● Tree Testing, Card Sorting, Click Testing
● Conversion Paths
● Journey Mapping Exercises
Page 24 | How Technical Should A Drupal PM Be?
UX & Design
● Wireframe tools
● Understanding of responsive design principles
● Have an opinion on good design
Page 25 | 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 26 | How Technical Should A Drupal PM Be?
QA Testing
● Peer Code Review
● Security & Penetration Testing
● Performance Testing
● Cross Browser Testing
Page 27 | 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 28 | How Technical Should A Drupal PM Be?
3rd Party Applications
● Marketing Automation
● Personalization
● CRM Tools
● Split Testing Tools
● Translation Services
Page 29 | How Technical Should A Drupal PM Be?
What should I do?
September 1, 2016
Page 30 | How Technical Should A Drupal PM Be?
Improve Your Skills & Deepen Your Knowledge
● Build your own website, and use Drupal to do it!
● Educate yourself - Drupalize.me, Coursera, Talking Drupal
● Annoy your engineers
Page 31 | How Technical Should A Drupal PM Be?
Why should you do this?
September 1, 2016
Page 32 | How Technical Should A Drupal PM Be?
What Are the Benefits?
● Increases empathy for your development team
● Improves communication on your team
● Positions you to help out the team on low risk tasks when needed increasing the velocity in which you can get things done
● Better positions you to communicate the value of the work your team is doing to your clients
Page 33 | How Technical Should A Drupal PM Be?
In summary
September 1, 2016
Page 34 | How Technical Should A Drupal PM Be?
How Technical Should a Drupal PM Be?
● Does it Matter? YES!
● A Drupal PM’s technical abilities and understanding should be commensurate with the complexity of the project.
Page 35 | How Technical Should A Drupal PM Be?
How Technical Should a Drupal PM Be?
In the end, you will be better positioned to help your team:
● 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
● Coordinate Resourcing: Manage internal and external resources
Page 36 | 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
Subtitle
Add speaker name here
Title slide
Join us forcontribution opportunities
Friday, April 12, 2019
9:00-18:00Room: 602
Mentored Contribution
First TimeContributor Workshop
GeneralContribution
#DrupalContributions
9:00-12:00Room: 606
9:00-18:00Room: 6A
Subtitle
Add speaker name here
Title slide
What did you think?
Locate this session at the DrupalCon Seattle website:
http://seattle2019.drupal.org/schedule
Take the Survey!
https://www.surveymonkey.com/r/DrupalConSeattle
Page 39 | How Technical Should A Drupal PM Be?
Questions?
September 1, 2016