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

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

 
 

Outline/Structure of the Talk

  1. What is a 10x developer
  2. Qualities of a 10x developer
  3. Moving from individuals to teams
  4. Key characteristics needed to be inculcated or identified in a 100x scrum team member
  5. Recipe to build a 100x scrum team
  6. Challenges to look out for
  7. Mindset change for the organization when it comes to a 100x scrum team -

Learning Outcome

  1. Focusing on the team and not individual heroes
  2. Building pride within teams
  3. Organizations focus/shift of mindset to long term investments - scrum team
  4. Leadership need to build the potential individuals into a 100x scrum team
  5. Quicker way to inculcate the characteristics of self managed, empowered, innovative scrum team

Target Audience

Developers, Scrum Masters, Managers, Leaders, Coaches

Prerequisites for Attendees

  • Basic knowledge of Scrum and Agile
  • Team Formation - Tuckman model
schedule Submitted 2 years ago

Public Feedback


    • vinaya muralidharan
      vinaya muralidharan
      Agile Coach
      Fiserv
      schedule 2 years 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.

    • vinaya muralidharan
      keyboard_arrow_down

      vinaya muralidharan / Carol Mathrani - Let's build that Dream Team!

      45 Mins
      Talk
      Advanced

      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.