Technical Delivery Lead

**LATAM** working in hours that align with
**EST**.

The Delivery lead is accountable for the
_quality and timely completion of a project’s technical deliverables_. This is a leadership role that comprises aspects of software engineering, system architecture and team management. It is envisioned that the Delivery Lead would oversee the delivery of 1-2 projects. In a traditional agency setting, the role would best align with a “technical architect”. However that title emphasizes architecture over leadership, collaboration and delivery skills.

While the delivery lead may specialize in a particular area of software development, they strive to become “polyglot” technologists. A broad understanding of front-end, back-end, mobile, dev-ops and testing techniques assists the Delivery Lead in proposing effective solutions and facilitating communication and collaboration amongst the team. The Delivery Lead writes enough code to keep their skills current and relevant. They may also write code in order to fill gaps in the team’s skillset. However the Delivery Lead
_ should not write code if the time required compromises their other responsibilities_.

The Delivery Lead understands that software development is a challenging and stressful process. They promote a calm, positive, supportive and solution-oriented atmosphere within the team.

**Responsibilities**:

- Collaborate with the Delivery Leads team to establish the project's architecture and technology stack. While the Delivery Lead initiates the solution design, they acknowledge that architecture evolves and welcome contributions from other team members.
- Maintain up-to-date documentation to facilitate the team's understanding of how different solution components interact.
- Coordinate with the project manager to ensure the tech team has the necessary resources and allocation, effective delegation of work, and timely delivery of high-quality technical artefacts.
- Collaborate with the product manager and QA team to develop a comprehensive project test plan. This plan should specify the platforms, browsers, and devices requiring testing, as well as outline accessibility, load, performance, integration, and security testing requirements. It may also include guidelines for defect classification and resolution during the QA process.
- Serve as the primary technical contact for the client, handling all technical matters.
- Assist team members in resolving technical obstacles identified during daily stand-up meetings. Provide mentorship and guidance to engineers and QA analysts on the team whenever possible.
- Work with the project manager to identify potential risks that may impede timely project delivery. These risks can be related to technology, staffing, scope, or client management. Whenever feasible, the Delivery Lead aims to mitigate risks through decision-making, which may involve conducting technical spikes or proof of concepts.
- Collaborate with the project manager to schedule code freezes, product releases, deployments, and user acceptance testing.
- Promote an Agile delivery model, prioritizing features with high business value for early delivery in the project's development cycle. Collaborate with product and project managers to understand business requirements and prioritize stories accordingly.
- Participate in and contribute to a project's Scrum rituals and ceremonies.
- Escalate to the project manager if stories do not meet the agreed-upon definition of ready. This definition may vary across projects, but generally includes detailed acceptance criteria, testability, clear design direction, team estimation, and deliverability within a single sprint.
- Advocate for craftsmanship by implementing code analysis tools, linting tools, peer reviews, and other processes. Encourage software development principles such as DRY (Don't Repeat Yourself) and SOLID. Code should be efficient, maintainable, tested, and well-documented.
- Select and document an appropriate code branching model, ensuring the team understands it. Set up version control and complete documentation by the end of sprint zero.
- Ensure the establishment of a CI/CD pipeline to facilitate efficient delivery and testing of new features. This should generally be completed by the end of sprint zero.
- Identify, document, and provision development, testing, staging, and production environments. Automate deployments to ensure repeatability without adverse effects.
- Foster collective ownership of the codebase within the tech team. Share knowledge to enable any team member to resolve problems that arise during the project.
- Collaborate with the project manager to identify, document, and address technical debt accumulated during the project.
- Advocate for the user experience, identifying opportunities for improvement whenever possible.
- Provide input on the feasibility and effort required for designs or interactions in the early design phases. Work closely with UX or UI teams to balance