CHEFS Sprint 35 - Prioritized Objectives

Rank	Objective	Q4 Key Result(s)	Tracking Jira(s)/Items

Rank	Objective	Q4 Key Result(s)	Tracking Jira(s)/Items
1	Reduce frequency and duration of client-impacting CHEFS incidents	Establish baseline of time-to-resolution duration per incident	FORMS-966: Reduce frequency and duration of client-impacting CHEFS incidentsBacklog
2	Complete transition of product documentation from current wiki to DevEx BackStage platform	De-commission CHEFS GitHub Wiki documentation by Feb 29 2024	FORMS-967: Complete transition of product documentation from current wiki to DevEx BackStage platformDone
3	Continuous product improvement via Agile events, including NEXUS processes and bi-weekly sprint plans & reviews	Develop pilot-ready MVPs for: Addition of auth support for digital credential POC Enablement of SSO between CHEFS & Standard Keycloak-homed applications Achieve QoQ form publication growth of 10% (Average Number of Forms Published Monthly over the past year from 60 to 66) Achieve QoQ new user growth of 10%	FORMS-968: Pilot-ready MVP: Authentication support for digital credential POCDone FORMS-969: Pilot-ready MVP: Enablement of SSO between CHEFS and applications within Standard Keycloak realmClosed FORMS-971: Address Open Issues Raised Via Confluence Bug Tracker in Priority OrderBacklog
4	Develop a Conversational Form Design Experience	5 pilot users will create and publish forms using this feature by March 30 2024	FORMS-970: Initial Proposal: Develop a Conversational Form Design Experience aka Forms GPTDone
5	Implement Automated Test Suite	Automated Testing Implemented (from x% coverage to y% coverage) of codebase	FORMS-972: Implement Automated Test SuiteBacklog
6	API Gateway Integration	All API endpoints within CHEFS transitioned to API Gateway by March 30 2024	FORMS-973: API Gateway IntegrationDone