42
Leadership in Open Source [email protected] @scottbw

Leadership in Open Source

Embed Size (px)

DESCRIPTION

Slides from Leadership in Open Source session at TYPO3 Developer days

Citation preview

Page 1: Leadership in Open Source

Leadership in Open Source

[email protected]@scottbw

Page 2: Leadership in Open Source

What I’ll be covering in this session

1. What is leadership in an OSS project?

2. Leadership attributes, character and styles

3. Mentoring

4. Leadership communications

Page 3: Leadership in Open Source

1. What is leadership in OSS?

Leadership is really just common sense. Which is why its so difficult.

Page 4: Leadership in Open Source

John Quincy Adams

If your actions inspire others to dream more, learn more, do more and become more, you are a leader

Page 5: Leadership in Open Source

What is leadership?

• Leadership is a characteristic that can be demonstrated in any role, in any function, and at any time

• Leadership is about the tone of our behaviour, not a set of rules to be followed

• Leadership is not about doing everything yourself

Page 6: Leadership in Open Source

Management is not leadership?

Managers Leaders

Follow Rules Follow Instincts

Focus on getting things done

Focus on getting the right things done

Side with safety Side with risk

Focus on delivering today Focus on articulating tomorrow

Mark Anderson: The Leadership Book

Page 7: Leadership in Open Source

Does OSS need leadership?

“… what is leadership in open source communities? It's accountability. It's shouldering the responsibility for making sure work gets done. Largely that means making sure that those who want to do work can do it - that there are no roadblocks for those doing the work. It may also mean doing the work yourself if no one else steps up. Sadly, many people don't realize this and work towards attaining leadership roles ... This almost always fails in a community ... In short, if there's a change you want made, and you aren't participating in making it happen, then you aren't doing it the open source way.” - David Nalley

Page 8: Leadership in Open Source

Cooperation vs. Collaboration

The genius of open source has been to break projects into chunks where people can go and work in isolation.

Then bring it back and fold it into the project.

This is what makes projects efficient.

Always be thinking about how you can make problems into co-operative problems, rather than collaborative problems.

David Eaves

Page 9: Leadership in Open Source

Management in cooperative work is through leadership

- communicate the vision, tone and norms- ensure appropriate division of work to

prevent deadlocks and stalling- minimize overlaps that can cause conflict- facilitate communication over shared

concerns and overlaps- shepherd occasional larger-scale strategic

refactoring

Page 10: Leadership in Open Source

In summary…

OSS projects are social capital: leadership is about growing and

directing that social capital

Page 11: Leadership in Open Source

2. Leadership attributes, character and styles

Page 12: Leadership in Open Source

Leadership Attributes

Page 13: Leadership in Open Source

Standard Bearers

Establish the ethical framework of an organisation

Set the tone of work by their demeanor

Set the norms of work through their behaviour

Page 14: Leadership in Open Source

Developers

Help others through teaching and mentoring

Take opportunities both to learn and to teach

Page 15: Leadership in Open Source

Integrators

Orchestrate the activities of the organisation

Articulate the vision of the future

Page 16: Leadership in Open Source

ACTIVITY

Think about one OSS leader who you've worked with in the past. How much did they act as standard bearer, developer (of people) and integrator?

Did they pay too much attention to one and ignore the others, or did they balance out these attributes?

Page 17: Leadership in Open Source

Leadership Character

Page 18: Leadership in Open Source

Leadership Character Traits

Demeanor

Visibility

Messaging

Communicating direction

Approachability

Listening

Fairness

Performance mgt

Personal development

Open to innovation

Respecting diversity

Principles

Honesty

Respect

Fairness

Clarity

Openness

Collegiality

Decisiveness

Humility

(Respect for) Diversity

Bravery

Mark Anderson: The Leadership Book

Page 19: Leadership in Open Source

Even more lists!USMC:

Justice

Judgment

Dependability

Initiative

Decisiveness

Tact

Integrity

Enthusiasm

Bearing

Unselfishness

Courage

Knowledge

Loyalty

Endurance

TPG:

Honest

Competent

Forward-looking

Inspiring

Intelligent

Fair-minded

Broad-minded

Courageous

Straightforward

Imaginative

Tanya Prive, Forbes:Honesty

Ability to delegate

Communication

Sense of humour

Confidence

Commitment

Positive Attitude

Creativity

Intuition

Ability to Inspire

Page 20: Leadership in Open Source

OK, so..?

Don’t be too concerned with the lists..!

Take a process approach: appraise your strengths and weaknesses, and devise strategies to address what you see as problem areas

To be a better leader, you need to take your own personal development seriously

Page 21: Leadership in Open Source

Questionnaires and self-tests can bring useful insights, even when they are complete nonsense

Self-analysis

To develop leadership character you should be reflective and self-aware

Page 22: Leadership in Open Source

