Project Manager | Technical Delivery (Cloud, Data & AI) | Stakeholders, Risk & Governance
I’m a delivery-focused Project Manager / Technical Project Manager (TPM) who helps teams turn complex initiatives into predictable releases.
My background spans client-facing delivery, stakeholder alignment, and governance cadence, with pragmatic technical fluency (cloud/data/AI) to clarify constraints, remove blockers, and improve handover quality.
This GitHub is a project-first portfolio.
-
It is: delivery artefacts, working prototypes, and documentation discipline
-
It isn’t: a second CV or a wall of buzzwords
Delivery planning and execution for a generative‑AI customer service system, from roadmap/decision gates to release and handover.
Highlights
-
Delivery cadence, stakeholder alignment, dependency/risk visibility
-
Privacy-by-design controls (PII handling mindset, audit-ready activity logging)
-
Governance guardrails aligned with GDPR and EU AI Act readiness
-
Metrics-first release readiness (quality checks, telemetry signals, operational handover)
Public-safe artefacts are curated per project. If a repo isn’t public yet, I can share a redacted package on request.
Built a structured submission pack with a delivery roadmap, milestones, assumptions, and audit-ready artefacts to support controlled execution.
Highlights
-
24‑month technical + financial roadmap (decision gates, CAPEX/OPEX assumptions)
-
Governance artefacts: DPIA/risk framing, evidence packs, reporting structure
Tools built to shorten feedback loops and standardize execution.
-
Commercial Kit Generator — turns technical docs into a structured set of client assets (one‑pager, pitch deck, FAQ, datasheet, playbook)
-
NexoCLI — lightweight CLI helpers for repeatable workflows
-
Nexo‑Agents — library of structured agent commands/workflows for CLI usage
-
LLM Prompt Optimizer — provider-aware prompt rewriting app
-
Operational governance & SLA delivery: service ownership mindset, vendor coordination, backlog/cycle-time reduction
-
Process automation products: workflow redesign + internal tooling to improve throughput and follow‑through
-
Quality & compliance discipline: audit readiness, acceptance criteria, traceability and handover
-
Delivery Planning & Control: scope, milestones, dependencies, execution tracking, release readiness
-
Stakeholder Management & Governance: steering-style updates, reporting cadence, decision traceability
-
Risk, Issues & Change: trade-off communication (time/scope/quality), escalation paths, unblock strategy
-
Backlog & Work Management: Jira, GitHub Projects (Projects v2), OpenProject (Community) — familiar with Azure DevOps Boards
-
Documentation & Handover Discipline: structured knowledge bases (Markdown/Confluence), runbook-ready handover, operational checklists
-
Vendor & SLA Governance: service ownership mindset and operational delivery consistency
I don’t use GitHub to claim “architect of everything”; I use it to show how work gets delivered.
Typical tools you’ll see across my projects:
-
Planning & tracking: Jira, GitHub Projects (v2), OpenProject
-
Documentation: Markdown, ADR-style notes, structured handover docs
-
Visual artefacts: Visio, diagrams.net (draw.io), Lucidchart, FreeMind (WBS-style decomposition)
-
Delivery context: cloud/data/AI literacy for technical alignment (not as a pure engineering role)
Short discovery → clear acceptance criteria → execution tracking → governance cadence → release readiness → documentation + handover so the team can operate and evolve the system.
-
LinkedIn: https://www.linkedin.com/in/nsalvacao/
-
Email: nuno.salvacao@gmail.com
-
Location: Lisbon (UTC+0) • Remote-first • Open to hybrid in Portugal
Recommendations and professional references are maintained on LinkedIn (public).



