Requirements Gathering

Our average requirements gathering process would be a fixed scope exercise, based primarily on the following:

• Planning and research, so we could come to the workshops with the right questions.

• Initial business and discovery workshops - to give us additional context around commercials, general context, team and stakeholders.

• Initial functional and technical workshops with all key stakeholders - this is where we’d start to capture the detail for the specification. We’d typically bring team members into these sessions that have the right experience so it’s more of a discussion and collaboration, and we’re building out the right requirements and solutions together.

• Internal review and solutioning.

• Agreement on solutions, including commercials and implementation route.

• Enhancement of documentation.

• Presentation of specifications and documentation with agreement on next steps.

Our team has deep experience in scoping out complex projects across a wide range of ecommerce platforms and technology stacks, and we’re also partnered with most platforms and key tech partners.

The level of detail we go into varies, depending on the complexity of the project, budget and the people that are going to be working with the spec. The most common use case is that we build out a detailed spec to give to agencies so they’re able to accurately quote for a project, without having to include T&M or broad ranges in their proposal. In addition to this, we often scope out more technical requirements and then propose different solutions to the agency or internal team.