Steffan Surdek is a senior consultant and agile coach at Pyxis Technologies. Steffan has worked in IT for more than seventeen years and worked with teams distributed around the world. In the last few years, Steffan was an agile trainer and coach in large companies such as IBM and the TD Bank Group and spoke at many conferences and user groups about agility with distributed teams.
Steffan is co-author of the book « A Practical Guide to Distributed Scrum ».

Canada
2012 sessions
The Five Dysfunctions of a Distributed Team View session page
English session - Introduction
This talk is what happens when you combine the knowledge in Patrick Lencioni's book "The Five Dysfunction of a Team" with some of the ideas presented in the book "A Practical Guide to Distributed Scrum" and the experiences Steffan Surdek acquired working with distributed teams in the last five years.
Last fall, Steffan read Lencioni's book and quickly realized that he could now give a better explanation to many situations he faced when working with distributed teams. In this talk, participants will learn to relate these dysfunctions to the challenges that come with being part of a distributed Scrum team. They will also come out with some suggestions and ideas on how they can address theses issues to make their distributed teams work more smoothly together.
Effective Collaboration in a Sprint View session page
English session - Intermediate
Teams face many challenges during a Sprint. Some of them, such as requests that seemingly come out of the blue or getting
timely answers to questions from the Product Owner, are common to both collocated and distributed teams. Others such as
communication and time zone challenges are more often found with distributed teams.
In this talk, Steffan Surdek discusses different challenges teams may face during a Sprint and presents suggestions teams can use to help make their Sprints run more smoothly.
Content high-level overview:
- Handling language differences
- Handling cultural differences
- Handling teleconferences
- Using documentation to communicate better
- Valuing the whole team
- Promoting Transparency
- Effective Daily Scrums
- Handling new requests
- Handling maintenance issues
- Getting timely answers