This story starts with a goal. The company wanted teams to “build and run” their own applications. How could they put that change into practice? Willem-Jan started by suggesting a full, cross-functional Scrum team for a product. That got accepted, but what came next was bold, unexpected, and kick-started the cultural change needed to bring the company to the next step in their transformation.
As a Scrum Master and writer for Serious Scrum, Willem-Jan is passionate about helping people understand what it means to work in a complex Product Environment. Which is how he likes to talk about Scrum.
When this project started, there were multiple teams involved that had not yet collaborated effectively. On top of that, the project was very challenging for everyone involved. Justin worked with the teams to help them realize that their shared challenge could be resolved if they were able to change their approach to collaboration. In this episode, we share a great story of transformation at the team level that yields many insights for changes across the whole organization.
A Product and Agile Coach with product management experience ranging from payments to enterprise custom build. Justin has hosted a small series on Product Management and another series on Being a Scrum Master.
Justin has also pioneered a new form of Canvas to help bring teams together. All of this information can be found on his blog: http://www.ponolabs.com/labs/
Sometimes, we can succeed so well with the teams, that the teams start feeling that the organization as a whole is not ready for them. In this episode, we talk about a team that was pushing the boundaries and getting push back from the organization. We discuss the different approaches Dimitri took to help the organization and the team find a common agreement and a new way of working.
Dimitri is a business, transformation, and agile coach and a repented project manager. Dimitri works side by side with executives, managers, and teams to uncover better ways of developing software and delighting customers.
Many Scrum Masters are familiar with the anti-pattern where managers want to “own” the team and are very directive. To the point of telling team members what they can, or should not work on. In this episode, we talk about how those managers can also find value in Agile approaches. Saritha shares a story about personal transformation in a waterfall organization that wanted to go Agile.
About Saritha Rai
Saritha has been working in the IT industry for 13+ years and is an adaptable and constant learner. She has over a decade of experience in software development and is passionate about training, guiding and coaching people to have a good working environment which will result in high-quality deliverables.
There was a team where the team members and the manager did not have a good relationship. George understood this was a problem for the team, and the manger and tried to help them transform their relationship.
In this episode, we talk about how we can help teams and their managers or stakeholders build a collaborative relationship.
About George Mathews
George Mathews is a Scrum Master at SentryOne for two fully remote teams. Prior to that, he had experience as a Customer Service Representative, Operations Analyst and Finance Technical Analyst allowing him to employ a broad practical point of view as he coaches Agile teams at SentryOne.
Collaboration is one of the key aspects of focus for Scrum Masters. We are, and should always be on the lookout for way to improve collaboration in our teams, and across teams and departments. In this episode, we dive into a specific Actionable Agile Tool that aims to boost collaboration: The Internal Unconference. Gene and Jeff share their own experience organizing Internal Unconferences, and why this even may be exactly what you need to improve collaboration in your organization.
Discovering how to improve collaboration across departments
When teams work on a new product, there’s a risk that the Vision is not set, and that the Product Owner is not able to convey the reason why the product is being developed. In this episode about a big business change, we talk about the risks of a missing Vision, and why the Product Vision is an essential tool for business changes.
About Mandy Sunner
Mandy calls herself the Angel of Agile as she guards her team and stakeholders from attacks and compromises which are forthcoming in an era of uncertainty. Her Agile approaches are thought through by virtue of being a systematic thinker and keeping the customers at the forefront of development. A problem solver with many years of practical experience.
When Tony joined this organization, the mandate was to help the organization change. There were about 4000 people involved in that change. There’s no Scrum Master/Agile Coach team big enough to take on that responsibility, so they took a different approach.
Tony coaches Agile teams across the UK and currently serves as program advisor to the Scrum Alliance. His most recent client is applying Scrum and Kanban in the engineering and production of physical goods.
Tony is also in the organizer team for the Scrum Gathering in sunny Lisbon this year, and he’s busy working with a great team of volunteers to review and build a program of great talks and workshops.
As Scrum Masters, we work constantly with change. It is therefore critical to establish our own approach to being a change agent. In this episode, Olsen shares with us what he learned about the role, and the approach that works for him when working with change, and being a change agent.
About Olsen Turan
Olsen is an experienced Agile Coach and Scrum Master with a mix of Servant Leadership skills and technical knowledge acquired over his decade-long career. His background includes Ph.D. studies in Organizational Leadership, Agile Transformation and Coaching, Project Management, and Scrum Master duties.
As Scrum Masters, focusing on helping teams succeed and collaborate, we will often notice certain negative patterns before the team members realize what is going on. It is then our responsibility to help the team understand what is going on. However, that’s not always an easy process. In this episode, Sami explains how she introduced an anti-pattern to the team, how they reacted, and especially how her own calm persistence (she calls it “gentle pressure”) helped the team realize what was going on, and improve the situation.
About Sami Prentice
Sami is a Scrum Master in Denver, Colorado. She used to work in the beer industry before making the switch to Scrum Master and she is passionate about facilitating awesome meetings that don’t suck.