D24*7 Remote Deposit Capture Modernization

Modernizing a business-critical Remote Deposit Capture platform and transforming delivery from quarterly releases to a two-week cadence.

Legacy ModernizationRemote Deposit CaptureDevOpsProgram Leadership

Organization: UST
Role: Engineering Program Manager
Industry: Financial Services
Duration: March 2022 onward

Objective

Deluxe's Deposit 24/7 (D247) supports Remote Deposit Capture for financial institutions and businesses. The modernization program replaced an end-of-life legacy foundation with a modular platform while maintaining service continuity and familiar customer workflows.

As Engineering Program Manager, I led delivery across a program of approximately 120 FTE, with direct ownership of Deposit, Branch Capture, and DevOps including ArgoCD. The program combined application modernization with delivery transformation, reducing the release cycle from approximately three months to two weeks.

Business Challenge

Legacy risk: Core technology was approaching end-of-life and constrained future development.
Limited documentation: Critical behavior and dependencies relied heavily on institutional knowledge.
Slow delivery: Large releases required approximately three months of coordinated development, testing, and deployment.
Tight coupling: Changes in one module increased regression scope and cross-team coordination.
Customer continuity: Modernization had to preserve trusted workflows for existing users.
Operational risk: A business-critical financial-services platform required controlled migration without service disruption.

Context

Product scope: Deposit, Payments, and Branch Capture capabilities within the Remote Deposit Capture portfolio.
Delivery scope: Application architecture, frontend, APIs, microservices, runtime, CI/CD, quality automation, and security controls.
Direct ownership: Deposit, Branch Capture, and the DevOps / ArgoCD workstream.
Program scale: Approximately 120 FTE at peak across engineering, quality, platform, security, product, and leadership stakeholders.
Delivery objective: Move from large quarterly releases toward smaller, repeatable, independently deployable increments.

Responsibilities

Program governance: Connected roadmap, scope, milestones, resources, dependencies, risks, quality, and release readiness.
Release leadership: Planned and governed approximately 6–8 major releases from engineering readiness through production deployment.
Workstream delivery: Led Deposit and Branch Capture modernization and coordinated their cross-platform dependencies.
DevOps transformation: Owned the delivery model around Jenkins, Kubernetes, and ArgoCD.
Resource planning: Managed capacity, skill alignment, legacy expertise, and workstream allocation across a large program.
Risk management: Maintained critical-path visibility and escalated technology, dependency, quality, and production-readiness risks.
Stakeholder alignment: Coordinated client leadership, product, engineering, quality, platform, security, and operations teams.
Executive reporting: Communicated progress, decisions, trade-offs, risks, and outcome metrics.

Execution

Discovery and Transition

Mapped legacy behavior, business rules, interfaces, and hidden dependencies before replacement.
Engaged subject-matter experts to recover undocumented knowledge and support transition planning.
Sequenced modernization to reduce end-of-life exposure while maintaining production stability.

Architecture Modernization

Introduced React.js Micro Frontends to modernize experiences in manageable increments.
Used APIs and microservices to separate business capabilities and reduce cross-module impact.
Adopted Kubernetes as the runtime and orchestration foundation for containerized services.
Preserved familiar user journeys where change did not create clear customer value.

Delivery Transformation

Established Jenkins-based continuous integration and ArgoCD-based deployment automation.
Integrated TOSCA regression automation, SonarQube quality analysis, and Checkmarx security scanning.
Reduced release scope through modular delivery and stronger component isolation.
Shifted delivery from approximately three-month release cycles to a two-week cadence.

Governance and Readiness

Translated the roadmap into release-level scope, milestones, ownership, and acceptance criteria.
Tracked planned versus delivered work, spillover, scope change, capacity, and dependency-driven variance.
Governed engineering, QA, automation, environment, security, defect, business, and production readiness.
Used risk and dependency reviews to manage downstream impact rather than report schedule variance alone.

Outcomes

Faster releases: Reduced the release cycle from approximately three months to two weeks, a roughly 6× improvement in cadence.
Modern architecture: Replaced tightly coupled legacy patterns with Micro Frontends, APIs, and microservices.
More independent delivery: Improved component isolation reduced cross-module coordination and regression exposure.
Automated deployment: Jenkins, Kubernetes, and ArgoCD created a more repeatable and visible path to production.
Integrated controls: TOSCA, SonarQube, and Checkmarx embedded testing, quality, and security into delivery.
Improved responsiveness: The modernized platform provided a stronger foundation for performance and scalability.
Program delivery: Coordinated approximately 120 FTE and delivered 6–8 major releases across the modernization lifecycle.

Lessons Learned

