51 to 52 of 52 Contract Acceptance Criteria Jobs

stakeholders to gather functional and technical requirements for the re-write. Documenting these requirements in JIRA as Features and User Stories with clear acceptance criteria. Re-writing the applications using our standard TypeScript/React boilerplate and development guidelines. Following internal version-control practices and using the development environment … contractor will have access to required systems and documentation. Stakeholders and the Product Owner will be available for requirement discussions and sprint reviews. Acceptance Work will be considered complete when all agreed Features/Stories are delivered, accepted by the Product Owner, meet our coding and security standards ...

Support Agile Teams in applying consistent data modelling practices and semantic layer alignment. Data Quality & Controls Translate EDM policies into domain-specific rules and acceptance criteria. Partner with delivery teams to embed automated data quality checks and validation rules into data pipelines. Ensure Features include required data quality controls … contribute to Definition of Done and acceptance criteria. Metadata, Lineage & Privacy Governance Guide Agile Teams in embedding lineage capture and metadata tagging within delivery pipelines using modern tooling (e.g., Collibra, Informatica, Alation). Ensure consistent application of metadata standards and lineage tracking across domains. Oversee PII and sensitive data ...