Technical Risk Register

S/N	DATE	DESCRIPTION	Identified by	Risk / issue	MITIGATION	RISK OWNER

S/N	DATE	DESCRIPTION	Identified by	Risk / issue	MITIGATION	RISK OWNER
RK-1	Jan 26, 2023	BB Specifications are too vague/high-level. Even if there would be more than one implementation of a BB, it is unlikely to be a drop-in replacement for others.	@Meelis Zujev (Deactivated)	Risk	Learn from first implementations and decide upon needed detail level of specs and ambition of “drop-in replacement”	@Steve Conrad
RK-2	Jan 26, 2023	Sandbox team does a lot of use case research, way more than expected, and set assumptions which can be wrong, so that the use case implementation is not reflecting real scenarios	@Meelis Zujev (Deactivated)	Risk	Include domain experts from other initiatives to consult on the use case design (e.g. GIZ, Mifos, G2P) Follow the UC process identified by the country engagement team, and ensuring the PC is providing relevant information to the sandbox team	@Meelis Zujev (Deactivated) @Wes Brown
RK-3	Jan 26, 2023	The speed of development is so fast that we might not follow “coding guidelines”, best practices (test, peer review,…) We do not have coordinated process and not following agile principles	@Meelis Zujev (Deactivated)	Risk	Reflect in retrospectives about the current speed and potentially slow down if quality is at risk Reflect/share other WG best practicies Continue to drive toward the use of agile methodologies	@Jake Watson
IS-1	Jan 26, 2023	open-api specs aren't in most BB repos	@Taylor Downs	issue	Find a paid contributor for each BB and ask them to spend their next billable hour moving their specification to `/spec` There is tasks for BB Leads in Jira to include the open-api into their repos	@Esther Ogunjimi track completion of issues
RK-4	Jan 26, 2023	Coordination between sandbox and testing team if sandbox makes progress before API specs, adaptors, and configuration scripts for real examples are in BB repos, sandbox team will be blocked. (and depending on how they're contracted that might get expensive!) Different tech approachis in Sandbox and Testing project set-up may couse extra work (Docker compose vs Kubernetes)https://govstack.slack.com/archives/C02UUB9SD97/p1676459013710879	@Taylor Downs@jarkkohyoty	Risk	Prioritize handling of issue IS-1 Regular sync to talk about progress and ensure alignment. Colloboration and technical argumentation before decisions	@Steve Conrad @PSRAMKUMAR @Meelis Zujev (Deactivated)
IS-2	Feb 2, 2023	API Testing team is blocked by BB reviews when progressing on test configuration	@Dominika Bieńkowska (Deactivated)	issue	Reminde the BB Leads to review	@Satyajit Suri
RK-5	Feb 8, 2023	BB candidate allignment under syncronized process and flow (cadence)- it might bring overlapping and extra work to all parties	@Meelis Zujev (Deactivated) @Satyajit Suri	Risk	Clear and open communication between all involved parties. Clear goal statment and roadmap (Follow up with Staya and Meeliz for context)