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
What is Business Agility? In a time where it seems that every company wants to adopt Agile, there’s also the dark side of Agile: the belief that it only affects “people in the IT department”. That could not be further from the truth.
In this episode, we have Evan Leybourn sharing what Business Agility is about, and why it matters for your organization.
We all face silos in our organizations, and sometimes even in our teams. Henri did just that, and found a way to replace those silos with collaboration. Listen to hear how Henri removed the silos, step by step.
About Henri Karhatsu
Henri is a consultant at his own company Karhatsu IT Consulting in Helsinki, Finland.
He is a very experienced software developer that has worked for and with many clients over his career. He’s also been exploring how to improve our industry of software development and sharing his learnings in his blog.
You can connect with Henri Karhatsu on LinkedIn, and reach out to Henri Karhatsu on Twitter. Henri Karhatsu’s blog.
It is critical that we build a model that allows us to think about the whole organization. And use questions to investigate the system. As Sean put it “questions communicate value”.
About About Sean Dunn
Sean is an Enterprise Agile Coach with IHS Global. He has been involved with agile development for 8 years as a developer, product owner, and agile coach. Prior to his exposure to agile development Sean spent 13 years in the Canadian Army. In fact, Sean is known to point out that the Army is far more agile than most people think.
That background in the Canadian Army influenced his view of Leadership and the role of Leadership in creating and developing great teams.
You can connect with Sean Dunn on LinkedIn, check out Sean Dunn on the Scrum Alliance or email him at firstname.lastname@example.org.
Check out Sean Dunn’s blog on leadership.
Tim’s story is about a team that is changing an organization. He discusses how believing you can, and wanting to improve the world can sometimes lead you down the wrong road. And he suggests a few rules to take into account if you want to survive the change process as a team.
About Tim Bourguignon
Tim likes to describe himself as a full time geek, agile developer and BS hunter. He was born in France, raised as a European child and currently lives in Germany where he juggles with software development and Scrum Mastering. When he’s not in front of a computer, you’ll find him behind a camera, in his running shoes or with his wife & son… of course never in that order!
You can connect with Tim Bourguignon on twitter or visit Tim Bourguignon’s website to see what he is up to.
How do we help organizations to recognize the value that scrum teams can bring, and the obstacles they face in the process? Stephen Thomas shares his recipe and describes a few ideas of how the retrospectives can be an effective practice to help organizations evolve and get better.
Stephen’s recipe for organization improvement:
Help the teams understand their progress with a physical (as opposed to digital) and visual burndown (colorful if possible).
Write the principles on the wall and make sure people see them regularly. Point to them when needed.
Have lots of wall space for teams to use and create their shared view of their work.
Help start and facilitate organization-level retrospectives, because improving one team is not enough for lasting change.
Make the team independent
Before implementing all of this, make sure that the organization has the necessary knowledge to work in an agile manner, helping organize training if needed, and working with stakeholders regularly.
About Stephen Thomas
Stephen has been managing digital projects since 2004. Initially specialising in e-learning, he now looks after multiple projects that range from rapidly produced native apps to large-scale social networks. Based in Oxford, he is also one of the founders of the DOPM meetup.
You can connect with Stephen Thomas in LinkedIn, and follow Stephen Thomas on Twitter.