Team leadership in the age of Agile - Roy Osherove

  • 6,253 views
Uploaded on

More from Roy at 5whys.com and osherove.com . …

More from Roy at 5whys.com and osherove.com .
In this talk Roy explores the three maturity stages of a software team, and how a team leader can adjust their leadership type based on the current phase the team is in. Roy explores common mistakes and techniques team leaders can take to make sure their team gets on the road to craftsmanship and maturity in software development.

More in: Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
  • A GENUINE PRESENTATION.THE ASPECTS COVERED IN
    THE PRESENTATION ARE PRACTICAL & SOLUTION ORIENTED.
    I WOULD LIKE TO USE THIS PRESENTATION FOR MY TALKS.
    I WOULD BE THANKFUL IF I CAN GET A COPY OF THIS PRESENTATION.
    MY EMAIL : mpslaich@yahoo.co.in
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
6,253
On Slideshare
0
From Embeds
0
Number of Embeds
5

Actions

Shares
Downloads
0
Comments
1
Likes
13

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Team LeadershipIn the age ofAgile
    @RoyOsherove
  • 2. Twitter: @RoyOsherove
    5Whys.com – blog
    Osherove.com – courses for team leaders
    Easy Unit Testing
  • 3. www.ArtOfUnitTesting.com
  • 4. Story
    The Interrupt
  • 5. Story
    Promises, Promises
  • 6. Story
    The Generous Lead
  • 7. Team Leader
    Great Teams Are Grown, Not Hired
  • 8. Three Team Maturity Stages
  • 9. Most team leaders use the wrong kind of leadership for the current team stage.
  • 10. Treat a chaotic team as a self leading team
    Teach them TDD when they don’t even use source control
    Acting as scrum master /coach when what they need is someone to save them from themselves
    Not making enough time for team learning
    Not spending enough time with the team
    Leadership in chaos #Fail
  • 11. Failure to grow a learning team into a mature team
    Fixing the team’s problems or them
    Failure to recognize impediments and teach avoidance
    Giving in to fear of confrontation with team members
    Leadership in Learning Teams #Fail
  • 12. Don’t let a mature team self organize
    Lead the daily meeting
    Decide on technical issues for the team
    Telling people what to do instead of setting constraints
    Leadership in mature teams #Fail
  • 13. The team is now in Chaotic Mode
  • 14. Treat a chaotic team as a self leading team
    Teach them TDD when they don’t even use source control
    Acting as scrum master /coach when what they need is someone to save them from themselves
    Not making enough time for team learning
    Not spending enough time with the team
    Leadership in chaos #Fail
  • 15. “when the ship is sinking the captain does not call a meeting, he gives orders”
    Main Goal – Get the team into a plateau, and get some slack time for learning
    Take back control (or others will take it)
    By talking to management
    Remove outside interference
    Declare single point of entry for requirements if needed
    By talking to the team
    Put out fires so the team can start learning
    Chaotic-Team Leadership
  • 16. Make time for our team
    Hold one on one meetings
    Hold daily stand up meetings
    Organize tasks
    Find out what is not working continuously
    Find Bottlenecks
    Start Optimizing the team’s process
    Your first commitments to the team during chaos
  • 17. Making time for your team
    Max 50% outside the team
    50% at least
    One on one meetings
    Team meetings
    Standup meetings
    Coaching
    Teaching
    Managing Goals
    Pairing
    Code review
  • 18. Absolutely Essential Team Practices During Chaos
    Non Technical
    Daily Standups
    Big Visible Task Board
    Same Room
    Weekly Support Shifts
    Technical Practices
    Build Automation
    Code Review
    Build by Feature
    Pair Programming
    Unit Testing
    TDD
  • 19. The team is now in Learning mode
  • 20. SLACK
  • 21. Story
    The Generous Lead
  • 22. Failure to grow a learning team into a mature team
    Fixing the team’s problems or them
    Failure to recognize impediments and teach avoidance
    Giving in to fear of confrontation with team members
    Leadership in Learning Teams #Fail
  • 23. Steady Growth (plateau)
    Developing Developers
    Gerald M. Weinberg – “becoming a technical leader”
  • 24. Fast Growth
  • 25. Ravines before Fast Growth
  • 26. What are you going to do about it?
  • 27. Story
    Promises, Promises
  • 28. Lack of commitment
    “we need to..”
    “If only we had ..”
    “I’ll try to get it done soon..”
    Commitment
    “I will ____ by ____”
    Commitment Language
  • 29. Say it
    Mean it
    Use commitment language
    I will… by…
    Do it
    Or flag as soon as possible that you won’t make it
    Integrity
  • 30. Explain to team
    Explain individually
    Use integrity as growth mechanism (1 on 1)
    Use integrity as part of standups
    Getting Integrity
  • 31. Changing Behaviors that won’t change
  • 32.
  • 33. Dealing with an information hoarder
    Action
    Make it a growth challenge (integrity)
    Thank them for sharing information and teaching others (even if they don’t)
    Make them in charge of training on this subject
    Tell them why you feel it’s a problem and ask them what you think should be done
    Create a shared team project requiring this knowledge
    Influence
    [personal motivation]
    [Social Motivation]
    [social ability and motivation]
    [personal & social motivation]
    [Environment motivation and ability]
  • 34. The team is mature
  • 35. Influencing Behavior using constraints
    Six Influence Factors
  • 36.
  • 37. April - in Oslo
    July – SkillsMatter in London
    Details at osherove.com
    Lead Better – 2 day course
  • 38. Be part of my book “Notes to a software team leader” –
    5whys.com/Note
    Book – Notes to a software team leader
  • 39. @RoyOshereove
    5whys.com – my blog for team leaders
    Management 3.0 by JurgenAppelo
    Other Resources
  • 40. And then… short song?
    Q & A
  • 41. When I was just a new team lead
    One of the clients came to me
    Will we succeed?
    How much will it cost?
    Can we finish in half the time?
     
  • 42. Yes, of course we can,
    Whatever you ask will be
    The future is known to me
    What you ask will be
     
  • 43. The second week the project ran
    The client called and told me this
    I changed my mind, we need something else
    Can you change it? You’re da man.
  • 44.  
    Yes, I think we can
    If we work really hard, we will
    We’ll work nights, ignore the pain
    Please don’t change your mind again
  • 45.  
    On the 10th month the client called
    And said that he’s moving the project abroad
    We’re running too late
    We’re doing it wrong
    It seems like this is our fate
  • 46.  
    Que sera sera
    Whatever will be will be
    The projects moved overseas
    Que sera sera
     
  • 47.  
    Que sera sera X 2
    Whatever will be will be
    The projects moved overseas
    Que sera sera
     
  • 48. Be part of my book “Notes to a software team leader” –
    5whys.com/Note
    @RoyOsherove
    Thank You
  • 49. Randomness adds noise