...

• Horizontal focus: Cover as many process steps of the use case as possible but restrict possible user path ways pathways through the process (follow a guided “happy path” without every thinkable if/but derivation). This option includes the UI (frontend) and the functional BB layer (backend).

...

• Vertical focus: Cover all possible user paths (as much if/but derivations as possible) but restrict to a few selected process steps. This option includes the UI (frontend) and the functional BB layer (backend).

OR

• UI focus: Cover as much many process steps of the use case on the UI via wireframes and/or frontend but do not add the functional BB layer (backend).

OR

• BB focus: Cover as much many process steps of the use case with one BB application candidate. This option uses only the frontend and backend functionalities of one BB application (e.g. eRegistration by UNCTAD).

Why is a focus needed?

• With the given resources, it is impossible to implement a country use case in an end-to-end and fully functional manner (frontend + backend). By choosing priority focus will be determined

Implementation

Phase 1: Business Analysis

...

Deliverable: BPMN Diagram of the to-be-implemented use case steps (example: USCT MVP)

...

Prerequisites:

• BPMN Diagram

• Needed(chosen) BB candidate applications integrated in into the Sandbox environment

Fixed timebox: 4 sprints (2 months)

Participants: Multifunctional team inc Full Stack of Gofore Developer TeamDeveloper, Analyst/ PM, Country Representative as the PO

Deliverable: Use Case Prototype according to the agreed prioritization. The functional scope is based on what the team can deliver in the given time box