RoyOsherove_TeamLeadershipInTheAgeOfAgile
0 likes400 views
The document discusses challenges team leaders face at different stages of a team's development and maturity. It outlines three stages - chaos, learning, and mature. It provides examples of leadership failures at each stage when the wrong type of leadership is applied. It emphasizes the importance of the team leader adapting their leadership style to the current needs of the team based on what stage of development and maturity it is in.
![Dealing with an information hoarder
Action Influence
Make it a growth challenge (integrity) [personal motivation]
Thank them for sharing information [Social Motivation]
and teaching others (even if they
don’t)
Make them in charge of training on [social ability and motivation]
this subject
Tell them why you feel it’s a problem
and ask them what you think should be [personal & social motivation]
done
Create a shared team project requiring
this knowledge [Environment motivation and
ability]](https://image.slidesharecdn.com/file3-110405162851-phpapp02/85/RoyOsherove_TeamLeadershipInTheAgeOfAgile-33-320.jpg)
RoyOsherove_TeamLeadershipInTheAgeOfAgile
- 1. @RoyOsherove
- 2. Twitter: @RoyOsherove 5Whys.com – blog Osherove.com – courses for team leaders Easy Unit Testing
- 7. Team Leader Great Teams Are Grown, Not Hired
- 8. Three Team Maturity Stages Self Organization Managed Learning Chaos
- 9. Most team leaders use the wrong kind of leadership for the current team stage.
- 10. Leadership in chaos #Fail 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
- 11. Leadership in Learning Teams #Fail 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
- 12. Leadership in mature teams #Fail 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
- 13. The team is now in Chaotic Mode
- 14. Leadership in chaos #Fail 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
- 15. Chaotic-Team Leadership “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
- 16. Your first commitments to the team during chaos 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
- 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
- 22. Leadership in Learning Teams #Fail 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
- 23. Developing Developers Steady Growth (plateau) Gerald M. Weinberg – “becoming a technical leader”
- 24. Fast Growth
- 25. Ravines before Fast Growth
- 26. What are you going to do about it?
- 28. Commitment Language Lack of commitment “we need to..” “If only we had ..” “I’ll try to get it done soon..” Commitment “I will ____ by ____”
- 29. Integrity Say it Mean it Use commitment language I will… by… Do it Or flag as soon as possible that you won’t make it
- 30. Getting Integrity Explain to team Explain individually Use integrity as growth mechanism (1 on 1) Use integrity as part of standups
- 31. Changing Behaviors that won’t change
- 33. Dealing with an information hoarder Action Influence Make it a growth challenge (integrity) [personal motivation] Thank them for sharing information [Social Motivation] and teaching others (even if they don’t) Make them in charge of training on [social ability and motivation] this subject Tell them why you feel it’s a problem and ask them what you think should be [personal & social motivation] done Create a shared team project requiring this knowledge [Environment motivation and ability]
- 34. The team is mature
- 35. Influencing Behavior using constraints Six Influence Factors
- 37. Lead Better – 2 day course April - in Oslo July – SkillsMatter in London Details at osherove.com
- 38. Book – Notes to a software team leader Be part of my book “Notes to a software team leader” – 5whys.com/Note
- 39. Other Resources @RoyOshereove 5whys.com – my blog for team leaders Management 3.0 by Jurgen Appelo
- 40. Q&A And then… short song?
- 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. Thank You Be part of my book “Notes to a software team leader” – 5whys.com/Note @RoyOsherove