Conditional Logic Release

[Abi-Nada]

Things to validate:

• [ ] Functionality Testing (CDS Internal Testing, QA Testing, Diary Study)
• [ ] A11y testing (Pete's internal audit, Fable testing)
• [ ] Data output and integration with client workflow (Diary Study, QA Testing)
• [ ] Does the schema work? (Dev testing)
• [ ] Backwards compatibility (Dev testing)
• [ ] Testing data loss scenarios (Dev testing, QA Testing)
• [ ] Bilingualism (testing ratio 7:3 EN/FR users)
• [ ] Security (product x tech sync)

Milestones:

• [ ] Implement findings from Fable testing (Critical and severe issues only)
• [ ] Implement findings from Internal CDS functionality testing (Critical and severe issues only)
• [ ] Implement findings from Diary Study research with Forms clients (Critical and severe issues only)
• [ ] 1.5 weeks for a dev to test backwards compatibility + validate that the schema works (QA testing at the same time)
• [ ] Brief to policy (confirm no impacts to SLA or ToU)

Client comms (Setting expectations for before and after release: drafting communications/marketing strategy):

• [ ] UI update (pre-release): Create a banner in the product to let clients know that a change is coming
• [ ] UI update (post-release): Banner on prod -> something like "Branching logic is new to GC Forms. If you find bugs, contact us to report them etc."
• [ ] Guidance documentation on using CL is translated and published
• [ ] Mailing list post is drafted and translated (Growth)
• [ ] Run through feature with Growth and Support
• [ ] GC Forms marketing site updates: Update to point to the Strategic roadmap (Growth)

Prod release: