As part of my collaborations with Atomic Consulting and Reverse Studio, I have followed and coordinated projects for organisations operating, among others, in the university, healthcare, public, corporate and non-profit sectors.

For projects born from these collaborations the professional relationship was with the companies, not with their clients. All end clients remain anonymous: I indicate only the sector or the kind of organisation.

  • University and training
  • Healthcare
  • Public Administration
  • Corporate
  • National associations and organisations

University and training

Project Management for universities and training organisations

As part of a professional collaboration · anonymous client

Need

Managing change and evolution requests over time, keeping priorities clear, progress under control and releases reliable.

My role and responsibilities

Project Manager, point of connection between the client and the development and design team, with direct technical work when needed.

  • Setting priorities and planning activities
  • Constant alignment between client, developers and designers
  • Validation of the work before each release
  • Continuity of support after release

Activities carried out

  • Requirements gathering and analysis with the client
  • Turning requests into defined tasks ordered by priority
  • Coordination between client, developers and designers
  • Progress monitoring and resolution of critical issues
  • Validation and release
  • Follow-up support and enhancements

Method

  1. Request
  2. Analysis
  3. Task
  4. Development
  5. Check
  6. Release
  7. Support

Quality outcome

A single, orderly channel between client and technical team, with a repeatable path from request to release and continuity in support and enhancements.

Healthcare and Public Administration

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

As part of a professional collaboration · anonymous client

Need

Carrying projects forward with many stakeholders, collecting and ordering requests and ensuring continuity between development, release and support.

My role and responsibilities

Technical Project Manager, with end-to-end project management: from discussion with the contacts to release and subsequent support.

  • Relationship with the client's contacts and management of their requests
  • Coordination of different skills: development, design and suppliers
  • Continuity between development, release and support

Activities carried out

  • Dialogue with contacts and stakeholder management
  • Gathering, analysis and prioritisation of requests
  • Multidisciplinary coordination of developers, designers and suppliers
  • Release planning and management
  • Technical support and full stack development when needed
  • Support and evolutionary maintenance

Method

  1. Request
  2. Analysis
  3. Task
  4. Development
  5. Check
  6. Release
  7. Support

Quality outcome

A single point of contact between the organisation, the technical team and the suppliers, with requests handled in a tracked way and ongoing support after going live.

Security and governance

Cybersecurity and governance of web ecosystems

As part of a professional collaboration · anonymous client

Need

Having a clear picture of the technical and security status of the sites, understanding who was responsible for what between client and suppliers, and getting oriented with respect to NIS2 requirements.

My role and responsibilities

Technical Consultant for security and governance: analysis of the state of the sites and support for the client's decisions.

  • Reconstruction of a complete and reliable technical picture
  • Identification of critical issues and intervention priorities
  • Proposal of operational recommendations and a clear allocation of responsibilities

Activities carried out

  • Technical inventory of the sites: WordPress and PHP versions, plugins and themes in use
  • Check of application security and Wordfence configuration
  • Review of backups, hosting and multi-factor authentication (MFA)
  • Identification of critical issues and intervention priorities
  • Mapping of responsibilities between client and suppliers
  • Support analysis with respect to the NIS2 directive
  • Operational recommendations for the client

Method

  1. Assessment
  2. Analysis
  3. Critical issues
  4. Responsibilities
  5. Recommendations

Quality outcome

A clear picture of the state of the sites and of the critical issues, more clearly defined responsibilities between client and suppliers, and a set of operational recommendations to start from.

Analysis and technical support activities: this was neither a formal audit nor a compliance certification.

Professional website

Technical management and optimisation of a professional website

Technical management engagement · anonymous client

Need

Entrusting the technical management of the site to a single person, from domain and DNS to security, from performance to backups, and solving problems when they arise.

My role and responsibilities

Single technical point of contact, with full management of the technical side of the site.

  • Site security and continuity
  • Performance and technical SEO
  • Technical problem solving

Activities carried out

  • Securing WordPress and updates
  • Domain and DNS record management
  • Technical SEO and performance optimisation
  • Backup configuration and verification
  • Hosting and infrastructure management
  • Diagnosis and resolution of technical issues

Method

  1. Analysis
  2. Priorities
  3. Interventions
  4. Check
  5. Maintenance

Quality outcome

A single point of contact for the entire technical side, able to intervene at every level: from DNS to hosting, from code to security.

Own product

MeriPacSuite: a suite of online management systems, from idea to release

Own project, linked to MeriPac.it

Need

To offer different sectors vertical tools, designed for their daily work, without multiplying development and maintenance effort.

My role and responsibilities

Design, full stack development and release management: from the technical structure to going live.

  • Architecture and technical choices
  • Security and data protection
  • Releases and maintenance over time

Activities carried out

  • Analysis of the workflows of each department
  • Architecture with a core shared by all the management systems
  • Full stack development in PHP, JavaScript and MySQL
  • Security: two-factor authentication, HTTP security headers and consent log
  • Integrations with external services such as Google and payment systems
  • Versioned releases, changelog and evolutionary maintenance

Method

  1. Need
  2. Analysis
  3. Requirements
  4. Development
  5. Check
  6. Release
  7. Evolution

Quality outcome

Five online management systems and a sixth in progress on the same technical base, developed and maintained with a documented release process.

Let's work together

Do you have a project with similar needs?

Tell me about your context: let's work out together whether and how I can help you, as a Technical Project Manager or as an external consultant.