Skip to content

Project Management

Abstract illustration of a project timeline, milestones and task cards running from discovery to maintenance

Project lead and team captain for AI projects

I am Yunus Sevğane — a project manager with a software engineering background, and I want to work as a project lead / team captain on artificial intelligence (AI) projects. Since 2014 I have run team and project management; along the way more than 200 corporate websites, over 10 mobile apps and more than 3 marketplace integrations were delivered. I have worked in AI agent processes, LLM RAG and LLM fine-tuning, and I use my ISO/IEC 42001:2023 lead auditor training as a framework for AI governance.

The position I am looking for

Roles I am open to: Head of AI, AI Program Director and CTO-level remote C-level positions. I am not saying I hold these titles — I am saying which roles I am looking for; my experience is on the Résumé page. I have worked remotely on projects in Canada, Dubai (UAE) and Germany; see the FAQ for more.

Which projects do I manage?

Process: discovery, plan, delivery, handover, maintenance

  1. Discovery: I listen to the goal, the users, the existing systems and the constraints, and I write down what will not be done as well.
  2. Plan: scope, stages, schedule, budget frame and risks go into a single plan; ambiguous items are discussed up front.
  3. Delivery: I split the work into short cycles; at the end of each you see a working result and can correct course early.
  4. Handover: acceptance criteria are written in advance, so handover is a checklist, not a surprise; usage guidance and a handover document are provided.
  5. Maintenance: we set up a sustainable routine for post-launch updates, security and improvement.

How I run AI programs

  • Pilot first: I write the goal and the success criterion, start with a small pilot, measure the outcome, then expand.
  • Governance from day one: purpose, owner, data source, access and monitoring are defined up front through an ISO/IEC 42001 lens.
  • Data privacy and authorization: written into the plan in the first phase.
  • Team building: I identify the roles needed (data, engineering, product, security) and build the team with you.
  • Decision records: model, data and scope decisions are written with their reasoning, so leadership and the technical team look at the same document.

Methods

  • Agile (Scrum) practice: short sprints, a prioritized backlog, a demo and feedback at sprint end.
  • Scope management: change requests are taken in writing and decided with their impact on schedule and budget stated.
  • Budget and time tracking: planned versus actual is compared regularly; deviations are discussed before they grow.
  • Risk management: risks are recorded with an owner and a mitigation.
  • Team and supplier coordination: I am the single point of contact across developers, designers, testers and external suppliers.
  • Remote work: written and recorded communication, a shared task board and a meeting rhythm that suits different time zones.

Technical depth

Because I know frontend, backend, DevOps and AI processes, I can question a team's estimates and reach the right technical decision quickly. I have completed lead auditor training in ISO/IEC 27001:2022, 42001:2023, 9001:2015 and 20000-1:2018. This page is not a certification claim on behalf of an organization; it describes how I work.

How do we start?

The first step is a short intro call: I listen to the goal and expectations, then turn scope, schedule and deliverables into a written plan. See How I Work for more detail, or Projects for the kinds of work I have done.

To book an intro call: use the contact page or write on WhatsApp (+90 531 679 10 14). See also How I Work and the FAQ.