Description

This curriculum spans the breadth of enterprise Agile practice, comparable to a multi-workshop program addressing acceptance criteria across team, program, and portfolio levels, including collaboration protocols, compliance integration, test automation alignment, and cross-team coordination in scaled frameworks like SAFe.

Module 1: Defining Acceptance Criteria in Agile Frameworks

Selecting between behavior-driven development (BDD) format and traditional user story acceptance criteria based on team familiarity and domain complexity.
Deciding whether to co-locate acceptance criteria within user stories or maintain them in a separate traceability matrix for regulatory compliance.
Resolving conflicts between product owners and development teams when acceptance criteria are perceived as overly prescriptive or too vague.
Establishing a standardized template for acceptance criteria across multiple Scrum teams in a scaled Agile environment.
Integrating regulatory requirements (e.g., FDA, GDPR) into acceptance criteria without compromising Agile responsiveness.
Documenting edge cases and non-functional requirements (e.g., performance thresholds) as enforceable acceptance criteria.

Module 2: Collaboration and Stakeholder Engagement

Facilitating three amigos sessions (product owner, developer, tester) to align on acceptance criteria before sprint planning.
Managing stakeholder expectations when subject matter experts provide inconsistent or contradictory validation inputs.
Deciding which stakeholders must formally sign off on acceptance criteria for high-risk features.
Handling situations where key stakeholders are unavailable during refinement, delaying criteria finalization.
Using prototypes or mockups to validate acceptance criteria with end users before development begins.
Escalating misaligned business priorities when different departments demand conflicting acceptance standards.

Module 3: Integration with Backlog Management

Enforcing a Definition of Ready that includes approved acceptance criteria before pulling a story into a sprint.
Re-prioritizing backlog items when acceptance criteria reveal higher-than-expected implementation complexity.
Splitting user stories based on acceptance criteria granularity to meet sprint timeboxes.
Tracking changes to acceptance criteria in version-controlled backlog tools to maintain audit trails.
Managing technical debt by linking updated acceptance criteria to previously closed but now non-compliant stories.
Coordinating acceptance criteria updates across dependent epics in a portfolio backlog.

Module 4: Test Automation and Validation

Choosing which acceptance criteria to automate based on frequency of change and business criticality.
Aligning Gherkin syntax in automated tests with acceptance criteria to ensure traceability.
Addressing flaky automated tests that pass or fail inconsistently despite correct implementation of criteria.
Integrating automated acceptance tests into the CI/CD pipeline without increasing build duration unacceptably.
Deciding whether to treat unautomatable criteria (e.g., UX assessments) as manual verification gates.
Maintaining test data sets that satisfy complex acceptance criteria involving stateful business processes.

Module 5: Governance and Compliance Alignment

Mapping acceptance criteria to regulatory control objectives for audit readiness in highly regulated industries.
Documenting rationale for deviations from standard acceptance criteria due to technical constraints.
Implementing role-based access controls on acceptance criteria editing to ensure change accountability.
Generating evidence packs from Jira or Azure DevOps to demonstrate criteria fulfillment during external audits.
Reconciling Agile acceptance practices with waterfall-based contractual deliverables in hybrid projects.
Establishing a change control board review for modifications to acceptance criteria post-sprint commitment.

Module 6: Handling Changes and Scope Control

Rejecting mid-sprint changes to acceptance criteria that would invalidate already-completed development work.
Logging and assessing the impact of requested criteria changes through a formal change request process.
Managing scope creep when stakeholders introduce new validation expectations not reflected in original criteria.
Re-baselining acceptance criteria after major architectural changes without invalidating prior testing efforts.
Handling discrepancies between implemented functionality and updated acceptance criteria during sprint review.
Using change velocity metrics to report on instability in acceptance criteria across multiple sprints.

Module 7: Measuring Effectiveness and Continuous Improvement

Calculating the percentage of user stories with incomplete or missing acceptance criteria at sprint start.
Tracking rework incidents caused by ambiguous or incorrect acceptance criteria.
Correlating test pass/fail rates with clarity and specificity of acceptance criteria.
Conducting retrospective analysis on stories that failed acceptance despite meeting documented criteria.
Using team feedback to refine the acceptance criteria template based on recurring misunderstandings.
Benchmarking acceptance criteria quality across teams using peer review findings and defect escape rates.

Module 8: Scaling Acceptance Criteria in Enterprise Agile

Harmonizing acceptance criteria standards across Agile Release Trains in a SAFe implementation.
Establishing centralized vs. decentralized ownership of acceptance criteria for shared components.
Synchronizing criteria across teams working on interdependent features in a program increment.
Using API contracts and service-level agreements as enforceable acceptance criteria in microservices environments.
Resolving versioning conflicts when acceptance criteria for shared libraries evolve independently.
Implementing a federated review process for cross-team features requiring unified acceptance validation.