Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

Mifos circleCI requirementsDPGs integration into Test Harness

AOB

  • Date for the next review meeting

    • Thursday 21.12

✅ Action items

  •  Damian Szafranek Discuss with Nico which statuses should be visible in the table - done and added to a ticket
    Jira Legacy
    serverSystem JIRA
    serverIdf5c6bdaf-d23e-347d-a1e8-579e20a81dda
    keyTECH-1013
  •  Steve Conrad Start a Slack conversation with Damian Borowiecki and Benjamin about the Consent BB Test harness
  •  Steve Conrad Coordinate moving source code outside of the bb-identity repository

⤴ Decisions