Sprint Release Flow for Client Feature Requests

Overview

CAMS development operates on a sprint cycle model, with new work typically delivered in two-week sprints. This structure allows us to manage priorities, release features incrementally, and ensure regular deployment opportunities.

This article is intended to help clients understand how new features and enhancements are released through the CAMS platform. By outlining the standard release flow and approximate timelines, we aim to provide clarity and set realistic expectations around delivery and testing windows.

The CAMS release process ensures that all updates undergo structured testing across three environments before being made available in production.

---

Understanding the Release Flow

You can also refer to the simplified sprint release flowchart below for a visual summary of these steps.

When you request a new feature or fix, it progresses through the following stages:

1. Development Environment (3–4 working days)

• The CAMS development team implements and internally tests the feature.

• Internal QA checks are performed to validate stability and functionality.

2. Stage Environment (3–4 working days)

• The feature is promoted to the Stage environment.

• A dedicated QA person tests it in a controlled setting.

• Any issues raised are addressed before progressing further.

3. Live Environment

• The feature is released to the Live environment for client use.

• UAT (User Acceptance Testing) is conducted with your team or designated testers.

• Once feedback is addressed, the feature is marked as complete and supported.

---

What This Means for You

• The full cycle from development to live generally takes 6–8 business days, provided no major issues arise.

• UAT is a collaborative phase — timely feedback helps avoid delays.

• If a request involves multiple dependencies or touches sensitive workflows, additional time may be required.

We recommend planning ahead for UAT, especially if the feature impacts reporting, workflows, or external integrations.

---

Managing Expectations

• Not all features are released immediately after development. Quality assurance and UAT are required steps to ensure reliability.

• Urgent fixes may follow a different expedited path, but standard enhancements follow this flow.

• Your account contact or project lead will coordinate timelines and communication.

---

Need Help?

Still have questions about timelines or release status?

• Use the CAMS web support widget

• Or contact [e-mail]

Understanding the release flow helps align your team’s expectations and ensures smooth rollout and adoption of new features.