This organization was proud of their achievements. However, their culture was not allowing them to collaborate, and move the organization to the next stage. That move was critical for them to survive a changing market.
In this episode, we discuss a non-conventional way to approach organizational change, and how that helped this particular organization. Listen in, to learn about why that approach worked and how you can apply that approach in your Scrum team.
About Susanne Taylor
Susanne is a transition coach, which translates to roles as: change management facilitator, organizational development consultant, scrum master, agile coach and community manager. (Often simultaneously.) Susanne has learned to be adaptable and resilient after having lived in Alaska, Japan, Taiwan and now Germany. She is passionate about accompanying people on journeys of transformation. (And she considers herself an introvert.)
Scaling the use of Scrum in any organization is not easy. In this episode, we discuss Izis approach to that challenge from the Scrum Master perspective. Scrum Masters in larger organizations end up having to work with multiple teams. We explore an approach that may help Scrum Masters serve more teams, while amplifying their impact.
About Izis Filipaldi
Izis’ mission is to help people to improve their knowledge and professional value inside organizations, applying the agile way of working. She has been working as an Agile Coach for more than 7 years, helping people to deliver products, developing an environment free of judgments where they can fail fast and learn faster. Continuous improvement of: people knowledge, product delivery, and work environment, are her 3 main focus on work. And she loves what she does!
Nick shares the process a team went through to move from Scrum to Kanban. Their initial goal was not to move to Kanban, but through small steps and focusing on improving they found themselves using Kanban even without trying.
Do you wish all change process would be this simple? Listen in to learn what steps Nick went through with the team.
About Nick Stewart
Nick has worked in the “Projects Space” for the last 5 years, initially working with business change, then in IT using Prince 2, Waterfall and ultimately found Agile organically through pain of delivering projects using the other methodologies. More recently he has taken on a Delivery Lead role which allows him to continue to learn whilst helping teams deliver continuous value.
When introducing change to an organization, the way we present ideas and involve people become key aspects to our success. In this episode, we talk about how introducing ideas in different ways may have radically different results. We identify some approaches that have worked well, and we talk about the concept of “baby steps”, or relentless movement towards a direction. Finally, we discuss how to involve the team members directly in that process. As Scrum Masters we don’t need to tell the team what to do, they know. If they understand why the change is necessary, they can come up with the right steps.
About Sebastian Reverso
Sebastian is from Tucuman, Argentina. He has been working as a software developer since 2012 and as a Scrum Master since 2017.
Among his favorite activities are mountain biking and football (soccer).
The Agile Online Summit has been on since 2017, and is now in its third edition. From 500 participants in its first year, the AOS 19 will have 3000+ attendees from all over the world, and when you look at the list of speakers, it’s easy to understand why. AOS 19 will have, among others:
Andrew Stellman will talk about the people aspects, and how those affect Agile adoption
Al Shallowly will explore the 3rd decade of Agile, and what it might bring
Rebecca Scott will share her ideas on how teams can improve their connection with other teams
Bob Gallen will speak about Product Ownership
Anantha Natarajan will share lessons from implementing agile in a non-IT organization
Richard Lawerence will share his experience and ideas about Behavior Driven Development
Date and place: October 7th to 11th
This session packed conference will take place online from October 7th to 11th. Beyond the recorded sessions that will be accessible in those dates, there will also be live sessions organized to help you ask direct questions from the participants as well as interact with your fellow conference attendees.
For more details stay tuned to the Agile Online Summit website, where all the sessions are described, and where the information about upcoming live sessions will be added.
A networking opportunity you can enjoy from home or at the office
As any IRL (in-real-life) conference, Agile Online Summit is a networking opportunity, which will help you get to know the speakers as well as other participants. There will be a slack channel available for all who sign-up at this link (NOTE: DISCOUNTED VIP TICKET for Scrum Master Toolbox Podcast fans).
The Slack channel will be the preferred community hang-out area with channels for you to interact with participants from all over the world, but there will also be live sessions where you can ask questions directly from the speakers. Sign-up for the conference to know when those sessions take place (NOTE: Tickets are FREE for live attendance, purchase the VIP ticket for life-time access to the talks).
About Tom Henricksen
Tom Henricksen is a technical professional and coach. After working for many years as a developer, Scrum Master, and manager he has made a lot of mistakes and wants to help others achieve their goals. Tom has a passion for sharing wisdom with other agilists.
Tom is the founder and host of the Agile Online Summit.
In this episode, we discuss how Scrum Masters can introduce Scrum to non-software teams. Specifically, we share the story of a marketing team, and how Scrum was introduced.
We discuss the differences between Scrum for Software and Scrum for non-software teams. We share tips on how to introduce Scrum to non-software teams. Finally, we review how Agile principles can help Scrum Masters find the right practices for non-software teams.
About Jaime Bartol
Jaime has been a ScrumMaster/Agile Coach for 6 years with experience in large organizations as well as startup teams! She has worked with frontend and data engineering teams and even brought Agile to awesome marketing teams! Jaime’s passion is about teams and using Agile/Scrum fundamentals to elevate efficiency, productivity, and joy!
In this episode, we discover the approach that Rachel has found when she needs to help an organization adopt Lean Product Development. It’s not an easy process, but Rachel breaks it down for us. Through her experience, we learn a path that may help us when we help the organization we work with.
About Rachel Martz
Rachel has been in digital product development for over 20 years, having performed every role imaginable. She entered the agile space 13 years ago, doing hands-on product strategy and development modernization.
Rachel is in the data and analytics industry at the moment and loves being a Scrum Master because it’s the most impactful role she can have for helping improve people’s lives.
The role of Scrum Masters is to help the team improve. Those improvements are changes that we also need to help the team understand and implement. In this episode, we talk about what Scrum Masters can do to help the teams continuously improve and change.
About Angeliki Hertzfeldt
Angeliki finds that Scrum has transformed her into a better person: in the working environment, with friends and strangers, in social activities, and with her family, as a new mum.
This episode is about the story of changing an airport company to use Agile. This provides a great background to talk about the essence of Agile, and the management practices that go with it. We discuss how to avoid the “buzzword” resistance to change, and how to engage a team that has never heard of Scrum before.
About Joost Mulders
Joost has been an agile practitioner since 2008 and is continuously uncovering new ways to help teams and organizations on their agile journey. He’s taken several roles in that journey, such as Scrum Master, agile coach or management coach. He strives to create work-life fusion with agile, ultrarunning and filmmaking as the main ingredients.
In this episode, we explore the role that checklists can have in helping teams improve their process and their performance without adding more processes.
It is a normal tendency to “add more processes” to fix a problem a team is experiencing. In this episode, we challenge that view. Checklists, we argue, are a simple, effective tool that helps you reach a similar goal, but does not require the process to grow, and become bloated.
2 Common types of checklists that help teams improve how they work
There are several types of items we can add to a checklist. In this segment, we discuss 2 common types of checklists, and how they can help teams. We start by discussing the “process checklists”, which may include important tips on how to execute a certain process.
The key thing to remember is that checklists don’t replace processes, but are rather a set of reminders, or items that help teams execute a process once they’ve already read and understood the process.
The second type of checklists we discuss are those that summarize a series of requirements or pre-conditions that a team needs to follow-up on. This may include quality requirements or certain tasks that need to be completed before a certain work item is considered complete.
The most common checklists Scrum teams use
Scrum teams have a common set of checklists that they use. We discuss the commonly used Definition of Done, and also talk about the importance of having a Definition of Ready, and how that may help teams get started on the right foot when a new Sprint is about to kick-off.
Additionally, we talk about a pre-release checklist. With a pre-release checklist, teams are able to keep a memory of what they’ve learned from the past about meeting the release requirements, and can continuously improve that critical aspect of any team’s process.
In this segment, we also tackle the usual objections that people given when asked to consider the use of checklists. Checklists may be seen as “more bureaucracy”, but instead, they are there to help teams summarize a process that already exists, provides transparency about the process execution, and ultimately it should be a time saver for the team.
How about you? How have you used Checklists in your work? Share your experience in the comments below.
About Diana Getman
Diana Getman has more than 25 years of experience as a project manager leading cross-functional teams, in both startup and non-profit organizations. Diana has held the roles of Scrum Master, Product Owner, and Agile Coach and is the current President at Ascendle, a custom software development firm in Portsmouth, NH.