As Agile and Scrum get adopted in more and more organizations, there’s a need to help organizations replace the old coordination mechanisms, like the Program (several projects coordinated via a centralized organization). In this episode, we talk about coordinating at Portfolio level many Scrum teams. We also share the steps to get that implemented at Elena’s company.
About Elena Popretinskaya
Elena considers herself a lifetime learner (she says, she absolutely loves having “aha!” moments). And she especially enjoys learning together with and from other people: her team and her friends. Elena is curious about everything: people, software craftsmanship and the world around. Elena is also a passionate hiker and a cross-country skier 🙂
When the organizations we work with need to adapt, sometimes that means changing the team composition. In this episode, we talk about a project that required the teams to re-organize and find a new way to collaborate. We discuss the impact of distribution on team formation and dive deep into a process of self-selection: when teams create themselves by allowing team members to find the right group to contribute to a mission.
About Catrine Björkegren
Agile coach and scrum master, Catrine has worked with agile for a decade in various areas like education, nuclear waste, government agencies, pharmaceutical and at the Royal Swedish Opera.
She believes that co-location is the key to building teams and that leadership is the key to successful agile transformation.
Teams can get carried away with the practices of Scrum and continue to follow them blindly, even when they are not getting the value they want out of those practices. In this episode, we tackle the need for the team to own the process, and take over changing it to meet their needs. Kristopher shares a technique that can help the team learn what it means, and effectively own their process.
About Kristopher Stice-Hall
Is the co-owner of Digital Maelstrom, a consultancy specializing in custom software, DevOps, managed cloud services, and information security. He has been doing Scrum Master work for over 10 years. He has worked with fortune 500 companies to companies less than 15 people. He also has been doing software development for 17 years.
Digital transformations are a dime a dozen at this time. Many organizations are going through a transformation of business model, not just adding IT to an old business model. However, digital transformations are not only about business models, but also about ways of working. In this episode, we talk about the change process inherent to digital transformations, and how Scrum Masters can help teams survive the big change we call Enterprise Agile Adoption.
About Varun Maheshwari
Varun is a Scrum Master and agile practitioner in Australia. He believes in “being agile” rather than “doing agile”. For him, Agile frameworks are not the goal, but rather “Delighting customers, Zero Defects, Quick ROI, Better team work, Excellent Quality & Shortest ‘Time to Market’” are some of the possible goals.
Sometimes, the teams and organization are excited about the change. Possibly the adoption of Scrum or some other Agile methodology. However, it is not enough to have the enthusiasm of the team. Without a clear direction for the change process, “business as usual” will catch up, the pressures of daily work will take over and the change will stall. We talk about how we can avoid, or recover from the “business as usual” pressure cooker that teams will inevitably face during the change process.
About Elena Astilleros
Elena coaches people who hate wasting their time with badly run agile ceremonies, meetings or projects. She gives them tools to get more out of their time while sprinkling in a little enthusiasm and cheerleading. You can find some of her tools in the forthcoming book Invisible Leader.
Scrum Masters can be change catalysts, and often they become an active part of Agile adoption at their organization. However, even motivated, energetic Scrum Master can burn out. Change is a long process, and it can’t keep going if only you are working on it. In this episode, we talk about the importance of creating a “guiding coalition” to ensure that change takes hold and progresses in an organization.
About Eduardo Ribeiro
Eddy is passionate about helping people, teams, and organizations foster a culture of continuous improvement where experimentation and embracing change becomes part of their DNA.
He’s also the author of the Beyond Lean Agile Blog, a Co-Founder of the Lean Coffee Portugal Community, Founder of Agile Online Community and Co-Founder & Director of Startup Grind Porto.
One rainy Monday, a developer runs a script. The whole database is wiped out, and there are no backups. What can we learn from this story? Scrum Masters must help teams prepare, and sometimes recover, from disasters. This is such a story. We also discuss how we can prepare our teams to avoid catastrophic failures.
Nedeljko is a Scrum Master and a full-stack developer who has been in the IT industry for the better part of the decade. He spent the last 5 years actively working as a Scrum Master with many diverse teams and projects who has helped him understand his role better. One of the core developers of the first VivifyScrum release, he has participated in its development product-wise ever since.
Prioritization is not a simple, or easy task for Product Owners and teams. Sometimes, the teams focus on what they want to work on, sometimes on what is easy to do, but those are prioritization anti-patterns.
As Scrum Masters, we must assess the prioritization practices of our teams. When necessary, we must help them adopt new approaches to prioritization. Henrique shares one of those times with us.
About Henrique Centieiro
Henrique is a Blockchain Product Manager (i.e. dealing with the blockchain related features/user stories of the product). He is passionate about teams and agile, using scrum to manage even his personal tasks.
QA teams are isolated in many organizations. When Scrum Masters work with those teams, the first challenge is to help them see beyond their silo, and create a definition of success that includes working and collaborating with other teams.
In this episode, we talk about a QA team, and how they were able to transition to a more collaborative way of working, which – for the first time – included other teams.
About Ajeet Singh
Ajeet is an IT professional with 17 years of delivery experience in application development, system integration and software testing. He’s served as a ScrumMaster for over 3.5 years for the clients of USA, UK and Australian geographies.
When Scrum Masters help teams go through a change process there are few things more important than helping teams “take over”. In this episode, we explore the consequences of not helping the teams take over the change process, and also discuss approaches and tools Scrum Masters can use to help teams hold themselves accountable.
About Tilman Rumland
Tilman Rumland is an agile coach, expert speaker, and productivity enthusiast. He just released his new workshop series: “getting shit done that really matters to you”. As a scrum master, he implemented agile structures to agrilution, a small scale vertical farming startup, ranked on the Forbes TOP 100 innovative German Startups. (www.agrilution.com)