Quality

Plan

Define what quality means for Root

and why do we care?

The Goal

The Concept

Relativity

Context

Scope

Plan

• Regressions/incidents due to lack of testing (be it manual or automated),
• Regressions on data outputs (either due to intentional or non-intentional changes),
• Lack of E2E tests that catch regressions, Regressions on frontend (especially across verticals),
• Regressions caused by over-complexity due to different implementations of the same thing (e.g. different ways of doing validation, v1 <-> v2 milk inventory data, etc)
• Lack of e2e testing of flows
• Quick Fixes Hacks
• No way to prevent regressions or to systematically detect one
• Low confidence in every release

• low confidence in every release
• lack of a clear approach to maintain the consistency and integrity of existing logic
• unclear engineering practices
• coordination
• context is all over the place
• we don’t have a good definition of quality. what does high quality means in root context?
• poor planning
• indirection

• unconsolidated architecture/legacy systems that are not migrated/cleaned up
• no assessment history - can't see previous submission data or inventory
• code maintainability.
• technical debt.
• quick fixes hacks

Plan