Dynamic Reteaming: The Art and Wisdom of Changing Teams

location_city Bengaluru schedule Mar 7th 02:45 - 03:30 PM place Mysore Hall 1 people 34 Interested

Who says you need "stable" teams in order to build a successful software company? While the addition or removal of one person from a team means you have a "new team", there is a myth out there about "stable" teams. When your team compositions change it doesn't mean you're doing it wrong - it could be the secret to your success. Different companies have thrived through reteaming - the act of moving people around teams in different ways. In this talk I'll go over the what, why and how of reteaming and will share stories from different companies who are living this reality.


Outline/Structure of the Talk

1. There's a thought in the software industry that teams should stay the same in order to be successful.  I am debunking this myth. In fact, there are numerous companies who live the reality of dynamic reteaming - where team members switch from team to team for a variety of reasons and at a variety of cadences.  I've interviewed several famous companies who do this for my Dynamic Reteaming book which is available on LeanPub.

2. I will order this talk with examples of reteaming patterns that I have discovered in my research. These are real, true stories from our industry. These stories are categorized into the following sections: reteaming for company growth, for the fulfillment of team members, for code reasons, and for of liberating team members from undesirable/unsafe situations.

3. I end the talk with how to make dynamic reteaming easier in your company. It only takes the addition or loss of one team member to have a reteam.  This happens at every company. So you might as well get good at reteaming.  I will share several practices to help you do that.


Learning Outcome

After this talk the participants will look at their teams in a different light.  They will learn that:

-you have a new team system when you add or remove one team member.

-there are signals to pay attention to for splitting up teams into smaller teams.

-they can foster new innovation by isolating teams and giving them process freedom.

-reteaming is connected to learning and fulfillment of team members. Keeping people in the same team can stagnate their growth and could be a retention risk. 

-reteaming is a great strategy for spreading knowledge across teams.

-there are specific patterns to use when you have one new person join on a day versus 20 people in a day.

Participants will walk away with my reteaming cheat sheet which summarizes more than 20 unique patterns derived from my research and pointers to further reading.

Target Audience

This talk is geared at people who influence teaming and reteaming decisions at their companies such as managers, VPs, CTOs and team members.



schedule Submitted 4 years ago

Public Feedback

    • Joshua Kerievsky

      Joshua Kerievsky - Modern Agile

      Joshua Kerievsky
      Joshua Kerievsky
      Industrial Logic Inc.
      schedule 4 years ago
      Sold Out!
      45 Mins

      Genuine agility is enormously effective in helping us achieve our dreams. The trouble is, Agile has grown into a complex tangle of roles and rituals, frameworks and tools, processes and certifications. We need a return to simplicity. Modern Agile is here to help.

      Designed for people in many domains (not just IT), Modern Agile is defined by four guiding principles:

      • Make People Awesome,
      • Make Safety a Prerequisite,
      • Experiment & Learn Rapidly and
      • Deliver Value Continuously.

      Understanding and deeply practicing these four principles will help you get better results faster.

      In this talk I’ll share how these four principles power world-famous companies and how they can help you work with greater speed, simplicity, safety and success.

    • 45 Mins

      Better. Faster. Cheaper. Many IT organizations are constantly seeking the "best" practices that will deliver those characteristics, and the fact that they continue to search indicates they haven’t found them yet.

      It could be they are looking in the wrong place. Most efforts around achieving better, faster, cheaper center around becoming ultra efficient.

      Effectiveness may just be the better target.

      Join Kent McDonald to explore the difference between efficiency and effectiveness and learn three simple, yet powerful, techniques that he has found can help teams be more effective. You’ll learn how to:

      • Build a shared understanding of the problem you are trying to solve
      • Establish clear guard rails for distributed decision making
      • Measure progress based on outcome, not output

      Along the way he’ll share stories about how he has used these techniques and help you figure out when these techniques may work in your situation.

      You may be able to get faster and cheaper with efficiency, but in order to get better outcomes, you need to be effective. Come to this session to learn how.

    • Kent McDonald

      Kent McDonald - Examining the Product Owner Role

      45 Mins

      As with everything else related to agile, the nature of the Product Owner role, and whether it is needed or all, depends a great deal on context. As teams discover this, it leads to some common questions:

      • What do Product Owners Really Do?
      • Do we even need Product Owners?

      Join Kent to examine the Product Owner role and attempt to answer the above questions. He’ll  share his experiences and give you a chance to share your perspectives with each other. By the end of the session, you'll have more insight into the Product Owner role and how it applies (or not) to your situation. After all, the only consistent answer to the above questions is “it depends”.

    • Diane Zajac

      Diane Zajac / Doc Norton - Making Sense of Sense-Making

      90 Mins

      The world as we know it is growing more complex. As we automate away those things that can be easily repeated, we leave ourselves with ever more challenging work. The way we’ve worked in the past won’t necessarily work for today’s problems… or will it? Join Diane and Doc as they explore dimensions of complexity in software development and look at how teams and leaders might adjust their behaviors (and the software they create) based on the complexity of the problem at hand.

      This hands-on, interactive workshop will provide a practical introduction to Cynefin (a sense-making framework for complexity) and show how it applies to the work we do every day as creators of software. You’ll map your own work to Cynefin and learn about applicable management styles and optimal team interactions for each of the Cynefin contexts.

    • Diane Zajac

      Diane Zajac - How Agile Helped a BA Discover Her Real Value

      45 Mins

      As companies introduce agile practices, the Business Analyst role is often left by the wayside. The title does not even exist in Scrum or other specific agile implementations, leaving many Business Analysts wondering where they fit in. But fear not! The skills of a good BA are even more valuable in an agile environment!

      Join Diane Zajac-Woodie as she tells the tale of a new agile team, struggling with no formal training, a resistant corporate culture and unwilling team members. She shares how this team benefited from the communication, collaboration & facilitation skills of an experienced BA. She then highlights specific shifts that Business Analysts can make in order to help their own team’s transition. These include using story maps and writing executable requirements, just in time.

      Embracing their new roles, BAs can also encourage team members to cross role boundaries. This leads to new skill acquisition and a more cohesive team, which ultimately leads to higher quality software.

    • Diane Zajac

      Diane Zajac - Explore Your Customers' Needs with Empathy Mapping

      45 Mins

      “Success is not delivering a feature; success is learning how to solve a customer’s problem.”  ~ Scott Cook, founder of Intuit*

      If this is true, then the next question is: what is your customer’s problem? Unfortunately there’s no magic trick to figure out what customers need. But there is a simple technique that can help you gain insights and build empathy for them.

      Empathy mapping is a simple activity that you can facilitate with stakeholders (or anyone responsible for delivering products and services) to build empathy for your end users. It allows you to explore what your customers see, hear, say & do, as well as consider what they think and feel. This leads to insights about their pain and potential wants.

      Because this is done collaboratively, using silent brainstorming, everyone on the team contributes to a shared understanding of the customer. So not only do you build empathy, but you also create alignment within the team and among stakeholders. And that can only help you be more successful. 

      *as quoted in The Lean Startup, page 66