Legacy modernization is a knowledge challenge: Recovering undocumented behavior is as important as replacing technology.
Architecture must improve delivery: Microservices and Micro Frontends create value when they enable smaller, safer releases.
Modernization should protect customer familiarity: Technical change does not require unnecessary disruption to established workflows.
DevOps is a platform capability: Architecture, automation, quality, security, and deployment must evolve together.
Governance should focus on outcomes: Scope, capacity, dependencies, quality, and risk should connect directly to release readiness and business value.
Incremental transformation reduces risk: Sequenced modernization supports learning while protecting production continuity.

Objective

Business Challenge

Legacy risk: Core technology was approaching end-of-life and constrained future development.

Limited documentation: Critical behavior and dependencies relied heavily on institutional knowledge.

Slow delivery: Large releases required approximately three months of coordinated development, testing, and deployment.

Tight coupling: Changes in one module increased regression scope and cross-team coordination.

Customer continuity: Modernization had to preserve trusted workflows for existing users.

Operational risk: A business-critical financial-services platform required controlled migration without service disruption.

Context

Product scope: Deposit, Payments, and Branch Capture capabilities within the Remote Deposit Capture portfolio.

Delivery scope: Application architecture, frontend, APIs, microservices, runtime, CI/CD, quality automation, and security controls.

Direct ownership: Deposit, Branch Capture, and the DevOps / ArgoCD workstream.

Program scale: Approximately 120 FTE at peak across engineering, quality, platform, security, product, and leadership stakeholders.

Delivery objective: Move from large quarterly releases toward smaller, repeatable, independently deployable increments.

Responsibilities

Program governance: Connected roadmap, scope, milestones, resources, dependencies, risks, quality, and release readiness.

Release leadership: Planned and governed approximately 6–8 major releases from engineering readiness through production deployment.

Workstream delivery: Led Deposit and Branch Capture modernization and coordinated their cross-platform dependencies.

DevOps transformation: Owned the delivery model around Jenkins, Kubernetes, and ArgoCD.

Resource planning: Managed capacity, skill alignment, legacy expertise, and workstream allocation across a large program.

Risk management: Maintained critical-path visibility and escalated technology, dependency, quality, and production-readiness risks.

Stakeholder alignment: Coordinated client leadership, product, engineering, quality, platform, security, and operations teams.

Executive reporting: Communicated progress, decisions, trade-offs, risks, and outcome metrics.

Execution

Discovery and Transition

Mapped legacy behavior, business rules, interfaces, and hidden dependencies before replacement.
Engaged subject-matter experts to recover undocumented knowledge and support transition planning.
Sequenced modernization to reduce end-of-life exposure while maintaining production stability.

Architecture Modernization

Introduced React.js Micro Frontends to modernize experiences in manageable increments.
Used APIs and microservices to separate business capabilities and reduce cross-module impact.
Adopted Kubernetes as the runtime and orchestration foundation for containerized services.
Preserved familiar user journeys where change did not create clear customer value.

Delivery Transformation

Established Jenkins-based continuous integration and ArgoCD-based deployment automation.
Integrated TOSCA regression automation, SonarQube quality analysis, and Checkmarx security scanning.
Reduced release scope through modular delivery and stronger component isolation.
Shifted delivery from approximately three-month release cycles to a two-week cadence.

Governance and Readiness

Translated the roadmap into release-level scope, milestones, ownership, and acceptance criteria.
Tracked planned versus delivered work, spillover, scope change, capacity, and dependency-driven variance.
Governed engineering, QA, automation, environment, security, defect, business, and production readiness.
Used risk and dependency reviews to manage downstream impact rather than report schedule variance alone.

Outcomes

Faster releases: Reduced the release cycle from approximately three months to two weeks, a roughly 6× improvement in cadence.

Modern architecture: Replaced tightly coupled legacy patterns with Micro Frontends, APIs, and microservices.

More independent delivery: Improved component isolation reduced cross-module coordination and regression exposure.

Automated deployment: Jenkins, Kubernetes, and ArgoCD created a more repeatable and visible path to production.

Integrated controls: TOSCA, SonarQube, and Checkmarx embedded testing, quality, and security into delivery.

Improved responsiveness: The modernized platform provided a stronger foundation for performance and scalability.

Program delivery: Coordinated approximately 120 FTE and delivered 6–8 major releases across the modernization lifecycle.

Lessons Learned

Legacy modernization is a knowledge challenge: Recovering undocumented behavior is as important as replacing technology.

Architecture must improve delivery: Microservices and Micro Frontends create value when they enable smaller, safer releases.

Modernization should protect customer familiarity: Technical change does not require unnecessary disruption to established workflows.

DevOps is a platform capability: Architecture, automation, quality, security, and deployment must evolve together.

Governance should focus on outcomes: Scope, capacity, dependencies, quality, and risk should connect directly to release readiness and business value.

Incremental transformation reduces risk: Sequenced modernization supports learning while protecting production continuity.