Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Current »

\uD83D\uDDD3 Date

\uD83D\uDC65 Participants

\uD83E\uDD45 Goals

In those meetings, we should mainly focus on the Compliance Form development progress.

The purpose of this meeting is to show and validate past sprint increments and determine future adaptations. 

\uD83D\uDDE3 Discussion topics

Item

Notes

Sprint summary and progress on the project

  • Past sprint goal and scope validation 

  • Progress vs set project goals and milestones

Sprint goal:

  • Compliance form can be submitted.

  • GovStack approver can log in to the system.

The sprint goal was not delivered.

Features that were moved to the next sprint:

  • Email notifications

  • Automated Jira ticket creation

  • Authorization system

  • Software version in form

Sprint outcomes demo


Questions and comments to the outcomes demo

Necessary adaptions (identify + plan)

Requirements clarification

  • Should we take requirements from every version or only from released BBs?

    • We should use only released BBs but version won’t always use semantic versioning

  • Software Compliance table - should we show all forms (Status: DRAFT, IN_REVIEW, APPROVED, REJECTED)

Short vision for the next sprint 

Sprint goal:

  • Finalizing Software Form Handling

  • Implementing Approver functionalities

Features planned for the sprint (in order of importance):

  • Automated Jira ticket creation (Milestone 2)

  • Email notifications (Milestone 2)

  • Adding Software Version to the form (Milestone 2)

  • Authorization system (Milestone 3)

  • Read-only mode for the form (Milestone 3)

  • Help button

  • Filtering

DPGs integration into Test Harness

AOB

  • Date for the next review meeting

    • Thursday 21.12

✅ Action items

⤴ Decisions

  • No labels