4 of 4 Contract Acceptance Criteria Jobs in the North West

APIs. Ability to discuss technical concepts with engineering teams, including integrations, data flows, authentication, API behaviour, environments and release constraints. Experience producing user stories, acceptance criteria, process maps, workflows, wireframes, mockups and prototypes. Good understanding of agile delivery practices and backlog management. Experience supporting QA, UAT, defect management … acceptance sign-off. Ability to explain technical topics clearly to non-technical audiences. Useful Tools & Methods Experience using tools such as Azure DevOps, GitHub, Jira, SharePoint, Lucidchart, Figma, Balsamiq or similar would be useful. Knowledge of stakeholder mapping, process mapping, user journey mapping, story mapping, impact mapping and acceptance ...

experience delivering complex technology programmes using Agile, Waterfall, and hybrid methodologies. Deep understanding of Agile SDLC concepts including: Product Backlogs Features and User Stories Acceptance Criteria Definition of Ready (DoR) Definition of Done (DoD) Sprint Planning and Retrospectives Proven experience managing cross-functional agile teams operating within distributed ...

format that can be easily understood by all stakeholders Communicate effectively across both technical and business stakeholders, ensuring the understanding of requirements and acceptance criteria is aligned. Understand business processes and activities that impact and that are impacted by the product or service. Selecting the appropriate best practice ...

Leading service transition across projects, ensuring services are ready, supportable and aligned at go-live Working with project teams to define and secure service acceptance criteria, including running readiness checkpoints Connecting teams across Enterprise Technology to ensure support teams and stakeholders are prepared for live service What ...