Can't always get what you want (from clients)? Get what you need!

Business and Strategy

Doesn't it just drive you crazy when a client gives you way too much documentation, explains what they need way too clearly, and provides way too much insight into their objectives?

Didn't think so.

More often, at the start of an engagement, your client will have a general idea of what they want, possibly with a couple design mockups and a feature wishlist. Developing a small site from this kind of information is dangerous...on a large site, it's disastrous.

In this session we'll look at how to run a strong discovery process that collects the documentation we need prior to building a Drupal project. Topics include:

  • The risks of inadequate documentation
  • The roadblocks to acquiring needed documentation
  • What you really, really need to get from your clients
  • Different levels of client understanding and preparation
  • Approaches to helping clients express what they really need
  • Reconciling thorough documentation with Agile development
Intended audience: 

Project Managers, Account Managers, Project Owners

Questions answered by this session
Question 1: 
What information is critical at the start of a Drupal project?
Question 2: 
What are the components of a successful discovery?
Question 3: 
What communication issues are you likely to encounter in obtaining needed information?
Question 4: 
How can you effectively work with different client types during discovery?
Question 5: 
What are you risking by not performing an adequate discovery?
Your rating: None Average: 4 (30 votes)

Diamond Sponsors

Platinum sponsors


Gold Sponsors

Chapter Three
Treehouse Agency
Drupal Connect