Presentation: Leadership Lessons From the Agile Manifesto
Abstract
Whether you’re a Tech Lead, Engineering Manager, or Project Manager for an engineering team, you probably weren’t handed a leadership instruction manual when you were given your first team to lead. Even experienced technical leaders usually operate from a set of instincts and the hard lessons learned from painful mistakes. However, leadership is a skill that you can learn and develop if you know where to look. You don't have to be a “born leader”, but you do need a set of principles to guide the leader within you. This session will teach you how to apply the principles in the Manifesto for Agile Software Development to become a leader equipped with a framework for making decisions.
What’s the motivation for this talk?
When I was given my first technical team to lead many years ago, I didn’t know what to do. I copied the style of technical leads I worked with and what I could learn by reading USENET newsgroups about leadership (yes, it was that long ago). The results were mixed, and I felt that I was constantly making it up as I went along. However, after I began leading projects that used Agile software development, I eventually realized that the principles behind Agile provided powerful guidelines for leading my teams! These principles made me a more effective leader, increased team morale, and improved my ability to deliver software to customers.
What do you hope someone will leave this talk with?
This session will help attendees understand the principles behind the Manifesto for Agile Software Development and how to practically apply them to their daily leadership practices. They will leave the talk with a decision matrix for determining the right course of action when leading their teams, interacting with customers, and dealing with uncertainty.
How you you describe the persona and level of the target audience?
The persona of the target audience is someone tasked to lead a team of software developers. Ideally, this person has worked with cross-functional teams of 3 to 9 people and has completed at least one software development project using Scrum or Kanban.
Similar Talks
License Compliance for Your Container Supply Chain
Open Source Engineer @VMware
Nisha Kumar
Observability in the SSC: Seeing Into Your Build System
Engineer @honeycombio
Ben Hartshorne
Evolution of Edge @Netflix
Engineering Leader @Netflix
Vasily Vlasov
Mistakes and Discoveries While Cultivating Ownership
Engineering Manager @Netflix in Cloud Infrastructure
Aaron Blohowiak
Optimizing Yourself: Neurodiversity in Tech
Consultant @Microsoft
Elizabeth Schneider
Six Things I've Learned as a Manager I Wish I Knew Before
Lead Developer @bookingcom
Georgiy Mogelashvili
Monitoring and Tracing @Netflix Streaming Data Infrastructure
Architect & Engineer in Real Time Data Infrastructure Team @Netflix
Allen Wang
Future of Data Engineering
Distinguished Engineer @WePay
Chris Riccomini
Coding without Complexity
CEO/Cofounder @darklang