Page Comparison

GeneralAgile/Scrum Overview

Engagement Strategy

• David, as policy analyst, can be kept in the loop for future meetings regarding the project.

• Quick note: Scott will be covering for Heather for the next two weeks while she is away.

• The program area sees the value of the Agile approach for this project.

Engagement Strategy

• Heather has been working on a more formal engagement strategy to be able to involve the Operators. A draft will be sent next week.

• The program area agrees that it is very important to engage with the end users to test, and only test, the functionalities developed on the CHEFS platform. The purpose of this engagement is not about getting the requirements from the operators.

• Testing of the reporting capabilities will be done by the program area.

• The engagement with the operators is a bit more sensitive but we will look at connecting with one representative of each type of operator (i.e., personas). Jay will help identify this with the HAs.

• We want to be mindful of the amount of hours required from the HAs or the operators (6 hours every 2 weeks could be too much).

• The priority should be put on the Health Authorities when it comes to testing functionalities. For each given functionality a first round of testing with the HAs will help eliminate the main so that the next round with the operators can be quicker.

Next Steps

• Jay will reach out to the HAs to try and identify the main operators who will represent the main personas

• Heather will send a draft of the engagement strategy to CGI by Tuesday August 2^nd

• CGI (Killian) will schedule a meeting to review the draft of the engagement strategy

• CGI (Killian) will schedule the Introduction to Agile session with the Program Area