2023-10-31 Meeting notes

Sprint summary and progress on the project

• Past sprint goal and scope validation 

• Progress vs set project goals and milestones

Sprint goal:

• There is a table in the system that enables user to see software compliance results summary

The sprint goal was not delivered. There are few reasons for that:

• We started actual work on the compliance form a little bit later than planned, we were still finishing other topics.

• We had issues with deployment and data on a test server, so proper QA testing couldn’t start.

However, all the tasks are either on review, on QA, or are waiting for final synchronization with other tickets.

The planned milestone date is not threatened, we are still confident we can deliver it on time.

Sprint outcomes demo

No outcomes demo today. We had issues with the staging server of the application. We only want to show features that were fully tested and approved on the staging server.

Questions and comments to the outcomes demo

N/A

Necessary adaptions (identify + plan)

Requirements clarification

1. What should be expected format for the container field and what validation should be used?

   1. This could be either a link to the github repository or a different place with documentation (like a webpage)

   2. There should be also an alternative file upload input for the script

   3. Idea: changing field name to something more explanatory (ex: deployment instructions)

2. Should there be any verification if given software receives more than one form?

   1. For now we will allow multiple forms for the same software

   2. We should discuss it in the future how to handle it (probably with user authentication)

3. How to differentiate cross-cutting requirements for interface and for requirement specification

   1. Interface requirements would be “CRoss-Cutting Requirements”

   2. Second tab “Requirement Specifiction” would be “Functional Requirements”

4. What action should be taken upon pressing help button?

   1. Investigate if it’s possible to provide a slack link to a specific channel

   2. If it’s not possible, it should be an email to Wes and Steve

Short vision for the next sprint 

Sprint goal:

• There is a detailed compliance results report for each software.

• There is a way in the system to start a compliance form.

Additional points:

• Finishing up work from previous sprint

• Consent BB API compliance testing (https://govstack-global.atlassian.net/browse/TECH-967)

• IF we manage to catch up: Update test harness based on changes to APIs (https://govstack-global.atlassian.net/browse/TECH-972)

Discuss and decide what DPGs should be integrated into test harness 

• OpenIMIS

• Mifos

Mifos circleCI requirements

How to integrate their process with test harness?

@Damian Borowiecki will look into that and verify what’s needed

https://govstack.slack.com/archives/C053PAUE4HY/p1697816852277189