Let's build that Dream Team!

What would a dream Agile team look like? A small, collocated, cross-functional, self-organizing feature team?

Not always. There are several considerations that go into forming a team and there is no one-size-fits-all solution.

While the above described team attributes may help us be agile, there may be other conflicting goals which may nudge us in a different direction.

For anyone trying to design and set up a team, it is important to be aware of the many possibilities and the many goals that may influence team configurations.

Through this talk and with the aid of some hands-on exercises, we will aim to throw light on various aspects of team formation and the pros and cons of the choices we make.

 
 

Outline/Structure of the Talk

  • Various aspects of team formation (size, geographical distribution, specialization etc) – 10 mins
  • Pros and Cons of various configurations (small teams Vs. large teams, co-located teams Vs. distributed teams etc) – 15 mins
  • Short exercise to create a dream team based on various scenarios - 10 mins
  • What can we do in the field to balance various goals and their influence on team configurations – 10 mins

Learning Outcome

For roles that influence team design and configuration, the session will highlight the pros and cons of conventional and unconventional choices.

The audience will be able to apply the learning in their organization to be able to truly design teams fit for their context.

This will be established in a highly interactive way and through an exercise.

Target Audience

Agile Coaches, Leaders, Scrum Masters

Prerequisites for Attendees

NA

schedule Submitted 1 year ago

Public Feedback

comment Suggest improvements to the Speaker
  • Mayuresh Deshpande
    By Mayuresh Deshpande  ~  1 year ago
    reply Reply

    I like these aspects of the submission, and they should be retained:

    • ...Thank you Vinaya, this helps. 

    I think the submission could be improved by:

    • ...
  • Mayuresh Deshpande
    By Mayuresh Deshpande  ~  1 year ago
    reply Reply

    I like these aspects of the submission, and they should be retained:

    • ...

    I think the submission could be improved by:

    • ...Ladies, 
    • the slideshare link isn't showing us the slides. Is there any other link or document that we should be looking at for the content of the presentation?
    • vinaya muralidharan
      By vinaya muralidharan  ~  1 year ago
      reply Reply

      Hi Mayuresh

       

      Thanks for your comment.

      We actually didnt have any content related to this topic ready yet. The links were meant to give a general idea about the kind of content we have created in the past, our presentation styles etc.

      However, we have created something quick and dirty just to give some idea of what we may present if selected.

      You can find those slides here - https://www.slideshare.net/vinayamuralidharan/team-formation-considerations-93257998

      Hope it helps.

      Kind Regards

      Vinaya / Carol

  • Srinivas C
    By Srinivas C  ~  1 year ago
    reply Reply

    Unrealistic, I doubt if such a topic can be covered in a short time. Seems also superficial

    • Carol Mathrani
      By Carol Mathrani  ~  1 year ago
      reply Reply

      Hi Srinivas,

      Going with Vinaya's comment, i would also like to add that we work in an environment where team formation cannot be left to the way the industry suggests and depends alot on the need of the project. The stability of the team and the cross knowledge of the team across different products and applications also is a key criteria to enable a stable team. Taking these real life scenarios we have helped the teams and projects to take team formation decisions, keeping in mind that stability of the team throughout the project lifecycle is essential. Specially in situations where knowledge and products pose a hindrance in stable teams

      Kind Regards

      Vinaya/Carol

    • vinaya muralidharan
      By vinaya muralidharan  ~  1 year ago
      reply Reply

      Hi Srinivas

      Thanks for your comment. 

      We have used similar exercises in some of the groups that we have coached, to help them come up with team configurations that would work for them. We have found it to be useful to help them reach some of these decisions.

      Also from our experience, it is not always the best fit to have feature teams for instance...or colocated teams etc. Unfortunately, we have come across several coaches who recommend small, colocated, cross-functional, feature teams irrespective of the the context and business goals. We would like to challenge this thinking.

      Your comments are welcome, as always.

      Thanks and Regards,

      Carol/Vinaya

       


  • vinaya muralidharan
    vinaya muralidharan
    Agile Coach
    Fiserv
    schedule 1 year ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    Product Owners and others responsible for creating and maintaining the Product Backlog often focus on functional items.

    With good engagement in the Backlog Management process from the Development Team and Architects, technical and architectural items also find their way into the Product Backlog.

    But what about the human-centric items related to accessibility, inclusivity, internationalization and sustainability?

    Through the talk and with the help of several supporting examples and a short exercise, I would like to highlight the importance of addressing these aspects in the Product Backlog. The examples will include examples of good and bad backlog items and design decisions.

    I will also share some tips on how Product Owners and supporting roles can work these aspects into the Backlog Management process. These will include some ideas from Design Thinking but will not be limited to that.

  • Liked Carol Mathrani
    keyboard_arrow_down

    Carol Mathrani - Batman or Justice League - A 10x developer or 100x scrum team

    Carol Mathrani
    Carol Mathrani
    Agile Coach
    Employed
    schedule 1 year ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    There are many discussions around 10x developers and the need to have one - 10x instead of a few average developers. But why do we limit ourselves to individual heroes when we can focus on building an entire team of 100x potential. Its not like we dont need the 10x developers - but our necessity lies in having the 10x build a 100x team. The building of such teams should start within the organization, from among are very good programmers, not necessarily a 10x. As we propagate in scrum - a cross functional team that creates a working software together, with key characteristics of accountability, ownership and self managing. building them with a 100x scrum team concept