Connected care.

01 / Context

The problem

An Exeter charity needed a mental-health application shaped around its requirements. Delivery meant bringing together client needs, a team of six and a system that could be deployed and maintained.

02 / Responsibility

My contribution

I led a team of six, translated a charity’s requirements into a Django mental-health application, and delivered its cloud deployment and migration.

03 / Approach

The decisions

I led the team and translated requirements into features, with Django as the application framework. The system was first deployed on Google Cloud and later migrated to DigitalOcean. Service continuity was the migration constraint: the CV records a zero-downtime move. The detailed cutover procedure is not part of the available public record.

1. 01

   Understand

   Translate the charity’s requirements into features.

2. 02

   Deliver

   Build the Django application and deploy it on Google Cloud.

3. 03

   Move, keep serving

   Migrate to DigitalOcean with zero downtime, as recorded in the CV.

04 / Result

The outcome

The team built and deployed the application. I migrated it from Google Cloud to DigitalOcean with zero downtime, combining technical delivery with team leadership.