Skip to end of metadata
Go to start of metadata

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

Compare with Current View Version History

« Previous Version 4 Next »

\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:

  • Deployment details are saved in the compliance form.

  • There is a way in the system to get back and edit saved draft.

The sprint goal was delivered.

Sprint outcomes demo


Questions and comments to the outcomes demo

Necessary adaptions (identify + plan)

  • Deploymnet compliance in the software summary should be moved from column to row to be consistent with the current style

Requirements clarification

  1. Jira space for approver tickets. Technical Committee space is private - should it be made open or should we use a different space for it? TECH-895 - Getting issue details... STATUS

Short vision for the next sprint 

Sprint goal:

  • Compliance form can be submitted.

  • GovStack approver canlog in to the system.

Additional points:

  • Update test harness based on changes to APIs ( TECH-972 - Getting issue details... STATUS )

Mifos circleCI requirements

✅ Action items

  •  

⤴ Decisions

  • No labels