3. Deliverables

This section describes all the deliverables you need to provide during the course of the project.

We expect all of the following deliverables:

  • D1: Business case including financial analysis (documentation repo) Document describing in detail how you'll handle the launch of your first product and how you'll meet solvency requirements.
    This should be a Google Doc based on the Business Case template document (see the Resources section), which you link in the readme of the repo.
    Details on the contents of this document will be handled in the input sessions "Business Case and documentation".

  • D2: Project website (documentation repo)
    Marketing website showcasing your company and launch product.Link and admin credentials are provided in the readme of the repo.
    This is a Google site.
    Details on the contents of this website will be handled in the input sessions "Business Case and documentation"

  • D3: Analysis document (documentation repo)
    Document describing in detail the full analysis of your first product.
    This should be a Google Doc based on the Analysis template document (see the Resources section), which you link in the readme of the repo.
    All necessary information about the scope of your product (concept / personas / user stories / feature list) are provided as well as the schematics (flow charts / C4 diagrammes /UCD / ERD ….) to describe the project.
    Clickable wireframes and visual designs documenting the extent of the project including user testing reports.
    Use the Ethical Decision Making framework to argument at least 2 ethical dilemmas.
    All this will span the full renege of your concept’s scope, which will be far more extensive than the POC implementation thereof.

  • D4: Partial exam (Leho & exam repo)
    Over the course of the first 5 weeks, you will acquire knowledge of both client and server basic technologies related to the project through a combination of knowledge clips and self-study.
    In the first project week, you will complete an individual quiz/exam to assess their acquired knowledge. This will serve as a foundation, allowing you to confidently and smoothly transition into the development phase of the project.

  • D5: Proof of Concept (POC) (client & server repo)
    Proof of concept of the software system with a working version of the project. Scope determined after approval of feature list proposal.
    Provide also a publicly accessible API documented by an OpenAPI and/or asyncAPI spec for consuming your application.

  • D6: Project work, peer evaluations and retrospections (Leho & in gitlab)
    Every project day starts with a daily standup.
    All your project management epics(=user stories)/issues/tasks (both technical and otherwise) must be created and assigned in gitlab. Each Team member will log their work time they perform under the correct issue.
    Throughout the semester, we will implement various peer assessments and reflections. These will be collected on Leho.

  • D7: Presentation for investors jury (documentation repo)
    Final presentation of your work, where you'll convince a jury to invest in your product.

Warning

Omission of a single deliverable will result in a failing score for the entire module.