Part 2: Train Wrecks & Ugly Baby Client Meetings
This is from last year's highly-rated DrupalCon Amsterdam session with ample how-to action items. Over the past 10 years, this proven project methodology will save you time, money and heartache.
Who Should Attend:
-- Sales people who want to know more about business analysis & discovery
-- PMs who want to know more about balancing project power & authority
-- Shops who sell great projects but struggle with delivery
-- CEOs who want to balance authority, responsibility and accountability
-- Anyone who wants to make more margin and deliver success
Would you believe with a $100,000 project, as little as 50% can be spent on actual development? Where the heck is the rest of the money spent? You might be shocked how much can be wisely allocated in discovery, business analysis, risk assessment and architecture before one line of code is written.
Shocking still is that your projects will be more successful, your clients happier and your team humming like a well-oiled machine. Get recommendations, accolades and repeat business that is the holy trinity of business. Spending the effort and money in the right areas will give you the business results so many companies struggle with.
This follow-up from Train Wrecks, Ugly-Baby Meetings and other Client Calamities takes a deeper dive into the technical process of projects. This in-depth look at the discovery process can be used by small and large projects alike.
Clients are looking for strategic partners, not just a Drupal shop. In this interactive and discussion-based session, we'll cover these specific and detailed ways to walk projects through from the what, why, how, when and who. Learning how to ask the detailed questions, understand the clients needs, manage the internal politics and the entire scope of what makes a project successful will help everyone get better results.
1. Business Analysis: Learning how the client uses their data to build the right object model
-- Site audit
-- Performance audit
-- Web objectives
-- Business rules
-- Training early and often
2. Discovery: Translating their business into Drupal ideas
-- Content types
-- User Stories
-- Object modeling
3. Architecture: Moving ideas into engineering plans
4. Process: Managing teams and tasks
-- Change Orders
-- Burn Rates
5. Development: Wrapping it Up
-- User Acceptance
-- Bug fixes