Project Manager·Lalitpur
At-risk projects, cross-functional teams, and a habit of shipping anyway. Creating clarity for teams, confidence for clients, and momentum for projects.
Case Studies
Full-lifecycle delivery — from discovery through production release.
Professional CEO Talent Acquisition Platform
When the vendor took the code with them
Healthcare Risk-Transfer Financial Platform
Nine months stalled, ninety days to production
Healthcare CRM
From nine spreadsheets to one source of truth
Healthcare Case-Management Platform
Inheriting the flagship
Legacy Enterprise Claim Management System
Managing sideways on a legacy system
Consumer Video-Portfolio App
A first app for a first-time client
Internal Asset Management System
My first project, and my first escalation
What I bring
The tools, methods, and habits that keep complex projects moving.
Project Delivery
- Agile / Scrum / Kanban
- Sprint & release planning
- Backlog & user story ownership
- Scope / timeline / resource control
Risk & Recovery
- At-risk project takeover
- Stakeholder alignment & negotiation
- Escalation & decision traceability
- UAT coordination & sign-off
Process & Tools
- YouTrack · Jira · Azure DevOps
- KPI dashboards & reporting
- Process design & improvement
- M&S policy & operating procedures
How I navigate a project
Every project has the same three waypoints. The ones that go wrong usually skip one of them. I don't.
Orient
Map the real terrain before touching the plan. Understand what's actually built, what's assumed, and where the undocumented decisions are buried. Projects that skip this step get surprised later — I'd rather be surprised in week one.
Course-set
Lock in a delivery plan that accounts for risk, not just schedule. Re-baseline when reality changes. Escalate early. The goal isn't a plan that looks right — it's one that holds under pressure.
Land it
Execute tightly — sprints, UAT, cross-functional coordination, and production release. I stay in the detail through go-live, because the last mile is where most projects lose altitude.
A project doesn't fail because the technology was hard. It fails because nobody stayed on top of it.