• Like
  • Save
Leading Tech Teams
Upcoming SlideShare
Loading in...5
×
 

Leading Tech Teams

on

  • 690 views

Workshop from I T.A.K.E. Unconference 2014 on how to lead technical teams. ...

Workshop from I T.A.K.E. Unconference 2014 on how to lead technical teams.

Topics covered:
- Five duties of technical leaders
- Change management process
- How to communicate effectively

Statistics

Views

Total Views
690
Views on SlideShare
402
Embed Views
288

Actions

Likes
0
Downloads
5
Comments
0

1 Embed 288

http://2014.itakeunconf.com 288

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Leading Tech Teams Leading Tech Teams Presentation Transcript

    • Leading Technical Teams I T.A.K.E. Unconference 2014 Leading Technical Teams Flavius Stef | I T.A.K.E. Unconference 2014 1.0
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Agenda Why should people follow you? What makes a great leader? Patterns for catalyzing change How can you make change happen? How to listen and talk to others Reduce noise in conversations 1. 2. 3.
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Me? Flavius Stef In I.T. since 2002 Agile Coach and Trainer Was: – Web Developer – Project Manager – Scrum Master – Product Owner – Co-founder flavius.stef@mozaicworks.com (Twitter) @FlaviusStef
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Visual Map
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Why are you here? One leader you admire One leader you dislike
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Why should people follow YOU?Why should people follow YOU?
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Module agenda Solve one leadership problem Create strategy and debrief Leadership qualities The five areas to master Redo leadership problem Adjust strategy and debrief 1. 2. 3.
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Solve the leadership challenges At least 4 actions 07' create strategy 03' debrief
    • Leading Technical Teams I T.A.K.E. Unconference 2014 What does a leader do? Demonstrates character Clarifies direction Solves problems Increases motivation Develops people
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Demonstrates character Expose and embody your values Communicate properly Have a positive attitude Be disciplined
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Clarifies direction Envision the future Democratize information Enlist others Expect the best
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Solves problems Understand the problem Generate ideas Enable collaboration Challenge the status quo
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Increases motivation Care about others Answer: “What's in it for me?” Amplify or dampen voices Recognize contributions
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Develops people Set challenging goals Explain thought process Provide mentoring Create a learning community
    • Leading Technical Teams I T.A.K.E. Unconference 2014 What does a leader do? Demonstrates character Clarifies direction Solves problems Increases motivation Develops people
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Modify strategy At least 2 actions 05' change 05' debrief
    • Leading Technical Teams I T.A.K.E. Unconference 2014 During break Two leadership characteristics Find pair Discuss three next actions
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Learn More ● Gerald Weinberg – Becoming a Technical Leader ● Roy Osherove – Notes to a Software Team Leader ● John Maxwell – Developing the Leader Within You ● Kouzes & Posner – The Leadership Challenge ● David Allen – Getting Things Done ● Richard Hackman – Leading Teams
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Patterns for catalyzing changePatterns for catalyzing change
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Groups of 3-4 What techniques do you use for instigating change? 05' techniques 05' debrief
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Module agenda Before starting First one-two months Next one-two months After that Throughout 1. 2. 3. 4. 5.
    • Leading Technical Teams I T.A.K.E. Unconference 2014 BEFORE STARTING
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Define the purpose
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Communicate the purpose Icon: Renaud Mignerey, from The Noun Project
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Create the team Icon: Björn Andersson, from The Noun Project
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Create the team http://en.wikipedia.org/wiki/File:DiffusionOfInnovation.png
    • Leading Technical Teams I T.A.K.E. Unconference 2014 FIRST 1-2 MONTHS
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Train everybody
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Ensure slack while learning Icon: Jeremy Boatman, from The Noun Project
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Ensure slack while learning
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Address both rider and elephant Ron Baldesancho, from The Noun ProjectLuis Prado, from The Noun Project
    • Leading Technical Teams I T.A.K.E. Unconference 2014 NEXT 1-2 MONTHS
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Find and promote small wins Matthew R. Miller, from The Noun Project
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Coach and mentor Videologin.net, from The Noun Project
    • Leading Technical Teams I T.A.K.E. Unconference 2014 AFTER THAT
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Keep pushing until it's the norm Rohan Gupta, from The Noun Project
    • Leading Technical Teams I T.A.K.E. Unconference 2014 THROUGHOUT
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Plan D o StudyAct
    • Leading Technical Teams I T.A.K.E. Unconference 2014 WRAP UP
    • Leading Technical Teams I T.A.K.E. Unconference 2014 BEFORE FIRST NEXT THEN Define Purpose Communicate Purpose Create team Train everybody Ensure slack Address rider AND elephant Find & promote small wins Coach and mentor Keep pushing until it's the new “normal” Plan Do Study Act
    • Leading Technical Teams I T.A.K.E. Unconference 2014 You are the professional. Demand respect for your experience. DARE!DARE!
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Groups of 3-4 Solve the change challenges 10' group work 05' debrief
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Learn More ● Geoffrey Moore – Crossing the Chasm ● Chip & Dan Heath – Switch ● Linda Rising – Fearless Change ● Jurgen Appelo – How to Change the World ● John Kotter – Leading Change, The Heart of Change ● Google: “The Satir Change model” ● Google: “Plan-Do-Study-Act”
    • Leading Technical Teams I T.A.K.E. Unconference 2014 How to listen and talk to othersHow to listen and talk to others
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Module agenda Types of communication behaviors Aggressive, Submissive, Assertive Hearing what they say Listening and powerful questions Giving feedback Inferences and a feedback model 1. 2. 3.
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Three types of behavior Aggressive Submissive Assertive
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Aggressive communication ● Focus on self: opinions, rights ● Disregard others (no listening) ● Lack of skills or trust in skills ● Assumption that it's effective ● Alienation ● Concentrate on short vs long term ● Sometimes it escalates
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Submissive communication ● Need to avoid confrontation ● Low self-esteem ● Don't express own opinions, feelings ● Accept offense ● Buried resentment and anger ● Not involved in decision making
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Assertive communication ● Honest, Determined, Respectful ● Congruent communication: words, gestures, feelings ● Investigate other person's feelings ● Ask for what you want ● It's ok to say “no” ● It's ok to say “I don't know” ● You can change your mind
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Answer the quiz 05' individual work
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Levels of listening LEVEL 0 No listening Interrupting Think what to say next Say your opinion LEVEL 1 Wait for the other to finish Try to understand their point Say your opinion LEVEL 2 Listen to what's not being said Understand their point and their feelings Reflect point and feelings
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Closed questions ● Is it true that...? ● Why did you...? ● Is this a good idea? ● Have you thought this through? ● Can you give me an example? ● Does this answer your question? ● Can I help you with something?
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Open-ended questions ● Please describe... ● What do you hope to achieve? ● How would that help? ● What have you tried? ● What would X advise? ● What other options do we have? ● What would success look like?
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Listening exercise Work in pairs Think of a situation at work and describe it to your pair 2x 03' no listening _______closed questions 2x 03' empathic listening, _______open-ended questions
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Ladder of inference Observable data Selected data Interpret data Assumptions Conclusions Beliefs Actions Feedback loop
    • Leading Technical Teams I T.A.K.E. Unconference 2014 How to give feedback May I give you some feedback? When you (state observations) Then I (state feelings) Because I (state needs) Would you (state desired behavior) ?
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Feedback challenges Work in pairs, take turns 4x 01'
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Learn More ● Lyssa Adkins – Coaching Agile Teams ● Edgar Schein – Humble Inquiry ● Tony Stoltzfus – Coaching Questions ● Tom DeMarco – Peopleware ● Johanna Rothman – Behind Closed Doors ● Dale Carnegie – How to Make Friends and Influence People ● Arbinger Institute – Leadership and Self-Deception
    • Leading Technical Teams I T.A.K.E. Unconference 2014 That's a wrap! Thanks! flavius.stef@mozaicworks.com flaviusstef.wordpress.com Search: Twitter, LinkedIn, FB
    • Leading Technical Teams I T.A.K.E. Unconference 2014 Photo credits Cover: https://flic.kr/p/4kqC8H Cubs in a row: https://flic.kr/p/no4sib Portaits: http://en.wikipedia.org/wiki/File: {Jonathan.Ive.jpg,Marissa_Mayer_May_2014_(cropped).jpg,Martin_Fowler_(2008) .jpg,Tyson_-_Apollo_40th_anniversary_2009.jpg} Tree: https://flic.kr/p/8AYb1v Crossroads: https://flic.kr/p/7GWMCc High five: https://flic.kr/p/4YJRQ7 Support dude: https://flic.kr/p/gV1Ltr Guy doing kata: https://flic.kr/p/9aJGNi Cat on leash: https://flic.kr/p/a1T2C Arguing tigers: https://flic.kr/p/nqVpFP Cat with bow: https://flic.kr/p/7Q7wY