Goals
As the forminators team works to build their capabilities, there are several goals we must work towards as we look to build a strong foundation. Ministry teams shall build their Our current non exhaustive list of goals as we liaise with the showcase team on making the best version of CHEFS for the citizens of BC includes;
We shall continue to maintain the ability to build own custom features while contributing to the common code base under . To do so requires both teams to work and develop an overall Product Governance model (preferably an oversight committee with ministry reps to guide) and a ceremony or scrum of scrums to continue to prioritize and approve completed work.
CHEFS becomes a non-hosted common codebase with ministries standing up their own hosted service and becoming a subscriber of the common component (Is this also a CITZ goal?)
One team must own shall manage the code repository and accept the final merge of new code to the common codebase (maintainer role) – NRM for now but working . As of May 20022 the gatekeeper for all production pull requests is the NRM senior dev team. Both teams shall continue to collaborate on an improved model and towards a handover to CITZ/OCIO maintaining a shared oversight
Current Activities on deck (May 2022)
Onboarding and foundational work: work with the UX team to identify high value ‘quick win’ bug and corrections from user feedback surveys. This will give out UX and Dev teams time to familiarize themselves with working with the base product.
Work to identify & unpack the existing architectural patterns to form a more common codebase. This will enable a foundation for plug and play ministry specific features via configuration (CHEFS was stood up quickly for NRM purposes) - Both teams working together
...