VS03 Request to Release

Purpose and Outcomes

The Request to Release value stream delivers software changes from initial request through production deployment. This stream ensures rapid, reliable, and high-quality software delivery through coordinated engineering practices.

Customers and Stakeholders

Primary Customer

Product teams, clients, and end users requiring software changes and features

Key Stakeholders

• Product Mgmt, Engineering, QA, Operations, Architecture

Boundaries

Start Trigger

Feature request or change request approved and prioritized for development

End Trigger

Change deployed to production, validated, and monitored for stability

Typical Duration

1-6 weeks depending on change complexity and release cycle

Owner and Governance Model

• Value Stream Owner: [Name/TBD - Typically CTO or VP Engineering]
• Governance Team: @calab-ai/guild-executive
• Decision Authority: VS Owner for engineering flow; Practice Owners for practice artefacts
• Escalation Path: Leadership Team

Related Practices

• Business Analysis Management
• Solution Eng Management
• Solution Eng Management
• Platform Architecture Management
• Release Management
• Project Mgmt

Value Stream Documentation

• 01 Value Stream Map | 02 Governance & Roles | 03 Metrics | 04 Interfaces | 05 Practice Links

Review Cadence

• VS Performance Review: Weekly (sprint reviews)
• VS Design Review: Quarterly

Change Log