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
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.
Agile Coaches, Leaders, Scrum Masters
Prerequisites for Attendees
schedule Submitted 5 years ago
People who liked this proposal, also liked:
vinaya muralidharan - Does your Product Backlog include these?vinaya muralidharanAgile CoachFiserv
schedule 5 years agoSold Out!
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.
Carol Mathrani - Batman or Justice League - A 10x developer or 100x scrum teamCarol MathraniAgile CoachEmployed
schedule 5 years agoSold Out!
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