Xoxoday Plum implements system changes through a governed, multi-stage methodology covering formal request intake, impact assessment, agile development, rigorous testing, staged deployment, and post-rollout review to ensure security, compliance, and minimal disruption to your organisation’s operations.
Change Request and Impact Assessment
Every change to Xoxoday Plum begins with a formal request submitted through the support portal, via Customer Success Managers, or through account management. Each request is evaluated against business value, security posture, compliance requirements, technical dependencies, and potential operational risk before any work begins. This structured intake prevents ad-hoc changes from reaching production and ensures every modification is justified against your organisation’s business-criticality and risk appetite.Planning and Prioritisation
Approved changes are slotted into sprint backlogs or scheduled release cycles based on urgency and impact. Xoxoday Plum prioritises requests using a framework that weighs business impact, customer need, technical feasibility, and product roadmap alignment. Clients receive proactive communication about planned changes so internal stakeholders—such as HR teams operating on Darwinbox or SAP SuccessFactors—can coordinate testing and approvals well in advance.Development and Testing
Development follows Agile methodology combined with CI/CD pipelines, enabling frequent, incremental, and high-quality releases. Before any change reaches staging, it passes through unit testing, regression testing, InfoSec reviews, and User Acceptance Testing (UAT). Xoxoday Plum applies a “test early, test often” principle to catch defects at the earliest possible stage, reducing downstream risk significantly. For example, a change to the rewards catalogue integration with Workday or Microsoft Teams undergoes the full testing cycle—including security checks aligned with ISO 27001 and SOC 2 Type II controls—before it is considered deployment-ready.Staged Deployment and Rollback
Xoxoday Plum uses a phased rollout model: sandbox → staging → production. Each environment acts as a validation gate, ensuring the change behaves as expected before wider exposure. Automated monitoring is active throughout deployment to detect anomalies in real time. If an issue surfaces, rollback procedures are triggered immediately to protect your organisation from extended downtime. This approach mirrors blue/green deployment best practices, keeping platform availability high during even significant system updates.Post-Implementation Review and Continuous Improvement
Following every deployment, Xoxoday Plum captures performance metrics and customer feedback to confirm that the change delivered its intended outcome. Release notes and update communications are shared proactively, giving your teams full visibility into what changed and why. Learnings from each cycle feed directly into future planning, making the change management process continuously more effective over time. Learn more: [Xoxoday Plum Help Centre — Process](How does Xoxoday Plum handle data security and compliance?
Understand the security controls, certifications, and compliance frameworks—including ISO 27001 and SOC 2 Type II—that govern the Xoxoday Plum platform.
What is Xoxoday Plum's incident response process?
Learn how Xoxoday Plum detects, escalates, and resolves platform incidents to minimise impact on your organisation’s operations.