While a picture is worth a 1,000 words, our discovery workshops are worth 10,000. When starting off with any major website development project, the most critical task is properly aligning the vision of the client and the development team. A detailed discovery process can save clients anywhere from tens to hundreds of thousands of dollars in both direct project costs and the cost of delaying a major project launch when scope creep pushes back a projects final delivery.
At Facet our business analysts leverage a series of exploratory, architectural, and review tasks that promote transparency between the client and development team. Our workshops have a proven track record of success with both direct clients and white label agencies who love our process. Don’t take our word for it though, let’s dive into the process and you can decide for yourself.
Our process can be broken down into three phases:
- The Exploratory Phase consists of drafting questionnaires, collection of assets, and execution of any virtual meetings, teleconferences, or on-site workshops to collaborate on business intelligence surrounding the project.
- The Architectural Phase consists of formulating the information architecture, drafting wireframes, drafting the final discovery report, and performing small follow-up meetings to confirm findings and ask for clarification on functional workflows.
- The Review Phase consists of the final internal review of the project with lead developers on staff at your agency, as well as a final meeting with the client to review the findings of the project and to present the intended architecture. Final edits are made in this phase as any discerning questions arise.
Agile & SCRUM Discovery
In order to maximize the value of our discovery, we utilize the SCRUM methodology when collecting project requirements and project feature requirements.
The method is straightforward:
- Detail product requirements by adding items to the project backlog with high-level user stories, acceptance criteria, and priorities for each feature.
- Detail exclusions or exceptions from the project—this is especially important when migrating a website from an old platform into Drupal or another content management system.
- Identify key project requirements such as business rules and quality expectations including:
- Performance criteria - page load time, performance under traffic spikes, etc.
- Security criteria - site hardening, ISO compliance, identity management, etc.
- Constraints - timeline constraints, integration constraints, etc.
- Non-development criteria - design requirements, SEO strategy and configuration, training requirements, etc.
- Assess project complexity with development team’s story point voting—this allows us to gain perspective on what is going to be costly to implement before handing off the project to the estimation team.
Once the discovery workshop is complete, we deliver a discovery report to the client for discovery sign-off detailing:
- Project Requirements
- Project Backlog - priorities, user stories, acceptance criteria
Once the discovery sign-off is complete, your project is now ready for:
- Final estimates from our development team.
- Publishing as a requirements document in an RFP.
- This discovery is especially valuable if you are a public institution including a higher education institution or government agency.
- Or, if you’re one of our white label agency clients, you can then have your internal development team perform a final estimate.