schedule Mar 19th 11:30 AM - 12:15 PM place Jupiter 1 people 45 Interested

Ever wondered why some people prefer to work alone? Or why some people cringe when pair programming is mentioned? It might be that that person, like me, is an introvert. But is is really that simple? Can we really put every person in a box labeled "introvert" or "extrovert" or are we all just ambiverts?

During this session I will talk about introverts, extroverts and everything in between.
Drawing from almost 15 years of personal experience being an introvert on agile teams I will talk about the differences of being an extrovert
or an introvert, how to foster an inclusive team environment, and the importance of psychological safety.
You will hopefully leave this session better fit to help EVERYONE on your team to reach their full potential!

 
 

Outline/Structure of the Talk

This is how the talk is structured:
1 - Introduction (3 mins)
2 - The characteristics of introverts and extroverts. (10 mins)
3 - Different types of introversion. (5 mins)
4 - Psychological safety, one of the key parts of Modern Agile. What is it and how do we get it? Why is it so important to have on teams? (10 mins)
5 - Time to give some hands-on tips on how to foster an inclusive team environment, and also what agile practices that works best and what to avoid. (15 mins)
6 - I close with a short summary (2 mins).

I include a number of stories from my own experience as an introvert developer to exemplify some points.

Learning Outcome

  • Differences between introverts, extroverts and ambiverts
  • How everyone can be an excellent team player
  • The importance of psychological safety
  • Tips on how to improve the psychological safety in your teams
  • Tips on how to create an inclusive team environment

Target Audience

Everyone working on teams, agile or not. Managers and coaches will also benefit.

Prerequisites for Attendees

No prerequisites.

schedule Submitted 11 months ago

Public Feedback

