Sometimes, new teams are formed where some team members still have “legacy” tasks in their to-do lists. When that happens, it is the responsibility of the team (with the help of the Scrum Master) to figure out how to handle that work. There are many options to handle that situation. What is not ok is to let it grow, and spiral out of control. Teams own tasks, not individuals, therefore the Scrum Masters should help the team understand that legacy tasks are a team issue, not a personal issue.
Katy has over 14 years of software delivery experience, serving in roles ranging from analyst to developer, project manager and for more than 6 years, also Scrum Master. Her Scrum experience has been mostly with distributed teams working across multiple time zones. She hopes to someday have the opportunity to travel to meet her colleagues in China, but for now, Katy enjoys reading about creative methods to keep her team engaged.
Scrum Masters that move onto organizations that are just in the start of Scrum adoption may find that it is not an easy process, even when you have top-management support.
In this episode, we talk about what goes wrong when we focus on change from the top, and forget that the teams (whom we work with), might be against the change. Top management support is not enough for Scrum adoption!
About Nick Vitsinsky
Nick as more than 10 years in IT started from QA Engineer/Waterfall after two years realized that there should be a different approach to how to develop and ship the software. His philosophy and mindset is: “find out Agile and make it own moto”. He focuses on that on a daily basis.
Planning for a Sprint is not an easy task. There are many unknowns, even at the Sprint level, and team members justifiably feel uncomfortable discussing commitments, when they know there will be unexpected events during the Sprint.
How can Scrum Masters help teams learn the value, and the mechanics of planning? That’s what we discuss in this episode.
About Mili Shrivastava
Mili has more than 12 years of experience in the software industry. Loves to spend time with her family and is a big fan of outdoor activities like hiking and biking.
We reflect on the time it takes to effect meaningful change, and how Scrum Masters can help teams learn to be patient in the process. We also discuss some critical tools that help change take hold. Specifically, how transparency and customer/stakeholder engagement can drive change in a team.
About Jassy (Jan-Simon Wurst)
Jassy moved from developer to being a Scrum Master and then a freelancer. He calls himself: the person to contact for help in On-Boardings, as well as a friend of bottom-up, power to the people! No top-down, no micro-management. No despotism in agile software development.
As we work with organizations in transition, we need to help teams and Product Owners make sense of the new ways of working. In this episode, we discuss how Scrum Masters can help Product Owners and teams find a way to collaborate when changing towards Agile. We share some tools that help large groups come together and learn to focus more on the impact they seek, rather than just the work they need to do.
About Bradley Pohl
Bradley is a young Scrum Master working for a mid-sized US bank that is currently undergoing an “Agile Transformation.” As a part of the Transformation, his training consisted of a 4 week Agile boot camp that was designed to build scrum masters from the ground-up. In his free time, he applies lean and agile principles to designing websites and providing social media advertising to local small business as Catch On, at catchontech.com.
OKR’s are a management tool that is gaining wide acceptance in the tech industry and other industries. The ideas are simple and should be simple to adopt, except they are not.
In this episode, we talk about what Jeremy learned about the roll-out of OKR’s at his company and how Scrum Masters can help adopt OKR’s the right way! Not a simple process.
About Jeremy Willets
Jeremy Willets is a Technical Writer turned Scrum Master/Agile Coach. He’s passionate about bringing Agile to all facets of his organization. He enjoys spending time with his family, making music, and drinking the finest craft beer the world has to offer!
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 🙂