Skip to content

Phase 4 – Delivery and Factory Runs

This document shows how actual delivery works using Factory, platforms, and squads. It is written for architects, engineers, delivery leads, and project managers managing Factory-based delivery.

Phase 4 is where the Factory and Squads deliver real value. This phase demonstrates the delivery rhythm, Factory usage, platform integration, and communication patterns that ensure successful delivery.

Note

Delivery success depends on clear communication, regular feedback, and proper use of Factory and platform capabilities. Invest in these areas to ensure smooth delivery.

Objectives of Phase 4

The objectives of Phase 4 are to:

  • Deliver Working Software - Generate and deploy microservices using Factory
  • Integrate Platforms - Integrate Identity, Audit, and Config platforms
  • Maintain Quality - Ensure code quality through Factory QA agents and human review
  • Communicate Progress - Keep stakeholders informed of progress and blockers
  • Handle Changes - Manage scope changes and new requirements

Delivery Rhythm and Cadence

Weekly/Bi-Weekly Cycles

Typical Sprint Cycle (2 weeks):

  1. Sprint Planning (Day 1)
  2. Review backlog and priorities
  3. Plan Factory runs for sprint

  4. Assign work to Squad

  5. Factory Runs (Days 1-10)

  6. Vision/Planning agents refine requirements
  7. Architect agents design bounded contexts
  8. Engineering agents generate code

  9. QA agents validate quality

  10. Review & Feedback (Days 5-10)

  11. Code review and feedback
  12. Architecture review

  13. Customer feedback sessions

  14. Deploy to Dev/Staging (Days 8-10)

  15. Deploy generated services
  16. Integration testing

  17. Platform integration validation

  18. Sprint Review (Day 10)

  19. Demo deliverables
  20. Gather feedback
  21. Plan next sprint

Squad Output Expectations

Starter SaaS Squad: - 2-3 microservices per month - Complete with tests, pipelines, documentation - Integration with platforms - Deployable to dev/staging

See: Squads Business Model for squad capacity.

See: Product Portfolio - Squads for squad details.

Using the Factory in Sprints

Sprint Planning with Factory

Use Vision/Planning Agents: - Refine user stories and epics - Break down features into bounded contexts - Prioritize work based on business value - Create product roadmap

See: Vision & Planning Agents for agent details.

Architecture Design

Use Architect Agents: - Design bounded contexts and service boundaries - Define APIs and event contracts - Create ADRs for key decisions - Select templates and libraries

See: Architect Agents for agent details.

Code Generation

Use Engineering Agents: - Generate microservices from templates - Implement domain logic - Create tests and pipelines - Generate documentation

See: Engineering Agents for agent details.

See: Getting Started with Factory for Factory usage.

Quality Validation

Use QA Agents: - Review generated code - Validate architecture compliance - Check test coverage - Identify issues and improvements

See: QA Agents for agent details.

Example: Agent Marketplace Microservice

Factory Run Flow:

  1. Vision Agent - Refines "Agent Marketplace" epic into user stories
  2. Architect Agent - Designs bounded context, APIs, events
  3. Engineering Agent - Generates microservice (Api, Application, Domain, Infrastructure)
  4. QA Agent - Reviews code, validates tests, checks compliance
  5. Human Review - Architect and customer review before merge
  6. Deploy - Deploy to dev environment for testing

Integrating Platforms

Identity Platform Integration

Integration Steps: 1. Provision Identity Platform tenant 2. Configure OAuth2/OIDC clients 3. Generate microservices with Identity integration 4. Test authentication flows 5. Deploy and validate

See: Identity Platform API Overview for API details.

See: Getting Started with Platforms for platform integration.

Audit Platform Integration

Integration Steps: 1. Provision Audit Platform tenant 2. Configure audit event schemas 3. Generate microservices with Audit integration 4. Test audit event emission 5. Validate audit queries

See: Audit Platform API Overview for API details.

Config Platform Integration

Integration Steps: 1. Provision Config Platform tenant 2. Define configuration structure 3. Generate microservices with Config integration 4. Configure feature flags 5. Test configuration retrieval

See: Config Platform API Overview for API details.

Communication and Status Reporting

Weekly Check-In Call

Agenda (30 minutes): - Review progress since last call - Discuss Factory runs completed - Review services created/updated - Identify risks/blockers - Plan next week's work

Status Report Template

Weekly Status Report:

  • Factory Runs Completed: [Number] runs, [Services] generated
  • Services Created/Updated: [List services]
  • Platform Integration: [Status of platform integrations]
  • Deployments: [Deployments to dev/staging]
  • Risks/Blockers: [List any risks or blockers]
  • Next Week Plan: [Planned Factory runs and deliverables]

Communication Channels

  • Slack - Daily async communication
  • Weekly Calls - Synchronous status updates
  • Azure DevOps - Work items, PRs, commits
  • Email - Formal communications, decisions

Handling Scope Changes

Change Request Process

  1. Capture Change - Document change request
  2. Assess Impact - Evaluate impact on scope, timeline, cost
  3. Re-Estimate - Update estimates for Factory runs and deliverables
  4. Update Roadmap - Adjust roadmap and priorities
  5. Get Approval - Get customer approval for change
  6. Update ADR/BDR - Document decision if architecture/business impact

Scope Change Considerations

  • Factory Impact - Additional Factory runs needed?
  • Squad Impact - Does it fit within squad capacity?
  • Timeline Impact - How does it affect timeline?
  • Cost Impact - Additional cost implications?

ADR/BDR for Major Changes

Create ADR if: - Architecture changes required - New patterns or technologies needed - Significant design decisions

Create BDR if: - Business model changes - Pricing or commercial changes - Strategic decisions

See: Decision Records Process for ADR/BDR process.

Important

Scope Control: Don't promise "free scope" just because Factory is fast. Every change has impact—assess it properly, re-estimate, and get approval. Factory accelerates delivery, but it doesn't eliminate the need for proper change management.