Assignment deliverables

• Title of your project, team members and who did what during the sprint
• Groomed product backlog, updated GitLab Issues.
• Updated & groomed sprint backlog, populated with issues.
• The sprint plan: a clear sprint goal, work items, the corresponding milestone.
• Sprint Review Summary
• Demo of your project
• Link to your deployed and functional project
• Link to the recording of the usability testing session
• Product feedback points and goal for the last sprint
• Sprint Retrospective board and report on improving your process:
  • What is going well and working for us as a team?
  • What are we doing wrong as a team?
  • What changes can we make?
  • What changes will we take into the next sprint?
• Link to the git repository (README, CHANGELOG and LICENCE)
  • README for your project using best practices and containing the following:
    • Headline (Name)
    • Project Description
    • Feature list
    • Demo (Screenshots or Video)
    • Link to the up-to-date deployed version of your product
    • Usage instructions / Short user guide
    • Project Installation / Deployment instructions
    • Frameworks or technologies used
    • The readme must be well written, meaningful and descriptive.
    • Use Gitlab wiki if you need to write extensive documentation.
  • MIT licence in your repository and README (if another licence, explain why)
  • CHANGELOG file in accordance with Keep a changelog guidelines, created manually or automatically (with git-cliff or a similar tool).
• The transition plan with specific action points:
  • Discuss with the customer as to what measures need to be taken to fully transition the product
  • Identify the customer’s plans for the product after its delivery.
  • Discuss maintainability, deployment, documentation, and interoperability/interfaces with other systems.
  • Identify two project aspects relevant to your customer that will be documented and included in the ReadMe (it should be some other point than what is already mentioned in the list, or the existing points should be expanded and detailed beyond what is otherwise expected. Mark them as “For customer” and provide a short explanation why these sections in particular)
  • Your goal is to maximise the benefit/value of your delivered product to the customer, and increase the chance that it’ll be useful after your final delivery.

Technical tasks

This week our goal is to deliver MVPv3 and install CI/CD routines. Some tasks were transitioned from previous milestone. Here are the broad tasks:

• Take out the most important points from the previous customer meeting and work on them
  • UI: Action buttons on the right are better to be spread horizontally. This is better for left hand users
  • UI: The "level" circle is not necessary. We decided to not include level-based progression
  • UI: Make city metrics display more legible
• Add new features for MVPv3.
  • Add ability to place roads
  • Add the university building
  • Check if the building is connected to the university by a road and only then activate it
  • Add a (draft) ability to hold events
• Graphics
  • Request sprites for UI and units
• Test driven development and CI
  • Add CI for building a web release when a merge request is accepted (i.e. new feature completed). Publish this build with GitLab Pages (if available at university's domain)
  • Add tests. Decide which features need testing and add the tests.

After everything is done, do a retrospective, update the tracking sheet and submit the assignment.