> For the complete documentation index, see [llms.txt](https://specs.govstack.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://specs.govstack.global/implementation-playbook/0.9.0/govstack-implementation-playbook/adopt-govstack/design-and-delivery/prototype.md).
# Prototype
## Develop, test, and iterate a functional prototype.
Once the [wireframe ](https://govstack.gitbook.io/implementation-playbook/govstack-implementation-playbook/design-and-delivery/wireframes)[and/or voice command flow](https://govstack.gitbook.io/implementation-playbook/govstack-implementation-playbook/design-and-delivery/wireframes) is approved, we are ready to start developing and orchestrating a functional prototype of the service. The prototype is iteratively developed. Each successive iteration adds new functionalities and refines the prototype based on user feedback. This results in a service that meets the desired level of functionality and usability.
What are the benefits of protoyping?
Prototyping an e-service allows:
* Pre-procurement testing of software solutions
* Technical feasibility check
* Requirement gathering (e.g.BPMs) for procurement
* Transparency of the inner functioning of the Building Block approach
* Reference set-up for development, deployment, and operating life cycle
* Testing the Frontend with Users/Citizens
{% tabs %}
{% tab title="Activities / Resources" %}
* Develop Product and Technical specifications for the service.
* Develop the front end and back end of the service according to the Product and Technical specifications and approved wireframes and/or voice command flow.
* Develop a test script considering all the branches of "To-Be" user journey.
* Prepare
* test scripts
* security and quality assurance checklist
* digital service release plan
* stabilization and maintenance routine
* Refer [GovStack sandbox](https://govstack.gitbook.io/sandbox) documentation and prototype service using rapid prototyping tools. Learn more about the use of prototyping tools by reading the [Do It Yourself (DIY) Full Stack Sction](https://govstack.gitbook.io/sandbox/follow-methodology/diy/diy-full-stack) of GovStack Sandbox documentation.
* Launch α, β versions to a limited set of citizens/business users, admins, and public officials.
* Collect their feedback on the functional prototype and identify concrete steps to improve it.
* Iteratively developed and deliver the launch version that meets the requirements and needs of citizens/business users, admins, and public officials.
* Prepare the plan for migration of the prototype to the production environment.
* Prepare the launch of the service.
{% endtab %}
{% tab title="Responsibilities" %}
Who does what
* [Service designer](https://govstack.gitbook.io/implementation-playbook/govstack-implementation-playbook/annex/govstack-user-profiles-taxonomy#service-designer) – Lead the service co-design journey
* [Product Owner](https://specs.govstack.global/workflow/workflow-development/) – Lead software product development according to the service blueprint
* [Front-end developer](https://govstack.gitbook.io/implementation-playbook/govstack-implementation-playbook/annex/govstack-user-profiles-taxonomy#front-end-developer) – Develops front-end applications following UX/UI style guide
* [Solution architect](https://govstack.gitbook.io/implementation-playbook/govstack-implementation-playbook/annex/govstack-user-profiles-taxonomy#solution-architect) – Architects the service according to the BB integration plan
* [Back-end developer](https://govstack.gitbook.io/implementation-playbook/govstack-implementation-playbook/annex/govstack-user-profiles-taxonomy#back-end-developers) – Adjust BB, connects legacy systems, and test the application
* [Digital security manager](https://govstack.gitbook.io/implementation-playbook/govstack-implementation-playbook/annex/govstack-user-profiles-taxonomy#digital-security-manager) - validates compliance with digital security policy
* [Cloud architect](https://govstack.gitbook.io/implementation-playbook/govstack-implementation-playbook/annex/govstack-user-profiles-taxonomy#cloud-architect) - Designs cloud strategy and microservices architecture that supports the digitalization of government services
{% endtab %}
{% tab title="Deliverables" %}
Deliver a functional prototype of the service which:
* Complies with the approved 'To-be user journey' and wireframe and/or voice command flow
* Complies to Country digital service design standards. This includes standards for:
* [Service information sheet](https://govstack.gitbook.io/implementation-playbook/govstack-implementation-playbook/learning-and-exchange/artefacts#information-service-sheets)
* [Downloadable forms](broken://spaces/zlgZ7XvqYnhGTNjlQo19)
* [Web forms](broken://spaces/zlgZ7XvqYnhGTNjlQo19)
* [Electronic documents](broken://spaces/zlgZ7XvqYnhGTNjlQo19)
* [Notifications](broken://spaces/zlgZ7XvqYnhGTNjlQo19)
* [Performance analytics](broken://spaces/zlgZ7XvqYnhGTNjlQo19)
* [Citizen satisfaction survey](broken://spaces/zlgZ7XvqYnhGTNjlQo19)
* [Accessibility ](broken://spaces/zlgZ7XvqYnhGTNjlQo19)
* Complies with Country enterprise architecture, including digital security protocols approved by the country technical team
{% endtab %}
{% endtabs %}
Iterative prototyping
Following are the stages of prototyping a digital government service, from α version to the Launch version:
* α version prototype: α version is a rough functional prototype used to test the initial concept and get feedback from a limited number of users and stakeholders. The duration for the α version must be agreed upon between service owners and stakeholders. It usually lasts between a few weeks and months. α version can be hosted in a testing environment that may or may not be the GovStack Sandbox.
* β version prototype: Once the α version is tested and feedback is collected, the β version is developed. This prototype is more refined and is closer to the final digital service. It includes more features and functionalities and is tested by a larger group of users or stakeholders to identify any final issues before launching the next iteration.
In case the β version is hosted on GovStack Sandbox, preparations must be made to deploy it on the country's cloud infrastructure/ production environment.
* Launch version: The launch version is the first version of the service that is released to the public. It includes the core features and functionalities that meet the needs of the users and are further iterated based on future user feedback.
*
```
Iterative prototyping
```
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://specs.govstack.global/implementation-playbook/0.9.0/govstack-implementation-playbook/adopt-govstack/design-and-delivery/prototype.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.