Setting up teams to work collaboratively is one of the challenges that organizations go through when adopting Agile. The functional team setup (all DBAs, all testers, all windows devs together, etc.) is not acceptable for teams that want to quickly develop and deliver products and services to the market. But neither is it possible to have all possible skills (sometimes 10’s of skills) in one team because organizations simply don’t have that many people with certain skills.
In this episode, we talk about the possible team topologies, and how each of those affects our ability to deliver in different organizations.
How we set up teams directly affects the quality of the software teams deliver
Product Owners have an impossible job! I know, I’ve been a Product Owner. And even worse, a Product Manager transitioning to Product Owner! And even worse! I was also the Project Manager. Geeez! When I look back I am amazed I survived that phase of my career.
Here’s the kicker, that was the best time of my Agile adoption journey. I got to see my ideas come to life so quickly! And have a concrete business impact (the product we delivered went on to generate 10 Million Eur in sales a little over 3 years).
My Product Owner journey towards Agile was not easy! Let me tell you how I survived that stressful time, and lived on to learn a lot from the experience.
Amitai tells us the story of a team that was too large, and had an “inner team” that prevented anyone from influencing the larger team. We discuss the meaning, and impact of power structures inside teams that tend to perpetuate self-destructive behaviors.
Today we play one more Agile in 3 Minutes episode that talks about certain topics that are in line with the story Amitai shared with us. Today’s Agile in 3 minutes episode is episode #15, titled “Influence”.
About Amitai Schlair
Amitai is a Software development coach, and legacy code wrestler, non-award-winning musician, award-winning bad poet, and creator of Agile in 3 Minutes, which is a great podcast about what Agile really is about. A must listen for anyone interested in Agile Software Development.
You can link with Amitai Schlair on LinkedIn and connect with Amitai Schlair on Twitter.
Many will think that having daily standups + iterations + user stories is enough to “do” Scrum. Well, that can be very far from what Scrum is about. In this episode we discuss some of the most critical anti-patterns in teams that end up under-performing or even worse: dis-integrating.
We also mention two very important books for every scrum master: Agile Software Development by Cockburn, and Team of Teams by McChrystal.
About Matthew Heusser
Matthew Heusser is the co-author of Save our Scrum, co-chair of the enterprise track at Agile2015, And he is also an author at CIO.com. Matt Software is a delivery consultant/writer and Collaborative software geek since before it was cool.
You can find Matthew Heusser on LinkedIn, and connect with Matthew Heusser on Twitter.
“Nothing ever changes here” is a team anti-pattern that sometimes takes over and freezes team behavior. Teams experiencing that anti-pattern will often complain, be discouraged, but will not take action to change their situation. How to help teams like that? Antti tells us a story of a team that was in that situation and what he and his colleagues did to change the situation and save the project.
About Antti Tevanlinna
Antti is an agile practitioner, who got started with agile in my own very first Agile project way back in 2004. He’s been through all kinds of roles, from team member, to management, to customer-facing roles.
You can connect with Antti Tevanlinna on twitter, and check Antti Tevanlinna’s blog.