Technical Scrum Lead

As a Technical Scrum Lead at LivePerson, your main responsibilities include leading scrum teams, managing project timelines, and ensuring efficient delivery of software products. You'll also be involved in hands-on development work, continuously improving our enterprise-scale applications while coordinating product deployments and releases.

To qualify as a Technical Scrum Lead at LivePerson, you should have at least 6 years of industry experience in developing large-scale production software systems, including 2 years as a Scrum Master or Project Manager. A degree in Computer Science or a related field and certifications like Certified Scrum Master or PMP are highly preferred.

Technical Scrum Leads at LivePerson engage with a modern technology stack, including Node.js, Angular, TypeScript, and NoSQL databases like MongoDB. Familiarity with DevOps tools like Git, Docker, Kubernetes, and cloud platforms such as AWS or GCP is essential for this role.

LivePerson fosters a culture of continuous learning and innovation, which helps Technical Scrum Leads grow their careers. You'll have opportunities for further training, mentorship, and involvement in cross-regional teams, allowing you to expand your skill set and build a network of like-minded professionals.

The work culture at LivePerson is inclusive, collaborative, and encourages innovation. Technical Scrum Leads are empowered to take ownership of their projects while fostering meaningful connections within their teams and across the organization, making for a dynamic and engaging work environment.

In my previous roles, I have actively implemented agile methodologies such as Scrum and Kanban, ensuring that teams maintain effective collaboration and efficient progress in software development. I focus on regular iterations and continuous feedback to adapt and improve processes.

I believe in addressing conflicts as soon as they arise by fostering open communication. My approach is to mediate discussions, encourage team members to express their viewpoints, and work collaboratively to find a solution that respects everyone's contributions.

During sprint planning, I utilize techniques like MoSCoW (Must have, Should have, Could have, and Won't have) to effectively prioritize tasks. Additionally, I involve team members in the process to ensure alignment with project goals and dependencies.

Having led remote teams, I emphasize maintaining strong communication practices through regular check-ins, video conferencing, and collaboration tools. I also ensure that everyone feels included and connected to foster team spirit and productivity.

I assess performance through regular sprint reviews and retrospectives. By evaluating completed work against planned objectives and gathering feedback from team members, I identify areas for improvement and recognize achievements.

I focus on setting realistic timelines based on team capacity and actively track progress through daily scrums. By removing roadblocks quickly and maintaining communication with stakeholders, I ensure transparency and keep the project on track.

I prioritize feature requests in collaboration with stakeholders, assessing their impact on the overall project goals. By engaging in discussions to clarify requirements and expectations, I effectively manage priorities within the scrum team.

Maintaining alignment between development goals and business objectives can be challenging. However, I address this by facilitating regular communication between teams and stakeholders to ensure everyone is on the same page.

In a previous role, I led a retrospective that revealed bottlenecks in our workflow. By incorporating a Kanban board to visualize tasks, we significantly enhanced our sprint efficiency and increased team collaboration and accountability.

I believe in fostering an inclusive environment where team members feel valued and empowered to share ideas. Regular team-building activities and open communication help strengthen relationships and create a supportive team culture.