comment Suggest improvements to the Speaker
  • Yves Hanoulle
    By Yves Hanoulle  ~  10 months ago
    reply Reply

    I give this session an 8 out of 10

    what I love is:

    The topic. A lot of introverts feel agile is not for them/does not respect them, yet some of the best coaches and scrummasters are introverts. 

    it starts with a definition of introvert vs extrovert 

    it mentions ambiverts 

    in stresses safety

    To make this better

    - I would like to see more interaction 
    - add a (safe) exercise to practice stuff
    -I would like to see a small retro part where the audience mentions what they have learned

    Pair presentation 

     

    • Tobias Anderberg
      By Tobias Anderberg  ~  10 months ago
      reply Reply

      Thank you very much for the feedback Yves! I will take your points into consideration.

  • Tathagat Varma
    By Tathagat Varma  ~  11 months ago
    reply Reply

    Thanks for your proposal Tobias. I like the topic because in some sense, in the agile world, we assume everyone like to interact ("individuals and interactions...") or sit in open-plan offices and soak into osmotic communication, etc. In reality, a growing number of people are disenchanted with some of the side-effects of such workplaces, and would rather prefer a bit of solitude to come alive...and there is nothing wrong in that! Sadly, the generally understood ideas behind mainstream agile literature overvalue such interactions, without recognizing the presence of people who might thrive in a slightly different configuration. So, talks such as yours are very valuable in bring out the nuances to make the team truly inclusive in every meaningful sense of the word.

    Just so that the review team can fully consider your proposal, please share any videos of your part work, and also - I could not view your entire deck. Can you please confirm if you will discuss some real-life examples of building / coaching / being in agile teams that had such integration challenges, and your personal examples from it?

    • Tobias Anderberg
      By Tobias Anderberg  ~  11 months ago
      reply Reply

      Thank you for the comments! 

      Yes, I will use some real-life examples, but the main focus will unfortunately not be on storytelling but instead on the theories behind introversion and how it adapts to agile.

      I will hold a shorter version of this talk on a swedish conference tomorrow (18th of October) and it will be filmed there. When the video is up on youtube I will update this proposal with a link to the video. Unfortunately it will be in swedish, but hopefully it will give the review team some idea of my style of presentation.

      Could you describe in more detail what you mean by not being able to view my entire deck?

      regards,

      Tobias

      • Ravi Kumar
        By Ravi Kumar  ~  10 months ago
        reply Reply

        Hi Tobias,

        I love the topic and the slides looked great but as with TV I could not view the entire deck. To be specific the Github link shared could not load more pages. I could get to only the 'Long road ahead....for introverts' slide.

        It will help the review committee if you can share some real examples on coaching agile teams. Also, any links to you video.

         

        Thanks,

        Ravi 

        • Tobias Anderberg
          By Tobias Anderberg  ~  10 months ago
          reply Reply

          Hi Ravi!

          Thank you so much for the feedback.

          It seems like github is having trouble displaying the entire slideshow, but if you download it I think it works? At least it did so when I tried. (There is a download-link on the right just above the presentation). 

          I will work on adding a few stories from my coaching career to make the presentation even more personal.

          As for video, I will post it as soon as the film company is done editing the videos from the last conference on which I held the presentation. Hopefully any day now. :)

          regards,

          Tobias

          • Tathagat Varma
            By Tathagat Varma  ~  10 months ago
            reply Reply

            Tobias - I was able to download and view the slides. In general, I like the theme, conetents, etc. and the topic is surely very relevant and kind of new. I am just a bit worried about 107 slides in the session. How do you plan to use the time to cover all the content in these 107 slides?

            • Tobias Anderberg
              By Tobias Anderberg  ~  10 months ago
              reply Reply

              Hi Tathagat!

              My presentation technique is to use the slides merely as illustrations and I switch slide quite often. Each slide contains very little information and I believe that switching often sets a good flow and pace that keeps the audience engaged.


  • Liked Yves Hanoulle
    keyboard_arrow_down

    Yves Hanoulle / Geike Hanoulle - PairProgramming workshop

    90 Mins
    Workshop
    Beginner

    In a way, pair programming is like riding a bicycle. You could read a book about it, you could watch videos of other people doing it, but you can only really learn it by doing it.

    This workshop not only gives people a chance to experience pair programming, but to examine that experience in depth and see how their practice can be improved.

    The “promiscuous pairing” technique is used, followed by an extended feedback session where participants analyse the strengths of pairing, and look at how they can improve their interactions with their colleagues.

  • Liked Scott Ambler
    keyboard_arrow_down

    Scott Ambler - Choose Your WoW! How Agile Software Teams Can Optimize Their Way of Working (WoW)

    45 Mins
    Talk
    Advanced

    We like to say that agile teams own their own process by choosing their way of working, their “WoW.” This of course is easier said than done because there are several aspects to WoW. First, our team needs to know how to choose the appropriate lifecycle for the situation that we face. Should we take a Scrum-based approach, a lean/Kanban-based approach, a continuous delivery approach, or an exploratory/lean startup approach? Second, what practices should the team adopt? How do they fit together? When should we apply them? Third, what artifacts should the team create? When should they be created? To what level of detail? Finally, how do we evolve our WoW as we experiment and learn?

    There are several strategies that we could choose to follow when we tailor and evolve our WoW. One approach is to bootstrap our WoW, to figure it out on our own. This works, but it is a very slow and expensive strategy in practice. Another approach is to hire an agile coach, but sadly in practice the majority of coaches seem to be like professors who are only a chapter or two ahead of their students. Or we could take a more disciplined, streamlined approach and leverage the experiences of the thousands of teams who have already struggled through the very issues that our team currently faces. In this talk you’ll discover how to develop your WoW without starting from scratch and without having to rely on the limited experience and knowledge of “agile coaches.”

  • Liked Ellen Grove
    keyboard_arrow_down

    Ellen Grove - Asking Over Telling: Using Humble Inquiry to Build Great Teams

    90 Mins
    Workshop
    Intermediate

    More asking, less telling. As an agile leader, adopt the approach of humble enquiry to build relationships, increase trust and collaboration, and deal with the challenges of organizational transformations.

    "Humble enquiry is the fine art of drawing someone out, of asking questions to which you do not already know the answer, of building a relationship based on curiosity and interest in the other person." - Edgar H. Schein

    Working in an agile way asks us to rethink how we relate to each other as we tackle complex problems and challenge the traditional structures of our organizations. Humble enquiry - the art of asking instead of telling - is a critical skill for agilists who seek to improve collaboration and address difficult problems head on. Inspired by Edgar H. Schein's book 'Humble Enquiry, this workshop will teach you the fundamentals of how to do more asking and less telling. Through mini-lectures and interactive exercises, we'll discuss the different types of questioning, consider the forces around and within us that inhibit our ability to ask instead of tell, and examine how this powerful technique can improve collaboration within agile teams as well as help to address some of the challenges of agile transformations.

  • Liked Woody Zuill
    keyboard_arrow_down

    Woody Zuill - Mob Programming and the Power of Flow

    45 Mins
    Talk
    Beginner

    Five people at one computer? How can that possibly be productive?

    While this seems like a reasonable question, it's not easily answered - until we begin to understand the power of flow.

    Mob Programming grew from the quest of one team to learn how to work well together. Once we started We almost immediately noticed that working this way provided better results in a variety of ways:

    • We were getting more done, and they were the more important thing
    • The quality of our work was increasing dramatically
    • Our Knowledge, skills, and capabilities were improving rapidly
    • And all while we were having a lot of fun as well!

    While we noticed these benefits and more, and it was clear this was in a large part due to working well together throughout the day - we didn't have an understanding of why this was working so wonderfully for us.

    A hint came early on when we recognized we were achieving a one-piece flow - but we didn't realize the importance of this until we started exploring the meaning and power of "flow".

    In this presentation, we'll share the results of that exploration, and see if we can get a better understanding of Mob Programming and the power of flow.

  • Liked Rashina Hoda
    keyboard_arrow_down

    Rashina Hoda - Becoming Agile vs Doing Agile (Research Talk)

    Rashina Hoda
    Rashina Hoda
    Sr. Lecturer
    University of Auckland
    schedule 11 months ago
    Sold Out!
    45 Mins
    Talk
    Beginner

    After 20 years since the manifesto, the latest state of agile reports more than 80% of organizations as "still maturing" in their agile practice. As agile methods expand beyond small teams and software itself, we are still struggling to answer these questions:

    • Why is it that some teams are more 'agile' than others even though they all claim to be practicing agile methods?
    • What all dimensions need to change as teams, managers, and entire organizations attempt to become agile?
    • How do these dimensions interact with each other?
    • Overall, what does it take to become agile and how does that differ from doing agile?

    This talk is based on my original theory of becoming agile developed from 10+ years of industrial research of agile practice in New Zealand and India, which received the distinguished paper award at the IEEE/ACM international conference on software engineering (ICSE), in 2017.

    In this session, I will explain the key dimensions that need to transition during agile transformations, using industrial examples, and highlight what you can do to progress beyond simply doing agile, to harness the most from your agile transformations.

    This keynote will add a unique research perspective to the conference program, sharing agile research in an industry-friendly format and delivery style.

  • Liked Jutta Eckstein
    keyboard_arrow_down

    Jutta Eckstein / John Buck - Using Beyond Budgeting and Sociocracy for agile-friendly performance appraisals

    90 Mins
    Workshop
    Intermediate

    There are many suggestions dealing with Agile-friendly performance appraisals, which promise to rely on trust, honesty, respect, safety, and servant leadership. The Agile Manifesto does not address performance appraisal although it does generally mention regular and frequent feedback, which can also be applied to performance evaluation. Two related methods, Beyond Budgeting and Sociocracy, offer interesting approaches to agile performance review. In this session we want to present these two different performance appraisal approaches, how they're are supported by the values of BOSSA nova (short for Beyond Budgeting, Open Space, Sociocracy & Agile) and want to invite the participants of this workshop to discuss the synthesis of the two approaches.

    This session looks at several real-world examples from actual companies including Accenture, Equinor, and Google.

    The first principle of Beyond Budgeting asks to “engage and inspire people around bold and noble causes; not around short-term financial targets,” the eleventh principle advocates: “Evaluate performance holistically and with peer feedback for learning and development; not based on measurement only and not for rewards only.” Thus, the main strategy of Beyond Budgeting is to separate (financial) bonuses from performance evaluation and to use relative and not fixed targets as a foundation for the evaluation.

    Sociocracy suggests holding 360 degree in-person meetings. The person being reviewed should request it when needed, not just on a rigid annual basis, and perhaps not just once in the year. In the 360 degree meeting, the organization itself can be critiqued in the review - “the way we organize is causing performance problems.” Similar to Beyond Budgeting there is a focus on the vision and mission of the specific department as well as the overall company as a source of inspiration and motivation. The output of the performance review meeting should be a development plan that the immediate group of supervision, peers, and subordinates consent to.

    Based on BOSSA nova, we invite participants to dive into what Beyond Budgeting and Sociocracy combined offer for performance appraisals. Participants will take away insights that they can use in their organizations.

  • Liked Jutta Eckstein
    keyboard_arrow_down

    Jutta Eckstein - CD – Continuous Delivery and Cultural Difference

    20 Mins
    Talk
    Intermediate

    DevOps and continuous delivery is typically elaborated technically - what kind of tools, technologies, or skills are necessary for being able to deliver continuously. Often it is forgotten that continuous delivery requires also a culture change - in development, operations, marketing, sales, and not least for the customer.

    This can be recognized for example, that although it is technically possible for a team to deliver continuously, but it seems that this delivery isn't welcomed. This means the actual system will not be directly used.

    Therefore, in this session by taking into account the necessary cultural change, I want to answer the question how to implement continuous delivery successfully and what kind of pitfalls you need to be aware of when doing so.

  • Liked Alex Sloley
    keyboard_arrow_down

    Alex Sloley - The End is Nigh! Signs of Transformation Apocalypse

    Alex Sloley
    Alex Sloley
    Alex Sloley
    schedule 11 months ago
    Sold Out!
    45 Mins
    Talk
    Advanced

    How can an Agile Coach figure out when an Agile “Transformation” is going wrong? Are there signs that they might see, heed, and take action upon? Of course, there are!

    Hindsight is 20/20, but in the moment, these warning signs can be hard to see. Let’s explore some of the more common, and frightening, warning signs that your Agile “Transformation” might be exhibiting. We will discuss transformation provider types, frameworks, keywords, and other anti-patterns that might be signs that THE END IS NIGH.

    This session will review common themes and help familiarize you with the warning signs. Armed with this new knowledge, you will be able to plan as appropriate, to help navigate your organization through potential impending doom.

  • Liked Vincent FUCHS
    keyboard_arrow_down

    Vincent FUCHS - Keeping hundreds of code repositories consistent, and staying sane !

    Vincent FUCHS
    Vincent FUCHS
    Technical architect
    Societe Generale
    schedule 11 months ago
    Sold Out!
    20 Mins
    Demonstration
    Intermediate

    With the move to microservices architecture, a lot of teams end up managing dozens of code repositories (vs just a couple before), and some tasks that were done quickly manually are now becoming very time consuming : consistency of the repositories, and eventually of your platform, gets impacted, making it more and more difficult to manage.

    Surely, there must be some tools existing to take care of boring tasks like finding where a given dependency is used, and upgrade it automatically (this is just an example)... Well actually, we didn't find anything, so we implemented them ourselves and made them available for everyone !

  • Liked Yves Hanoulle
    keyboard_arrow_down

    Yves Hanoulle / Geike Hanoulle - Real options

    45 Mins
    Talk
    Advanced

    We live in a world of "getting to yes" or "a positive no"
    Yet the world is no black & white.
    I live in a world of options. I like to say yes to all the options and only decide about an option at the last responsible moment. In this talk we will teach you to do the same.

    Real options is one of these agile tidbits that is applicable to all aspects of life.
    - a real option has a value
    - a real option expires
    - a real option has a cost

    In this talk we will give you examples that will teach you how to apply real options to your life and projects.

  • Liked Gabor Devenyi
    keyboard_arrow_down

    Gabor Devenyi / Alex Sloley - The magic number is 10

    45 Mins
    Talk
    Beginner

    Why are Agile teams supposed to be small? How big are they supposed to be? Most agilists tend to agree that a team of ten people works well.

    But what is it about the number 10 that makes it the “magic” number?

    Since the start of human evolution, people formed groups to be more effective. Whether it was the hunt for a mammoth or going to war, working in teams ensured a greater chance of success.

    There have been various researches from Dunbar’s paper through the Scrum Guide to military formations about the ideal number of people in a team.

    We’ll discuss the historical, scientific and cultural reasons why 10 seems to be the magic number of forming effective teams.

    Does the number of team members really matter? Is 10 really the magic number. You will get an answer that will help you to create effective teams with the right amount of people.

  • Liked Shane Hastie
    keyboard_arrow_down

    Shane Hastie - Being Agile in a Remote Team

    90 Mins
    Workshop
    Intermediate

    In this interactive session Shane discuss his experience working in a distributed, virtual organization which is founded on an Agile Mindset. The challenges of maintaining agility when remote, the ways the ICAgile team have consciously designed their team and organization culture and provide actionable advice based on real experience on how to maintain collaboration, teamwork and live the agile values in a remote only organization.

    ICAgile is a global, virtual organisation working with partners across over 100 countries spanning almost every timezone. There is no single corporate office and the ICAgile team is spread across seven locations in three countries. We have managed to build a strong collaborative culture and a truly safe working environment focused on outcomes rather than activities, holding each other to account and being really effective and productive while having a joyful workplace.

  • Liked Vivek Ganesan
    keyboard_arrow_down

    Vivek Ganesan / Rejikrishnan Rajan - Reinventing DevOps Practices for Blockchain Applications

    90 Mins
    Workshop
    Intermediate

    With the arrival of distributed applications that run on Blockchain, it is essential to rethink some of the basic aspects of DevOps. Few things that we take for granted in DevOps area are either irrelevant, impossible or too costly for blockchain applications. Join us to explore the changes that the blockchain apps bring to the DevOps arena, using a hands-on demo of a sample blockchain app.

  • Liked Yves Hanoulle
    keyboard_arrow_down

    Yves Hanoulle / Geike Hanoulle - Tips from the agile trenches

    45 Mins
    Talk
    Advanced

    The agile manifesto was created in 2001. That is (when I write this) 17 years ago, (when the conference takes place 18 years ago.

    At age 18, adult life begins. At 18 we think we know it all. Life is easy. Yet we quickly find out that easy, isn't always simple. Yves has gathered tips from many agile friends that are working in the trenches. Tips that will help your agile life.

  • Liked Yves Hanoulle
    keyboard_arrow_down

    Yves Hanoulle / Geike Hanoulle - The power of habits

    90 Mins
    Workshop
    Beginner

    agile, devops is all about repeatable, predictable good behaviors.
    Individuals have habits, teams and companies have routines.

    This talk is based on a famous book about creating habits. I took what I learned from the book, and mixed this with agile ideas about teamwork.

    If you have a bad habit you want to change? ==> Come to this session.
    If you don't have habits and want to learn how to create good habits? ==> Come to this session.
    If you want to understand what is the value of habits? ==> Come to this session.



  • Liked Jen Krieger
    keyboard_arrow_down

    Jen Krieger - A Culture of Openness

    Jen Krieger
    Jen Krieger
    Chief Agile Architect
    Red Hat
    schedule 11 months ago
    Sold Out!
    45 Mins
    Talk
    Beginner

    The “Agile mindset” was introduced to the software development community in 2001 in an attempt to foster freedom in the way that we work together. Its intent was to encourage organizational change that focused on people, collaboration and culture.

    But words on a screen don’t mean much in practice, especially if the people using them don’t - or won’t- understand their intent. How can individuals, teams and companies learn to correct these mistakes and break free from the challenges associated with change?

    Jen will share practical advice on effective Project Management, Agile Transformation, and getting things done– all told through the stories of her own journey towards something better at Red Hat.

  • Liked Yves Hanoulle
    keyboard_arrow_down

    Yves Hanoulle - The power of the junior

    45 Mins
    Talk
    Beginner

    The speed of the team, is not the speed of the fastest, smartest person. Its the speed of the slowest. That is why in a lot of team, people don't like juniors. They think they slow them down.
    In this session I want to show you the power of the junior. Why you need them.
    Everyone that goes to a new team is a junior, everyone who learns a new technology becomes a junior.
    At many moments in our life we are a junior.

    Some experts are afraid of being again a junior, and that fear can block them from learning new stuff, which eventually will make them loose their experts status.

    In this session I will show you what is the power of juniors, and why we should all embrace our internal junior.

  • Liked Oana Juncu
    keyboard_arrow_down

    Oana Juncu - Innovate Organisations - From Ego To Eco

    Oana Juncu
    Oana Juncu
    Agile Business DJ
    cOemerge
    schedule 10 months ago
    Sold Out!
    90 Mins
    Workshop
    Intermediate

    Because the productivity driven world of the industrial era encouraged us to divide in order to control, we live today in disconnection. Disconnection from ourselves, from our team, from our society. This workshop proposes to shift the paradigm and innovate using "reconnection" principles as defined by the Theory U. To understand the way theory U operates at a people group level, a concrete framework, "Process Work", by Arnold Minundell, will be experienced.

    The workshop is a hands-on experiment of impact of change on each member of a team, including the game change player. The different stages of transformation defined by the Theory U will be experimented via Process Work, and is equally inspired by the model of living systems.

    The ultimate intention of this workshop is to offer participants a learning experience of emergent co-created innovation , via quality listening, and the ability to redirect perspective

  • Liked Yves Hanoulle
    keyboard_arrow_down

    Yves Hanoulle - 20 coaching tips pecha kutcha

    20 Mins
    Talk
    Intermediate

    This is a pecha kutcha with 20 slides where I share 20 coaching tips.

  • Liked Pradeep Kellangere
    keyboard_arrow_down

    Pradeep Kellangere / Zaheerabbas Contractor - Implementing Rapid and Repeatable Pipeline for an Enterprise

    45 Mins
    Case Study
    Intermediate

    Enterprises and their individual feature teams are in a rush to build DevOps Pipelines with all the right reasons.

    While central teams are provisioning tools to be consumed at Enterprise level, individual feature teams are focusing heavily on building pipelines instead of building and enhancing business priorities.

    This results in "duplicate pipelines” solving the same problem of automation for build, test, package, infra, deploy and release using the given toolsets. - This results into duplication of efforts and redundancy.

    We intend to share our approach to build a pipeline enabled to for polygot programming languages and consumption patterns supporting various areas including.

    • A single click to deploy the complete pipeline infrastructure and app pipeline
    • Support multiple cloud deployment (AWS, Azure, etc…)
    • Adoption of open source tools
    • Clustered or non-clustered infrastructure deployments

    We will also emphasize on the implementation experience of the advanced Engineering practices in the area of immutable infrastructure, Chaos Engineering, blue-green/canary deployment.