About PMOVA
PMOVA is a technical project management practice built specifically for deep-tech R&D programs — semiconductor design, artificial intelligence and machine learning, complex engineering systems, and government-funded innovation programs. We are not a generalist PM firm that serves deep-tech as one vertical among many. It is the only context in which we operate.
Founded in Montreal in 2020, PMOVA operates at the intersection of engineering discipline and delivery governance — bringing PM leadership that is technically fluent, governance-rigorous, and calibrated to the delivery constraints of research-intensive organizations.
"To turn complexity into clarity and strategy into success — by providing the governance frameworks, technical judgment, and embedded leadership that enable deep-tech organizations to deliver high-stakes programs with precision."
This means operating inside the delivery team, not above it — and producing governance artifacts that reflect actual program state, not an optimistic interpretation of it.
Technical DNA
The technical foundation of PMOVA's practice is not a methodology applied from the outside. It is an engineering perspective built from the inside — through formal training in microelectronics and electrical engineering before PM practice was formalized.
A PM with an engineering background understands tapeout gates, TRL progression, verification methodology, and hardware/software interface requirements as first-hand technical knowledge — not as vocabulary learned on the job. That difference changes every risk assessment, every milestone definition, and every stakeholder communication.
It also changes how quickly an engagement can become productive. An embedded PM who can read a design review finding, parse a coverage report, and challenge a schedule estimate on technical grounds adds governance value from day one — not after a six-week onboarding to the technical domain.
Founder and Principal PM
Hachem Ben Salem
Founder & Principal Project Manager — PMOVA
15+ years managing semiconductor, AI, and deep-tech R&D programs across academic, government, and industry engagements. Background spans TRL-gated R&D governance, IC design program management, and multi-stakeholder funding consortia across Mitacs, NSERC, and international programs.
Academic training in microelectronics and electrical engineering provides the technical foundation for PM practice in hardware-intensive domains — where the difference between a PM who understands the engineering and one who does not is measurable in schedule recovery time and stakeholder trust.
Delivery Philosophy
Engineering Fluency
Every PM decision is informed by an engineering perspective. We speak the language of your design team, not just your executive layer — which means fewer translation errors between technical state and stakeholder communication, and faster escalation of decisions that actually require escalation.
Embedded, Not Advisory
PMOVA PMs integrate into your delivery team — attending design reviews, sprint retrospectives, and stakeholder briefings as principals, not observers. Governance artifacts are maintained as living documents that reflect actual program state, not assembled before milestone reviews.
Adaptive Methodology
Agile, Waterfall, Lean, or Hybrid — the framework is matched to the program's actual characteristics: research phase, hardware development cycle, regulatory requirements, and funding agency constraints. No one-size-fits-all playbooks applied regardless of context.
Zero-Failure Operating Standard
PMOVA engagements are structured for programs where the cost of delivery failure is consequential — missed tapeout windows, failed funding milestone reports, production model deployment failures. Risk governance is proactive and continuous, not reactive.
Why Generic PM Fails Deep-Tech Programs
The case for technical PM leadership is not a positioning claim. It is a structural argument about what PM knowledge is actually required to govern programs at the frontier of engineering.
Linear Frameworks on Non-Linear Work
Standard PM frameworks assume predictable task decomposition, deterministic durations, and stable requirements. Deep-tech programs — particularly in R&D and semiconductor development — have iterative research cycles, hardware-dependent verification gates, and external dependency timelines that can shift without warning. Applying a linear framework to non-linear work produces governance artifacts that misrepresent actual program state.
PM Without Technical Fluency
A PM who cannot parse a design review finding, a verification coverage report, or a funding agency milestone definition cannot accurately assess whether a program is on track or at risk. The gap between technical state and reported state grows until a milestone review forces a reckoning — at which point recovery options are limited.
Governance as a Compliance Exercise
When governance is treated as a reporting requirement rather than a delivery tool, the artifacts — milestone plans, RAID logs, risk registers — become documents produced for stakeholders rather than instruments used by the team. They lag reality by days or weeks and fail to detect risks before they become schedule events.
PMOVA Operating Model
Every engagement follows the same structural model, regardless of program type or engagement scope.
Stakeholder interviews, existing artifact review, dependency and critical-path mapping, initial risk identification — completed within the first week. Governance framework established by end of week two.
Sprint-level milestone tracking, RAID log maintenance, stakeholder reporting, partner coordination, and risk escalation — managed as standing responsibilities throughout the engagement, not assembled at reporting intervals.
Milestone framework, RAID log, communication plan, decision register, and stakeholder escalation matrix — maintained as living documents, version-controlled, and accessible to all program stakeholders.
Risk escalation triggers are defined at program inception, not identified reactively. Critical-path dependencies are tracked continuously. Blockers are surfaced before they impact milestone gates.
Domains of Expertise
Semiconductor and IC Design
ASIC, FPGA, and SoC programs — tapeout coordination, verification governance, and hardware/software co-design management.
Learn more →AI/ML and Data Science
Model lifecycle coordination, MLOps pipeline governance, and data platform delivery for enterprise and research programs.
Learn more →Grant and Innovation Programs
Mitacs, NSERC, IRAP, and Investissement Québec programs — milestone governance, technical reporting, and partner coordination.
Learn more →Project Management as a Service
Fractional, full-time, and project recovery engagements — senior PM embedded in your team in under two weeks.
Learn more →Montreal and Quebec Delivery
Bilingual PM leadership for Montreal's deep-tech and research-to-commercialization programs, with North American delivery capability.
Learn more →Ready to discuss your program?
Describe your program — technology domain, team structure, delivery challenge, and timeline. We'll assess fit and respond within 48 hours.