When we define success for ourselves we are affecting how we see the work we do. Balazs challenges us to take things step-by-step and define success at the daily level. And only then move on to the work the team does and we do. Finally we should focus on how the team themselves succeed at achieving their goals. Success has many different layers and all of those have a daily implication. Listen in to hear the examples that Balazs shares about how he takes higher level definitions of success to the daily level in the work he does with teams.
About Balazs Tatár
Balazs is a technical project manager, working for the European Commission in Brussels, Belgium. Currently he plays the Scrum Master role in a support team of one of the biggest web project at the European Commission. He is a former technical lead and fan of open source technologies.
When it comes to defining success, Samantha shares with us a moving story that starts with a piece of feedback she once received from one of her team members. That’s what success looks like. But how do we get there? Samantha shares how she uses the retrospectives as the engine of learning for teams. And as a tool to help ground the teams in the core ideas of their agile journey, so that they can get back to basics when necessary.
Samantha is a Scrum Master based in London where she works with clients in a number of different industries. In her spare time she is a game writer and designer and uses Scrum to work on game projects.
What is the value the Scrum Masters are bringing in to the organization? Of course the investors and management are going to ask this question. I would too if it were my company. So we need to be able to show how we are helping the teams and the organization grow and become better. How do we do that? We measure the impact of our work, and Karthik shares with us some of the metrics we can use to show the stakeholders around us what it is that we are contributing to.
In this episode we discuss experimentation and evolutionary change using Popcorn Flow, a continuous improvement approach developed by Claudio Perrone.
About Karthik Nagarajan
Karthik has worked as a Product Manager, Scrum Master and QA Manager across a variety of domains, including: Fintech, Travel, Human Capital Management, CRM, Recruitment, Insurance, Banking and Financial Services. He loves tackling complex business challenges and being a positive bridge between Product, Design, Engineering, Quality Assurance, Customers and Business Teams.
All the teams we work with are doing their best. We believe so. And we also believe that certain mental models and practices are keeping them from doing much better, while still trying their best. In this episode we talk about the critical different developing software and releasing software. Releasing is a completely different problem. We discuss that and how to help teams get to the point where they can release software all the time, anytime something is ready.
A Scrum Master who specialises in Mobile and User Centred Design based approaches, Adrian comes from a testing background and he still finds that he champions making testing easier for the teams he works with. Due to that Adrian is also a strong advocate of XP practices (and, from that, BDD)
Jacopo describes in this episode 2 patterns that may lead to success, and can help you define your own success as a Scrum Master. In the scope of those 2 patterns we also discuss multiple metrics that could be useful in navigating our own evolution and growth as Scrum Masters.
About Jacopo Romei
Agile practitioner since 2003, entrepreneur more than once, he has been agile coach in eBay Italia, co-founder of the ALE Network and a former member in Cocoon Projects, an open governance based company. His main focus now are contracts and lean-thinking-compatible agreements.
For a successful Scrum Master, Scrum is just the starting point. Success starts when the team is able to own the process, and tweak it to fit their needs without losing sight of why they adopted Scrum in the first place. Jeremy explains how he defines success and the paths he takes to get there.