Per chi è

Web agency e software house

Hai sviluppatori, ma non un Project Manager tecnico interno: faccio da ponte tra chi decide e chi sviluppa, con la competenza per entrare nel merito tecnico.

PMI con progetti in corso

Hai un progetto software o web con fornitori esterni e ti serve un referente unico per la parte tecnica, che coordini il lavoro fino al rilascio.

External Project Manager

It is a useful solution when:

Abroad this arrangement is called Fractional IT Project Manager.

  • you have several projects running at the same time;
  • you have developers, but no internal technical Project Manager;
  • you work with several suppliers and need someone to coordinate them;
  • you need a single point of contact for the technical side;
  • it is not yet the right time to hire a full-time figure.
Let's talk

Services

Di cosa mi occupo.

IT Project Management

I take charge of the project and carry it to release, keeping objectives, people and activities aligned.

  • Requirements gathering and analysis
  • Activity planning
  • Team coordination
  • Stakeholder management
  • Progress monitoring
  • Delivery
  • Vendor management

Technical Project Management

I act as a bridge between those who decide and those who develop, with the skills to get into the technical detail.

  • Link between business and technical team
  • Software and web projects
  • Technical analysis
  • Decision support
  • Validation
  • Release management

Profile

I manage digital projects with the expertise of someone who has also built them.

I come from full stack development, and this changes the way I run a project: I am not a purely managerial Project Manager. I can talk directly with developers, system administrators, designers, suppliers and company contacts, get into the substance of technical choices and identify critical issues in good time.

Computer Engineer, Cybersecurity curriculum Over 15 years in the IT sector Project Manager and Full Stack Developer Developer of MeriPacSuite Teacher of Computer Science, TPSIT and Systems and Networks

Selected project experiences

Projects followed from requirement to release.

A selection of project management, delivery and security experiences, described anonymously: for each one I state the sector, my role, the activities carried out and the method, never the client's name.

University and training

Project Management for universities and training organisations

As part of a professional collaboration · anonymous client

Requirements gathering, requests turned into tasks and coordination between client, developers and designers, through to release and support.

  • Project Management
  • Stakeholder Management
  • Software Delivery
Read the experience

Healthcare and Public Administration

Management of digital projects in the healthcare sector and for Public Administration

As part of a professional collaboration · anonymous client

End-to-end management of projects with multiple stakeholders: requirements gathering, multidisciplinary coordination, delivery and technical support.

  • Technical Project Management
  • Stakeholder Management
  • Software Delivery
  • Full Stack Development
Read the experience

Method

From requirement to release.

Every project follows the same path, from the first requirement to support after release. Knowing the technical work of each phase allows me to anticipate problems, instead of discovering them at the end of the project.

Phase 1 Understand

  1. Need

    I listen to the objective and the context: what is really needed, by whom and why.

  2. Analysis

    I assess technical feasibility, constraints and impact on existing systems.

  3. Requirements

    I translate the need into clear, verifiable requirements, shared with the client.

Phase 2 Organise and build

  1. Priorities and tasks

    I break the work down into tasks, set priorities and plan the phases.

  2. Coordination

    I align the technical team, designers, suppliers and company contacts.

  3. Development

    I follow development closely and, when needed, contribute directly.

Phase 3 Deliver and evolve

  1. Check

    I check and validate the result against the requirements before release.

  2. Release

    I plan and coordinate the go-live, reducing risks.

  3. Support and evolution

    I follow the project after release and gather new requirements.

Evolution reopens the cycle: new requirements start again from the first step, with the same method.

Contact

Tell me about your project or the collaboration you have in mind.

Choose the type of enquiry.
Enter your name.
Enter a valid email address.
Enter a subject.
Write a message.
Privacy consent is required to send the request.