As a full-stack engineer, our team member was able to hit the ground running with the tech stack and ways of working. A handover with the outgoing engineer supported knowledge transfer and understanding of the standards-driven environment.

Our expertise added value to the project, especially when it came to rebuilding and revising the product architecture, and build scripting and tooling:

• Knowledge of AWS and Terraform meant we could demonstrate how the new tech would interact differently from the previous version – and the challenges, risks, limitations and opportunities this provided
• In-depth understanding allowed us to be the ‘bridge’ between key stakeholders and developers, communicating messages around wants, requirements, and updates into the right language for each stakeholder
• Our ethos of doing the ‘right thing at the right time’ and asking the right questions around work planning supported focused, informed decision making.

As part of the ‘Doza way’, a priority was to upskill and coach the technical lead and team members, to avoid future knowledge gaps when maintaining and developing the system. As part of this upskilling, we facilitated best-practice in the team, for example:

• Swarming sessions: Having an individual handle a ticket from start to finish working collaboratively with the development team delivered quicker resolutions, and supported team learning and collaboration
• Pair programming: Working with another programmer to collaborate solved problems fast, reduced silo working, and allowed us to learn from (and teach) others
• Asking questions: It benefited everyone when we asked questions rather than giving the answers, encouraging problem solving and knowledge sharing across teams.

‍