...

• Recap of MVP Definition, Goal and Scope

  • Define and highlight the problem the MVP aims to solve

  • Collaboratively define what the MVP means for the project and establish its scope and boundaries.

  • Scope

    • Primary Goals of the MVP

    • User Group / Possible Personas and Scenarios

      • Discuss user scenarios aligned with the problem the MVP aims to address.

      • Identify key user journeys or tasks that the MVP should support.

      • Discuss any specific considerations from a technical perspective (e.g., scalability, integrations) that should be factored in.

    • Discuss the core features and functionalities that the MVP should include, considering input from all participants.

• Design and Development Collaboration, Planning next steps and roles

  • Presentation of the Wireframe planning and context

    • Discussion regarding how to define the content

      • add an additional layer to the BPMN regarding Data input and out/ which data is provided from BBs and how to cover other content

  • Collect feedback and suggestions from backend developers regarding technical feasibility and potential challenges.

  • Facilitate a discussion on trade-offs between design and development to ensure alignment and feasibility.

• Feature Prioritization and Roadmap

  • Collaboratively prioritize the identified features based on business value, user impact, and technical feasibility.

  • Create a feature roadmap for the MVP, considering development dependencies and resource availability.

  • Discuss potential iterations or phases beyond the initial MVP release.

• Adjusting BPMN diagrams

  • Decide documentation

  • Where to start? What are the limitations and considerations?

    • What is the most valuable and impactful area to start? UI, user flow or Building Blocks? Based on this collaboratively create the flow.

Recap of the Project Vision and Goals

...

• ?The application will be placed into GovStack execution environment

Outcome / Decisions:

• New Definition of the MVP was created

• The goals created

• The scope of the MVP decided to be discussed with the customer

• Content will be created together with developers and UX team

  • UX designers will provide the possible User Flow and skeleton wireframes+ Possible high level content

  • Developers will provide poissible data, limitations of the BBs and possible content for the flow + Possible high level content

Action Items

•  Discuss minimum scope (portal/registration/Log In phase with the customer)
•  Learn about the expectations of the customer for creating the scope
•  Do they expect this MVP application going to be accessible for everyone or it is only for the Govstack community? (Consider the Primary user group)
•  Where the MVP will be running?
•  Where is the application placed will be orchestrated?
•  Is it going to be placed in the portal/sandbox? Consider BBs placement also
•  Artun Gürkan Create a diagram regarding the possible scope version 1 and version 2 of the Jarkkos comment.
•  The clear understanding of which building block is necessary for the user journey. Mapping the USCT MVP flow with BBs (Spesificly with the specifications)
•  WIREFRAME DESICION