This phase is a critical starting point for understanding a project's scope, defining the organisational needs, and determining a project's required outcomes. This phase is often done by a project team internally before engaging with Public Purpose Technologies, utilising the skills and experience of your team. However, we love this phase of the project and are happy to deliver it.

This phase sets the foundation for the project planning and execution by providing a detailed understanding of the project objectives, the people involved, the system or solution requirements, and the overarching strategy for development and delivery. This approach ensures that all policy requirements are considered before moving to the next stage of a project, the technical assessment.

Input

What we need from you for this pre-engagement can usually be achieved through a Requirement Workshop with follow-ups to ensure we have all required background information, context and policy or legal constraints. The required info will include:

• An initial problem statement

• Background research

• Policy or legal documents the project must work within

• Regular time with a project lead who can answer questions as they arise during the period.

Output

You will be provided with a Requirements Gathering report and overview slide deck that will include:

• Refined Problem Statement with end-user validation

• Stakeholder/end users/audiences Personas

• Technical Requirements

• Possible Feature list with prioritisation

• Delivery Methodology

• Recommended Sprint Structure

• List of Legal and policy constraints/considerations with mitigation recommendations where appropriate

• General Business Analysis

Time and Resource:

1 Month - From the Requirement Workshop date, and once we have all required information. If you have the required input information, you should allow one month for delivery - subject to availability.

Our resource - A project manager will likely work with a minimum of three other roles during the Requirements Gathering phase:

• Engagement lead / Designer

• Solution Architect / Lead Developer

• Business Analysts / Researcher.

Note: an individual may perform more than one role.

Your Resource - We need to have regular and open communication with your team. At a minimum, this should include:

• Weekly meetings with a project lead, including availability between meetings

• Two meetings with the project sponsor or key decision maker during the Requirements-gathering phase.

• Wrap-up meeting and retro

Cost: $15,840

Requirements Gathering: Pre-engagement