I bring together software engineering, enterprise systems analysis, and Agile delivery to help teams make work visible and coordinate predictable releases. Today, I coordinate concurrent Scrum and Kanban teams delivering healthcare analytics across the US, Nepal, and India—grounded in SDLC rigor, proactive RAID control, and CAB release readiness.
My career is structured like a continuous delivery pipeline—each discipline eliminates handoff blind spots in the next. Click any stage to inspect:
Healthcare Analytics • SAFe SASM & POPM
I bring together software engineering roots, enterprise systems analysis, and Agile leadership to make distributed delivery across US, Nepal, and India predictable.
Having built custom ERP software and integrated APIs (IRD Nepal, eSewa) in C#/.NET, I translate architectural constraints, technical debt, and integration risks into honest executive trade-offs.
Translating individual 8h/day availability into committed story points across US, Nepal & India calendars—accounting for national holidays (Dashain, Thanksgiving), PTO, and 75% focus factor buffers.
Interactive queueing simulation demonstrating the mathematical trade-off between strict WIP limits and multitasking drag (hypothetical model):
Coached an active healthcare analytics engineering team from rigid sprint batching into a continuous flow-based Kanban model—eliminating artificial sprint-end bottlenecks without interrupting release cadence.
Designed inclusive ceremony cadences, asynchronous decision logs, and explicit blocker escalation protocols so US product leaders and Nepal/India engineering squads never lose 24 hours waiting on clarity.
Cotiviti Nepal / Infinite Computer Solutions • PM II (Transitioned 16 Feb 2024)
InfoDevelopers Pvt. Ltd. • Associate Team Lead (Business/System Analyst)
Perfect Active Solutions • CodeBee Tech • Kantipur ITINK
+ Facilitation Skills (Great Team Leaders) • Software PM Foundations.
Available for senior Agile Project Management roles, cross-border delivery leadership, and enterprise Agile transformation advisory.
Most project handoffs fail in the translation layer between business ambition, system architecture, and sprint execution. Because I have worked inside all three roles over the past decade, I close those gaps natively.
Having written production C#/.NET code, designed relational schemas, and debugged third-party API integrations, I understand why estimates slip and why technical debt compounds.
Three years leading system analysis for banking and national investment institutions taught me that downstream coding bottlenecks usually originate as upstream requirement ambiguity.
Leading concurrent Scrum and Kanban teams across the US, Nepal, and India requires more than running ceremonies—it requires building telemetry and trust across time zones.
High resource utilization often disguises slow value delivery. Use the interactive simulator below to explore how I use Work-in-Progress (WIP) constraints and blocker resolution to govern cycle time and release predictability.
Story points completed mean nothing if the release fails to solve the stakeholder's problem or breaks downstream systems. I align backlog prioritization directly with measurable business outcomes.
A team loaded at 100% individual capacity has zero buffer for unexpected complexity. I optimize for the speed of work moving across the board, not keeping every calendar slot packed.
Bad news does not improve with age. I build psychological safety and structured RAID logs so teams surface blockers weeks before a deadline rather than reporting misses in the sprint review.
AI accelerates code generation and documentation, which shifts the bottleneck toward requirements clarity, code review, and QA validation. Delivery management must evolve accordingly.
A structured editorial framework for upcoming field notes drawing from cross-border healthcare delivery, systems analysis, and practical AI integration.
Exploring how AI-assisted development compresses coding time while increasing pressure on upstream systems analysis, PR review queues, and regression testing.
Why historical flow metrics (cycle time scatterplots and throughput stability) often give executives better release confidence than hours spent debating Fibonacci numbers.
Practical playbooks for eliminating the 24-hour ping-pong delay across 10+ hour time-zone gaps through structured specification handoffs and decision logs.