Page Comparison

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

• Milestone 1 adjustments Karolina Kopacz (Deactivated)

• Draft form Karolina Kopacz (Deactivated)

• Saving and editing draft Karolina Kopacz (Deactivated)

• Getting requirements from gitbook Łukasz Ruzicki

Questions and comments to the outcomes demo

• We should update the text in the deployment compliance step to make it clearer for the user, Steve will prepare the text that we can use

• We do not have authorization for the draft but the unique ID is generated and the only way to edit it is to get an access to the link, it’s impossible to guess

• Is format for all gitbook requirements correct?

  • We need to verify it, Łukasz Ruzicki will check this

Necessary adaptions (identify + plan)

• Deployment 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?

   Jira Legacy
   server System JIRA serverId f5c6bdaf-d23e-347d-a1e8-579e20a81dda key TECH-895

Short vision for the next sprint 

Sprint goal:

• Compliance form can be submitted.

• GovStack approver can log in to the system.

Additional points:

• Update test harness based on changes to APIs (

  Jira Legacy
  server System JIRA serverId f5c6bdaf-d23e-347d-a1e8-579e20a81dda key TECH-972

  )

Mifos circleCI requirements

PR was merged and it’s in the testing phase. It will be presented by Damian Borowiecki (Deactivated) on thursday’s technical committee meeting