why drupal projects fail英文电子书.pdfVIP

Business and Best Practices Why Drupal Projects Fail: Breaking Down Barriers to Successful Drupal Adoption Presented by cpliakas WARNING: Discussion not technical Agenda Introduction Key components to success Why projects fail Breaking down barriers to success Questions About Chris cpliakas on D (sē plā kis) @cpliakas on Twitter Module maintainer, core contributor Zend, MySQL, LPI Certified Working with Drupal for 3+ years Member of Acquia’s PS team for 1+ year Pre-sales consultant for Acquia What makes me qualified? I work with many organizations I remember learning Drupal /blog/tag/bloody-head-banging-on-keyboard-animated-gif/ Artist unknown (please identify yourself, this image is great) I see dead projects! Been in the weeds Seen the big picture There are patterns Five key components of success Project management Process Development practices Thought partnership Expertise What we are really talking about Expectation management Communication Execution Barriers Red flags We use “Company X” Drupal. We do the impossible. We have really good PHP developers that just need a couple of days to get up to speed with Drupal. We are pushing boundaries, so we do not work with the community. We have an oshore team do most of our development. We cut our rates to get the project. We will get bigger projects if we meet the aggressive timeline. Let’s break it down Mismanaged Expectations No matter the end result, a project will be viewed as a failure if the original expectations were not met. Contributing factors Product misrepresentation – Accidental – Intentional Unsustainable precedence – Timeline – Cost Communication breakdown Lack of transparency Client / stakeholder driven project