Are you having trouble getting inter-team cooperation going?
Is it difficult to attack issues that require people from all over the organisation?
Do you find decision making to be difficult and slow?
Do you find it hard to just knuckle down and get things done?
Do you want to remind people in your organisation how many brilliant people they work with?
In that case, you might consider running an “Internal Unconference”.
Internal Unconference is an exclusive blog post by Jeff Campbell, author of Actionable Agile Tools, a book that includes 19 practical tools with step-by-step guides for Scrum Masters. Actionable Agile Tools is now available on Amazon.
Tim was faced with a problem. How to be a leader without any formal power. All Scrum Masters and Product Owners who have felt the responsibility, but not any “line authority” have faced the same problem. You need to help move the project along, but you can’t tell people what to do!
In this episode we explore the concept of Lateral Leadership how it can help you as a Scrum Master or Product Owner.
One of the tasks we take up as Scrum Masters is to help to change the wider organization. Starting with the teams that our team interacts with. Jason explains how he is able to detect and work with the teams outside that are ready and willing to help change the organization.
“That’s not Agile!” is a common phrase we hear when a team does not want to compromise their view of agile in order to improve the collaboration with external stakeholders. Although that phrase may be true, we as Scrum Masters must look beyond the surface and understand how to help teams collaborate better with stakeholders.
The word team is often abused. Many teams do not meet the basic requirements of what it means to be a team, yet they are called a team, and expected to behave like a team. Woody discusses such a team and explains what are the key aspects that make a team a real team.
About Woody Zuill
Woody Zuill, an independent Agile Consultant, Trainer, Coach, and Guide and has been programming computers for 30+ years. As a pioneer of the Mob Programming approach of teamwork for software development he has been sharing presentations and workshops on Mob Programming for conferences, user groups, and companies all over the world. He is considered one of the founders of the “#NoEstimates” discussion on Twitter.
You can connect with Woody Zuill on LinkedIn or contact Woody Zuill on Twitter.
If you are interested, check the MobProgramming conference.
When we try to help teams we often forget that just because people work in the same area or are nominally called a “team” they may not be a real team. In this episode Ryan relates the story of a team that imploded because of the anti-patterns inherent to teams that aren’t really teams.
We also refer to the Super-Chicken Ted talk that explains some of the anti-patterns that destroy team’s effectivity. We also talk about the book Get Rid or Performance Appraisals by Luis Goncalves.
About Ryan Ripley
Ryan Ripley loves helping people do great work. He is a servant leader at heart and is passionate about fostering safety and trust in the workplace. Ryan created the Agile for Humans podcast to put the focus back on the individuals and interactions that make agile work.
You can link up with Ryan Ripley on LinkedIn and connect with Ryan Ripley on Twitter.
Ryan also hosts a popular Agile podcast: Agile for Humans. Be sure to check it out!
The systems view of the Scrum Master work is not limited to one system. We work with the teams which are one system, but we also work with the team of teams. How the teams interact and cooperate is a system in itself. Enabling cooperation between Scrum Masters can be a very effective way to work with the larger systems.
Retrospectives are one of the key ceremonies for teams. Well prepared and executed retrospectives can take a team from ordinary to extraordinary and can help teams avoid the anti-patterns that so often lead to difficult problems down the line.
One of the resources that Jiri uses when preparing his retrospectives is Getting Value out of Agile Retrospectives.
The Product Owner role can enable to make the work of the team very difficult. In this episode Jiri talks about how important the Product Owner role really is and how to help teams align. We also talk about aligning remote teams discussing some of the techniques that Jiri uses to have remote teams collaborate effectively.
Sometimes we enter organizations and teams where everybody talks about how messy things are. This language prevents the people in that organization from seeing the situation clearly and does not allow them to move on. Alberto uses many techniques to help teams and organizations recognize and remove the “messiness” from their lives. In this episode he explains how he does that.
About Alberto Brandolini
Alberto looks at himself as sit at the intersection between the Agile/Lean community and the Domain-Driven Design community. Sometimes, he says, the solution is to write better software, sometimes the solution is to take a big modelling surface and see “the problem” in all its magnificence, sometimes the solution is to have a beer.
You can link up with Alberto Brandolini on LinkedIn, or connect with Alberto Brandolini on Twitter.