Station

Automation Readiness Review

Review automation readiness, quality, risk, compliance, human oversight, evidence, and release criteria.

Reusable capabilities create operational, data, security, privacy, compliance, and consumer-impact risks. Readiness checks reduce surprises before release or production use.

Method map

Metro map

Select a cycle, station, or stakeholder to open its permanent method page.

StrategicGovernanceConsumerTechnicalUser ExperienceUser ExperienceMarket InsightsMarket InsightsBusiness GoalsBusiness GoalsCompetitive AnalysisCompetitive AnalysisEcosystem VisionEcosystem VisionScalable InfrastructureScalable InfrastructureLegal and ComplianceLegal and ComplianceSecurity and PrivacySecurity and PrivacyDesign StandardsDesign StandardsVendor ManagementVendor ManagementContract DesignContract DesignDevelopmentDevelopmentCI/CDCI/CDTest AutomationTest AutomationRelease ManagementRelease ManagementService AgreementsService AgreementsConsumer AdoptionConsumer AdoptionPromotionPromotionPartner IntegrationPartner IntegrationAPI MindsetAPI MindsetRoles and ResponsibilitiesRoles and ResponsibilitiesUpskillingUpskillingOperating GuidelinesOperating GuidelinesPortfolio ManagementPortfolio ManagementBudget and Resource ManagementBudget and Resource ManagementStrategy1Automation OpportunityStrategyConsumer Requirements & Onboarding2Process & UserRequirementsArchitecture & Platform Decisions3Automation PlatformDecisionSolution & Interface Design4Automation WorkflowDesignDelivery & Operations5Automation Delivery &OperationsQuality & Readiness Assurance6Automation ReadinessReviewPublishing & Enablement7Automation Rollout &EnablementMonitoring & Improvement8Automation Monitoring &ImprovementBusiness Opportunities LinePlatform Architecture LineDesign LineDelivery LinePublishing and Adoption LineOperating Model Line

Selected station: Quality & Readiness Assurance

People to involve

Related resources

Outcomes

  • Documented readiness for release and reuse
  • Known gaps and mitigations before release
  • Evidence for governance, compliance, support, and operational approval
  • Reduced risk of issues in production

Journey criteria

Entry criteria

  • The chosen architecture, platform, and implementation style have been validated with the relevant architecture, security, and platform stakeholders.
  • The selected interface provides an appropriate abstraction for consumers.
  • The interface design and exposed capabilities trace back to business value and consumer needs.
  • The interface design follows agreed design standards and conventions.

Exit criteria

  • The chosen architecture, platform, and implementation style have been validated with the relevant architecture, security, and platform stakeholders.
  • The interface design and exposed capabilities trace back to business value and consumer needs.
  • The interface and its capabilities are documented clearly enough for review, audit, and onboarding.
  • The interface design follows agreed design standards and conventions.
  • The interface contract has been validated and tested against functional and non-functional requirements.

This is what success looks like

Use audit and compliance resources to verify that the capability is ready for controlled release and reuse.

  1. Use the audit checklist as a reusable quality checklist for interface contract, documentation, security, performance, and compliance readiness. — API Audit Checklist
  2. Use checklists, linters, and testing tools to verify consistency and conformance with standards.
  3. Collaborate with governance teams and domain experts to ensure the capability is ready for production.

Metro lines

Design Line

Focuses on solution and interface design principles that can be used across APIs, integrations, automations, data products, and other implementation styles.

Review station resources

Browse the resources selected for Automation Readiness Review; the summary above explains how they support this station’s work.

Station resources

Resources for Automation Readiness Review

checklist

API Audit Checklist

A lifecycle-based checklist to verify API readiness across design, delivery, publishing, and compliance using defined audit criteria and evidence.

Outcomes

  • Shared understanding of the purpose and use of API Audit Checklist
  • A consistent approach to applying API Audit Checklist
  • Improved application of the related practices

How it works

  1. Use the API Audit Checklist to ensure the API design meets functional and non-functional requirements, including security, performance, and compliance.
  2. Conduct audits to assess lifecycle coverage and verify that the API meets business, design, and operational standards.
  3. Ensure that documentation, security models, gateway configuration, and legal requirements are clearly defined, validated, and supported by evidence.

Relevant cycles

API Productization Cycle

The API-focused APIOps Cycles journey for productizing, designing, delivering, publishing, and improving APIs.

Automation Cycle

A cycle for identifying, designing, delivering, enabling, and improving automation opportunities.