Agile Transformation at CrossOver Nepal

Situation

When I joined CrossOver Nepal as Operations Manager, technical operations were being run reactively. Development, Support, and Sales/Marketing operated as separate silos with no shared cadence — incidents were fixed one at a time with no process for catching recurring patterns, and infrastructure changes were made without a consistent review process. The result was firefighting: the same categories of incidents kept resurfacing because nobody owned looking at the pattern behind them.

What I Did

• 1.Introduced a shared sprint cadence across Development, Support, and Sales/Marketing, so all three functions planned and reviewed work on the same rhythm instead of independently.
• 2.Established root-cause analysis as a mandatory step after any significant incident, rather than treating a fix as 'done' once the symptom was resolved.
• 3.Brought basic DevOps practices into the infrastructure workflow — consistent monitoring, backup verification, and a defined change process for system updates.
• 4.Set up regular reporting on KPIs and system performance for senior leadership, replacing ad hoc updates with a consistent, trusted source of truth.
• 5.Renegotiated vendor contracts and SLAs where the existing terms weren't matching actual usage or risk, to reduce cost without compromising reliability.

Results

Cross-functional teams began operating on a unified cadence rather than working at cross purposes. Recurring incidents dropped as root-cause analysis became routine rather than exceptional, and system availability and performance improved measurably across IT environments. Leadership gained a reliable, ongoing view into operational health instead of hearing about problems only when they became urgent.