Front-end Expansion

When RoseTech started working with 542 Digital in July 2021, their front-end web applications had been implemented using vanilla JavaScript and jQuery. Whilst this was functional, an increase in the number and complexity of projects meant that the front-end team needed expanding and the tech stack updated. Here's what we did:

• Decoupled and overhauled the tech stack. We decoupled the front-end projects from a large PHP Laravel application and standardised the tech stack to React/Redux with TypeScript. We then implemented a separate staged deployment pipeline using Gitlab CI/CD and AWS to ensure reliable delivery.
• Built and led the front-end team. We hired, led and managed a talented team of 5 Software Engineers, 2 Product Designers and 1 Project Manager. As a team, we delivered 27 projects across our time at 542 Digital.
• Implemented standards and process. We implemented industry standard project management and software engineering processes including Agile sprints, software versioning, code reviews, coding standards and automated testing.
• Design and development coordination. We created a Figma design system that allowed applications to be rapidly prototyped for client review before a line of code was written. This formed the basis of a component library we built to standardise components across our front-end applications.

Technologies Used

React, Next.js, Redux, TypeScript, JavaScript, SCSS, Docker, Kubernetes, Gitlab CI/CD, AWS, Storybook, Jest, Ant Design, Figma

Business Process Improvements

542 grew from a small business (10 employees) to an SME (40 employees) during our time working with them. We led on implementing processes across the business to ease this transition.

• Cross-team consistency. We led on implementing software development processes across multiple development teams. We also advised other teams, such as Data, on industry standard development practices.
• Feasibility and project workflow. We worked with 542, their clients and other partners on requirements gathering, estimations, project feasibility and a staged project workflow.
• Standardised documentation. We implemented Notion as 542's central database for documentation and meeting notes, including templates for project management, software engineering and design.

Growth Consultancy

We advised 542 on handling growth throughout our time with them, culminating in a consultancy project presented to senior leadership.

• Presentations to client.. We gave several high-level presentations on process and projects to 542's clients justifying increased costs due to necessary scaling based on their requirements.
• Growth at 542 consultancy project. We worked closely with 542's senior leadership team to capture the risks and opportunities of growth. We then synthesised and presented the information with recommendations, before leading a discussion on the outcomes and actions.