Dana Pylayeva, will host the coaching track at the summit, where we explore some of the hard lessons we need to be aware of when adopting coaching in our practice
Ayodeji Ishola, hosts a track on the state of Agile in the African continent, and will be showcasing talks that address the cultural specific aspects of Agile in Africa
Mariana Trigo, will have 6 sessions on career advice for Scrum Masters and hiring advice for those hiring Scrum Masters. She’ll have a special focus on how you can get into the Scrum Master role even if you don’t have a tech background.
Yves Hanoulle, the co-author of the Tips from The trenches audiobook, hosts a track on Hybrid work, very topical now that we have our teams remote most of the time
Martin von Weissenberg, will share patterns of scaled agile. Not the frameworks we always hear about, but rather practical, down-to-earth advice for specific needs when we scale agile
Accepting and learning to deal with Social Complexity in Agile adoption
When teams start adopting Scrum, it’s easy to think that when they are proficient in Scrum, the work is done. However, that’s not nearly enough to help the organization achieve its goals. What are the outcomes that the team is aiming for? Are those outcomes part of the team’s Vision, and Mission?
Peter suggests that we should start our work by defining together with the team and stakeholders what success means. That becomes the first question to ask before we start our work with the team.
Bing bang approaches are sometimes necessary, but not sufficient for the momentum of change that is needed
Coaching Agile principles is a cornerstone of mature teams. The competencies required though are both deep and varied. We want you to participate in our anonymous survey on Agile Coaching competencies. Help us to better inform aspiring coaches of how best to improve by telling us where you are at in your journey’
I’d love to come back on and talk about the insights gained, already the results are surprising and a great talking point but I won’t spoil it!!
This is a guest blog post by Jacopo Romei. Author of Extreme Contracts, a book about how to build trust, and deliver value without traditional contracts.
How to build trust with clients and stakeholders while getting what you deserve for your work: a story about trust
Over the last ten years, I’ve experienced the direct impact of lack of trust in vendor-buyer and even colleague-colleague relationships. I’ve come to find that it is the main reason why collaborations in knowledge work fail.
I’ve tried to fix that in my own work as an independent consultant and when working with other colleagues. That’s why I ended up experimenting with a new type of agreements which are optimized for trust building. This experimentation resulted in a set of principles that I call Extreme Contracts. Now, all my customers and I use this approach to shape our collaboration and they have started using Extreme Contracts also with their customers.
As part of our “Coach Your Product Owner” course, we’ve been hard at work creating simple and actionable tools you can use to help your Product Owner progress. But that coaching cannot happen unless we tackle the biggest problems we have when coaching Product Owners. So, last week I asked people who receive my Newsletter to help me answer this question:
When it comes to Coaching and Supporting your Product Owner(s), what is the single Biggest Challenge that you are facing right now?
The reason for this question is my belief that, as Scrum Masters and Agile Coaches, we must help the Product Owners as part of our duties. Sometimes those duties may be just about helping them manage/facilitate a particular session, but often we need to help the Product Owner grow their skills, knowledge, and experience with Agile product development. All aspects of it.
So what are the key challenges we face, when coaching and supporting our Product Owners?
To understand how the system behaves we must “poke” it, and Scrum is just the perfect method for that. Every sprint is an experiment that helps the team and the Scrum Master understand how the system behaves and reacts to the different experiments that we run every sprint. Jeremy has a collection of metrics he follows-up regularly to keep in aware of how the system behaves, and enable him to actual test new approaches every sprint.
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.
Passion is in the overlap between attitude and aptitude, and it is the ingredient that makes good Scrum Masters even better. Jeremy explains how he looks and tests for passion in the recruiting interview.
Incremental delivery is a buzzword in the Agile lingo. It is very often used, but seldom defined. Jeremy explains what incremental really means, and gives us an insight about the far-reaching benefits for those that take his definition to heart.
In this book we refer to the book User Story Mapping by Jeff Patton.