How to be balanced in a software development team

Could a leaderless team build better software? Discover a model where shared ownership replaces hierarchy to ship higher-quality products, faster.

#1about 5 minutes

Defining the difference between a group and a team

A team is a group of people who combine their efforts and communicate effectively to achieve a shared goal, unlike a group that just coexists.

#2about 4 minutes

The structure and roles of a balanced team

Balanced teams consist of cross-functional roles like developers, product managers, and UX designers who share leadership and responsibility without a formal leader.

#3about 2 minutes

Core principles for operating as a balanced team

Key principles include extreme programming, constant communication, joint decision-making, continuous improvement, and prioritizing fun to foster a healthy environment.

#4about 5 minutes

Practices for sharing knowledge and ownership

Balanced teams use pair programming, collaborative design reviews, and joint backlog prioritization to prevent knowledge silos and a hero culture.

#5about 3 minutes

Maintaining team connection while working remotely

Remote teams can foster connection using dedicated communication channels, daily greetings, and open video calls to simulate spontaneous office interactions.

#6about 6 minutes

Agile ceremonies that structure the workflow

The team uses a cadence of daily standups, backlog reviews, team-led retrospectives, and iteration planning meetings to stay aligned and organized.

#7about 1 minute

Integrating fun to improve team performance

Scheduling short, weekly team events for fun and games helps build morale and leads to more open and effective retrospectives.

#8about 3 minutes

Questions to assess your team's balance

The talk concludes with a set of self-reflection questions to help you determine if your team operates with trust, shared ownership, and open communication.

From learning to earning

Jobs that call for the skills explored in this talk.