Personal Development Workspace: From Unstructured Requirements to a Hosted HR Web Application

A completed HR software project that transformed unstructured personnel development requirements into a maintainable, tested, and hosted full-stack web application.

Project and problem

The client needed a structured HR application for personnel development. We delivered the Personal Development Workspace, a full-stack web application for the personnel development team and other authorised users. We took the project from an analysis of the existing content and an agreed MVP scope to a hosted application with a defined architecture, data model, basic user and role structures, tests, bug fixes, and technical documentation.

We assessed existing open-source solutions as possible building blocks and chose between reuse, modification, and custom development according to fit. Working closely with the client's personnel development contact kept domain priorities connected to technical decisions. The result was a working first version and a maintainable codebase for continued product development.

What we built and who used it

The MVP brought the frontend, backend, database, and basic user and role structures together in one web application. The client's personnel development contact provided the specialist perspective during delivery. Authorised users worked through the frontend, while the backend handled application logic and the database stored the information covered by the MVP.

The prioritised requirements, architecture, data model, tests, deployment setup, and technical documentation formed the product's supporting foundation. They gave later requirements a clear baseline and made the first version easier to extend.

How the project worked end to end

1. Analyse the starting material. We reviewed the existing content and requirements to identify overlaps, gaps, priorities, and unresolved decisions.
2. Structure and prioritise the needs. We converted unstructured input into clear requirements for the first usable version.
3. Agree the MVP boundary. Together with the client's personnel development contact, we selected the functions that belonged in the first release and separated them from later enhancements.
4. Evaluate reuse against custom development. We assessed existing open-source solutions and decided where reuse, modification, or new development best matched the requirements.
5. Design the technical foundation. We translated the agreed scope into an architecture, data model, and clear boundaries between the frontend, backend, database, and user management.
6. Implement the application. We developed the interface, server-side logic, data layer, and basic user and role structures as one product.
7. Test and correct the first version. We tested the application and fixed issues found during delivery.
8. Deploy and document the system. We deployed the application in the hosting environment and documented the technical foundation for maintenance and further development.

Technical implementation

Full-stack architecture and data model

We separated the user-facing frontend, backend application logic, and persistent data layer. The architecture and data model gave the MVP clear technical boundaries and kept product concepts out of interface code alone.

Users, roles, and authorisation foundation

We implemented basic user and role structures as part of the MVP. They established the first access-control foundation and left room for more detailed permissions as the product developed.

Maintainability, testing, and deployment

We organised the codebase for maintenance and extension. Testing and bug fixing accompanied implementation, followed by deployment in the hosting environment and technical documentation for the handover.

Design principles

We followed three practical principles:

• Define the MVP before expanding the scope. We prioritised the requirements and agreed the first-version boundary with the client's personnel development contact.
• Reuse before unnecessary reinvention. We evaluated open-source options and retained the ability to modify a suitable solution or develop missing functionality.
• Keep clear technical boundaries. The architecture, data model, full-stack structure, user and role foundation, tests, deployment, and documentation made later changes easier to locate and manage.

Consulting and domain collaboration

We combined consulting and implementation. Our contact in the client's personnel development team contributed the domain expertise, while we converted that input into requirements, scope, architecture, data structures, and application behaviour.

The collaboration produced practical decisions for our engineering work:

• what belonged in the MVP;
• where an existing open-source solution fit;
• where custom development was necessary; and
• how the application needed to remain adaptable.

Technical documentation completed the handover and preserved the information needed to maintain and extend the application.

Completed outputs

The project delivered:

• analysis of existing content and unstructured requirements;
• a structured and prioritised requirements baseline;
• an agreed MVP functional scope;
• coordination with the client's personnel development contact;
• evaluation of open-source reuse, modification, and custom development paths;
• technical architecture and data model design;
• frontend, backend, and database implementation;
• basic user and role structures;
• a maintainable and extensible codebase;
• testing and bug fixing;
• deployment in the hosting environment; and
• technical documentation for continued maintenance and development.

Conclusion

We turned fragmented personnel development input into a hosted full-stack product. The completed MVP connected domain clarification, open-source evaluation, technical design, implementation, basic access structures, testing, deployment, and documentation in one delivery. It gave the client a working product baseline and a maintainable codebase for continued development.