ACTIVITYReflective thinking is important for leaders - you need to calibrate and take an outside view of your leadership behaviour and demeanour.

Ask yourself:

Am I fair?

Do I listen to others?

Do I take responsibility?

Do I care about other people?

Am I honest?

Am I willing to debate?

Do my colleagues trust me?

Where do I excel as a leader?

What are my weaknesses - where do I know I could do better?

Page 23: Leadership in Open Source

Common mistakes by leaders

Lack of contact

Inconsistency in messaging

Unfairness in decision making

Taking feedback badly

Page 24: Leadership in Open Source

How to Receive Feedback

Leaders need to analyse feedback rather than just react to itavoid temptation to be defensive, or dismissiveavoid dwelling on negative feedbackthank people for feedback - even negative. show you are listening - don't just respond automatically, but demonstrate that you take feedback seriously and are thinking it through

Page 25: Leadership in Open Source

Common problems experienced by leaders

Feelings of isolationDwelling on mistakesBurnoutArroganceDoubt

Page 26: Leadership in Open Source

Are you a leader, or just acting like one? How could you tell the difference?

Page 27: Leadership in Open Source

Leadership Styles

Autocratic

Participative

Delegative

We’ve given you a leadership styles questionnaire so you can find out what your preferred leadership style might be

Page 28: Leadership in Open Source

3. Mentoring

Page 29: Leadership in Open Source

Why should I be a mentor?

Mentoring is a key part of leadership

Leaders are often the beneficiaries of mentoring

Leaders pass on their expertise and develop their community through mentoring

Leaders support their own self-development by mentoring others

Page 30: Leadership in Open Source

Mentoring vs. Coaching

Mentoring is an indefinite, relationship based activity with several specific but wide ranging goals…over an extended time period. The agenda is open and continues to evolve... seeks to build wisdom – the ability to apply skills, knowledge and experience to new situations and processes

Coaching involves ... meeting very specific objectives within a set period of time … mainly concerned with performance and the development of certain skills… there is usually a planned programme with a much shorter timeframe than in mentoring, so the learning goals are usually determined in advance.

(However, often used interchangeably, e.g. GSoC is probably “coaching” rather than “mentoring” according to this definition)

CIMA: Mentoring and Coaching Topic Guide

Page 31: Leadership in Open Source

What is mentoring for?

Developing knowledgeworking with mentees to build their skills and knowledge, either of the domain, or project-specific knowledge

Developing attitudesworking with mentees to develop their demeanor as a community member

Reinforcing normsworking with mentees to encourage specific behaviours

Building commitmentencouraging deeper participation in the community

Page 32: Leadership in Open Source

Key considerations for mentoring

Frequency of contactrealistically, how much time can you spend?

when do you want to be available?

Method of contactf2f, skype, email…

Duration of partnershipdo you want to set a limit? Or continue as long as you’re both happy to?

Page 33: Leadership in Open Source

Key considerations for mentoring

ConfidentialityConsider how you will handle confidential communications; for example you may need to discuss difficult situations in the community with mentees

Setting expectationsBe clear about what you are offering, particularly time and contact commitments

Page 34: Leadership in Open Source

Experiential learning

Adapted from David Kolb’s Learning Cycle

Page 35: Leadership in Open Source

Giving feedback

Giving feedback is a crucial part of mentoringFeedback should be frequent and timely Be as specific and relevant as possible

I.e. “your method names should be more self-explanatory and have comments to help other developers” not “your code is sloppy”

Always acknowledge achievements and progressKeep it simple and concise

Page 36: Leadership in Open Source

Getting started

Nurturing early contributorscan start at any time, just identify a new contributor, and offer to work with them

Mentoring in formal programmesjoin an established programme, or start one up for your project. Established programmes have a support network and processes

Page 37: Leadership in Open Source

Mentoring programmes

Google Summer of Codehttps://developers.google.com/open-source/soc/

VALS Semester of Codehttp://semesterofcode.com/

Outreach Programme for Womenhttps://live.gnome.org/OutreachProgramForWomen

Page 38: Leadership in Open Source

4. Leadership communications

Page 39: Leadership in Open Source

Leadership communication acts

SummationParaphrasingAcknowledgingDecisionsReframingUnblockingIndividual follow-ups

Page 40: Leadership in Open Source

ACTIVITY

Reflect on your communications with your project - can you identify an example where you have used one of the communication actions we've listed?

Page 41: Leadership in Open Source

Questions

Page 42: Leadership in Open Source

Resources

• Mark Anderson, The Leadership Book (Financial Times Series)

• David Nalley, Leadership in Open Source Communities http://opensource.com/business/11/2/leadership-open-source-communities

• David Eaves, Wiki's and Open Source: Collaborative or Cooperative? http://eaves.ca/2007/02/05/wikis-and-open-source-collaborative-or-cooperative/