Discovery and Requirements Gathering
Download as KEY, PDF1 like1,635 views
The session on 'getting paid (and adding greater value) in discovery' at the Pacific Northwest Drupal Summit focuses on the paid discovery process that helps both clients and service providers effectively gather requirements upfront. Presenters Sean Larkin and Andrea Burton will discuss methodologies for identifying stakeholders' needs, translating them into actionable project plans, and successfully communicating the value of paid discovery to clients. The session will also cover tools and strategies for scoping discovery and moving into implementation stages.
Discovery and Requirements Gathering
- 1. GETTING PAID (AND ADDING GREATER VALUE) IN “DISCOVERY” October 16th | Pacific Northwest Drupal Summit | PDX, OR
- 2. SYNOPSIS PNWDS Session: Getting paid (and adding greater value) in "Discovery" Track: Business and Project Management Experience level: Beginner, Intermediate Presenters: Sean Larkin and Andrea Burton of ThinkShout, Inc. Summary: Responding to RFPs, well, stinks... All that upfront work, guessing true requirements, fretting over how your budget breaks out compared to that of your competitors... It's a lot of work and nobody really wins - most importantly not your prospective client. Enter "the Paid Discovery Process." In this session we will review successful approaches to engaging in upfront, paid requirements gathering processes with new clients. We will discuss ways to explain the discovery process to prospective clients - as well as methodologies for exploring and documenting the needs of key organizational stakeholders and the target audience of the proposed website/ application. Finally, we will discuss the process of turning the results of paid discovery into an actionable project plan. Schedule info: Time slot: 16 October 13:30 - 14:20 Room: Astoria
- 3. AGENDA • What is Discovery and how does it fit into project management process? • How to talk about Paid Discovery • How to scope Discovery • Translating Discovery documentation into a winning contract for implementation • Subsequent implementation steps: Development plan; Quality assurance plan • Tools
- 4. WHAT THE HECK IS DISCOVERY?
- 5. DISCOVERY & PROJECT MANAGEMENT • Discovery: • Requirements gathering: • Desired outcomes • Personas (goals and motivations of site visitors) • User stories • First pass at budget and prioritization of features • Information architecture: • Site map • Wireframes • Content matrix • Finalize budget and prioritization of features • Implementation: • Graphic design • Software development • Quality assurance & Training • Content staging • Launch and support
- 6. REQUIREMENTS GATHERING • Desired outcomes • Personas (goals and motivations of site visitors) • User stories (ThinkShouter Andrea Burton facilitating a “storyboarding” session for Meyer Memorial Trust. ) Then, after first round of requirements gathering, do an initial prioritization of features and back-of-the- envelop budget.
- 7. INFORMATION ARCHITECTURE • Site map • Wireframes • Content matrix Then, after presenting site map and wireframes, review how they correspond to desired outcomes and talk about the budget and prioritization of features.
- 8. WIREFRAMES
- 11. HOW TO TALK ABOUT “PAID” DISCOVERY • Pull together the right people to implement successful services. • Focus and remember what the heck you’re trying to do. • Create a compelling story when going after funding. • “Dating” the right vendor. • Identifying true development costs and “Total Cost of Ownership.” • “Living document” to support ongoing development, quality assurance, training, content staging, etc. • Documentation is “portable.”
- 12. HOW TO SCOPE DISCOVERY A truly thorough discovery process is expensive - sometimes you can get away with choosing pieces as you go.
- 13. TRANSLATING DISCOVERY INTO A WINNING CONTRACT
- 14. FOLLOWING THROUGH • Translating discovery into a development roadmap • Quality assurance and training based upon discovery documentation • Content staging • Planning for future phases of development
- 15. THANK YOU! Sean Larkin 760.223.0589 (cell) sean@thinkshout.com Andrea Burton andrea@thinkshotu.com ThinkShout, Inc.