The changing role of the
TEAM LEADER
in a DevOps transformation
Steve Mactaggart @stevemac
Steve Mactaggart
Application Delivery Evangineer
$ whoami
@stevemac
What makes a team leader?
Responsibility for people
Ownership of process
Technical leader
Allocate capacity
Business influence
Strategic thinking
Plan work
@stevemac
Agile and DevOps myths
• They are the same thing
• DevOps is just about Automation
• We don’t need Operations staff anymore
@stevemac
DevOps
“DevOps is an extension of agile that
brings responsibility for long term
systems operations to delivery teams”
@stevemac
Where is the biggest change?
Allocate capacity
Plan work
@stevemac
With DevOps
How we allocate capacity has changed
We have long-lived persistent teams - Capacity is known
@stevemac
With DevOps
How we plan work has changed
Teams do work and have defined backlogs - Work is planned
@stevemac
With DevOps
If we have a handle on:
• Allocating capacity
• Planning work
What is the role of a Team Leader?
@stevemac
The two options
Move In - Join the team
Move Out - Support the team
@stevemac
Move In - Join the team
• Product Owner
• Scrum Master
• Technical Lead
• JATM - Just another team member
@stevemac
Move Out - Support the team
• Product Manager
• Capability Leader
• Business Sponsor
4 key foci
@stevemac
1. Challenge the team to learn from failure
• If new to Operations - Understand the impact of failure
• Failure is only bad if you don’t learn from it
• DevOps is new - accept that problems will occur
• Use diplomatic skills to improve relations
@stevemac
2. Empower increased capacity through automation
• It’s not the all of DevOps - but often a focus
• Work is infinite - the team is not
• Automation may be new to team - start early - start small
• Outcome is reducing repetitive actions
- not headcount
• Showcase even the small gains
@stevemac
3. Drive understanding of new career options
• Encourage empathy between Dev and Ops
• Understand the motivations of team and stakeholders
• Continually look for ways to T-shape people
• Head towards opportunities of cross-skilling
• Respect concerns - take your time
@stevemac
4. Educate on the responsibility of priority
• DevOps is an extension of Agile - Prioritisation is the key
• Focus inside a team creates confidence
• Clear priority that is not constantly changing
• Educate both ways - In and Out
• Define some guidelines
Questions
Steve Mactaggart
@stevemac
#LASTconf 2017
• Move In or Out
• Work on the 4 key foci
• Challenge the team to learn from
failure
• Empower increased capacity
through automation
• Drive understanding of new
career options
• Educate on the responsibility of
priority

The changing role of the team leader in a DevOps transformation

  • 2.
    The changing roleof the TEAM LEADER in a DevOps transformation Steve Mactaggart @stevemac
  • 3.
  • 4.
    @stevemac What makes ateam leader? Responsibility for people Ownership of process Technical leader Allocate capacity Business influence Strategic thinking Plan work
  • 5.
    @stevemac Agile and DevOpsmyths • They are the same thing • DevOps is just about Automation • We don’t need Operations staff anymore
  • 6.
    @stevemac DevOps “DevOps is anextension of agile that brings responsibility for long term systems operations to delivery teams”
  • 7.
    @stevemac Where is thebiggest change? Allocate capacity Plan work
  • 8.
    @stevemac With DevOps How weallocate capacity has changed We have long-lived persistent teams - Capacity is known
  • 9.
    @stevemac With DevOps How weplan work has changed Teams do work and have defined backlogs - Work is planned
  • 10.
    @stevemac With DevOps If wehave a handle on: • Allocating capacity • Planning work What is the role of a Team Leader?
  • 11.
    @stevemac The two options MoveIn - Join the team Move Out - Support the team
  • 12.
    @stevemac Move In -Join the team • Product Owner • Scrum Master • Technical Lead • JATM - Just another team member
  • 13.
    @stevemac Move Out -Support the team • Product Manager • Capability Leader • Business Sponsor
  • 14.
  • 15.
    @stevemac 1. Challenge theteam to learn from failure • If new to Operations - Understand the impact of failure • Failure is only bad if you don’t learn from it • DevOps is new - accept that problems will occur • Use diplomatic skills to improve relations
  • 16.
    @stevemac 2. Empower increasedcapacity through automation • It’s not the all of DevOps - but often a focus • Work is infinite - the team is not • Automation may be new to team - start early - start small • Outcome is reducing repetitive actions - not headcount • Showcase even the small gains
  • 17.
    @stevemac 3. Drive understandingof new career options • Encourage empathy between Dev and Ops • Understand the motivations of team and stakeholders • Continually look for ways to T-shape people • Head towards opportunities of cross-skilling • Respect concerns - take your time
  • 18.
    @stevemac 4. Educate onthe responsibility of priority • DevOps is an extension of Agile - Prioritisation is the key • Focus inside a team creates confidence • Clear priority that is not constantly changing • Educate both ways - In and Out • Define some guidelines
  • 19.
    Questions Steve Mactaggart @stevemac #LASTconf 2017 •Move In or Out • Work on the 4 key foci • Challenge the team to learn from failure • Empower increased capacity through automation • Drive understanding of new career options • Educate on the responsibility of priority

Editor's Notes

  • #4 We are here to talk about organisational change within DevOps - and how that changes a Team Leader’s role
  • #7 Agile teams Vs DevOps teams - Project teams vs Persistent teams - Coupled with broader organisational restructure