Skip to main content

End to end process

Before beginning

There is a backlog of projects as described in here. Based on this selection, the following step occurs.

Initiation

Upon client request (Ministry or other public sector entity), the project is initiated.

Project Synopsis

At this phase, the Digigov analysis team presents a project proposal. This proposal describes the current situation (also known as as-is) alongside with a draft of the proposed changes (also known as to-be) and the timeframe of the deliverables.

Official Commissioning

If the project synopsis is desirable, the project is officially commissioned and analysis can begin.

Analysis & Design

At this point, the analysis and service-design teams work together to identify the needs of the project. In parallel, the development team produces the boilerplate code that is not linked to the analysis and design output.

Analysis & Design Output

The output of the previous phase contains Functional Specifications described in a SRS document. A software requirements specification (SRS) is a document that describes what the software will do and how it will be expected to perform. Furthermore, it includes user stories provided by analysts and designers and also flows and wireframes produced by the designer team. As a reference, all these documents and mockups are contained in an analysis issue.

First MVP

This is the first deliverable of the project. The output of analysis and design guides what should be included in the first mvp. All other requirements and issues are moved to a general backlog. The process of delivering the first mvp is an iterative one, since it requires analysts to revisit the requirements of a projects, designers to rethink and maybe redesign their designs and developers to refactor their code. The first mvp is also a milestone.