Winner takes it all: About Drupal presales
k0teg
Recently, the attitude to open-source solutions in the enterprise world has changed and more and more clients choose such platforms as Drupal for building their high traffic and scalable web solutions. However, enterprise-level projects rarely won without any competition against other vendors. Usually there are numbers of proposals and most of them are very similar to each other.
In my session, I would like to share my experience and best practices derived from 30+ Drupal presales activities during last years, working at large service companies (1000+ and 10000+ people).
I will tell you about the following parts of proposals:
- Requirements analysis. Which questions to ask, and which assumptions to make?
- Architecture. How to understand if Drupal is a proper solution for given requirements, how to create a work breakdown structure, how to present your architecture using different views, prototypes and models?
- Estimates. How to make good estimates. How to assess risks?
- Document structure. What is a typical structure of responses to requests for proposals?
- Project planning. How many people do you need; how many sprints the delivery will take?
- Drupal strong and weak parts. Do’s and don’ts.
Aleh Kot is a Drupal Solution Architect at EPAM Systems Inc., Acquia Certified Developer and Zend Certified Engineer.