Details will follow

Details will follow

After more than a decade as an Agile Coach, I joined one of the first AI-native engineering teams expecting to help improve the way they worked. Instead, I found myself questioning many of the practices I’d been teaching for years.

This session is a candid story of what changed when AI became part of the team – not just another tool.

We’ll explore how practices like backlogs, refinement, WIP limits, documentation, and even traditional roles evolved, what stayed surprisingly relevant, and the new challenges that emerged along the way.

Rather than offering another framework, I’ll share a simple lens that helped us decide what to keep, what to adapt, and what to leave behind—without losing sight of Agile’s core principles.

You’ll leave with:

• A practical way to evaluate Agile practices in an AI-native world.
• Real examples of what to keep, tweak, and rethink in your own teams.
• A fresh perspective on the evolving role of Agile Coaches, Scrum Masters, and Change Leaders.

The email arrived on a Tuesday. Subject line: Quick update on your role — exciting news! J There was a smiley face at the end. I didn’t raise my hand. I didn’t apply. I didn’t even know what a Scrum Master was.

What happened next became a book.

In this session, Kim Hinsch brings her story off the page and into the room — honest, warm, and entirely unplanned. Drawn from her novel The Accidental Scrum Master, this is a session for anyone who has ever found themselves somewhere they didn’t choose and had to figure out how to belong there.

You will leave with something in your hands. And possibly a different idea of what accidental really means.

And if you can’t imagine it, how would you start working on it? If you’re looking for a way to turn this term into tips, tricks, tools and techniques, look no further!

We take interpersonal risks when we believe in the cause, in ourselves and in our teams. Beautiful things can be built where we bring our full selves to the table. And aren’t we all here to build beautiful things? So let’s start building those beautiful teams.

After this 45-minute workshop, you’ll be able to:

• Explain Psychological Safety to a 9-year old in 90 seconds
• Take relevant and concrete topics back to your teams
• Execute facilitation techniques to enhance Psychological Safety

Once you join, you can do more than just picture Psychological Safety. You can start building it, in your own environment. Imagine that!

You read a room before anyone speaks. You catch the silence that means pride versus the silence that means pain, the colleague who needs space versus the one who needs to be held. You’ve done it your whole life, and you’ve probably never put it on your CV.

Women are culturally trained, from very early and in very ordinary settings, to notice what isn’t said, to adapt, and to hold the emotional context of a room. Because this work is expected, it is rarely named. And because it’s rarely named, it gets treated as a soft skill instead of a professional competency.

In my talk I will share how culture shapes facilitation: Agile rituals inspired by Georgian traditions, and an experiment in using cultural anchors in the everyday life of a team.

The insight is twofold. It’s not only about turning a culturally familiar concept into an artifact that creates psychological safety, but also about using small tools to separate facts from emotions.

Hope you’ll leave with the confidence to design from your own table, building rituals for your team with the materials your culture already gave you.

In this session, I share the lessons I learned the hard way while supporting teams in large-scale and highly regulated environments. Through stories of mistakes, growth, and unexpected successes, I will explore why mindset alone is not enough, how enablement creates sustainable change, and why slowing down is sometimes the fastest way forward.

Whether you are a Scrum Master, Agile Coach, Change Practitioner, or simply someone trying to help others navigate change, I hope my experiences will inspire you to rethink how change happens—and how much of it is really yours to carry.

In this session, I will share what I’ve learned from facilitating IAmRemarkable with hundreds of practitioners across industries — the patterns that keep talented women invisible, and the small but powerful shifts that change everything.

You will leave not just inspired, but equipped: with a reframe, a tool, and a personal commitment to take up the space you have already earned.

As organizations rush to adopt AI in hiring, performance management, and decision-making, long-standing patterns of who gets seen, heard, and valued are not disappearing. They’re scaling.

For women, this creates a new kind of risk: algorithmic invisibility. Contributions like relational leadership, mentoring, and emotional labor – work that often falls outside traditional visibility patterns – become harder to measure, and easier to overlook.

This session introduces the AI-Era Belonging Model “Seen – Heard – Valued”: a practical framework to help leaders identify where invisibility occurs and redesign visibility, voice, and value in their teams. Because in the age of intelligent systems, belonging is no longer just a cultural issue. It is a design choice.

In this interactive talk, Priscilla Awad explores how to intentionally design sessions where teams feel safe, energized and connected.

Through the lens of Bloom, Build, Belong you will discover how to create psychological safety, use playful structure to unlock engagement and design moments that foster real belonging.

Expect practical, hands on techniques you can apply immediately whether you are facilitating a retrospective, workshop or team kickoff.

Leave with fresh energy, actionable tools and the confidence to create sessions where people dare to contribute, connect and grow.

We’ve all been in that room with the “know-it-all” whose dominance quietly kills collaboration. How do you handle it without starting a war?

In this session: No theory from books. No fluff. Just 5 real-world scenarios – from the “Professional Yapper” to the “Frustrated Team Member” and a clear Avoid vs. Try roadmap for each.

I’ll share my own failures and the field-tested tactics you can use the very next day. Just real tactics that work in real teams.

Because when you have the practical tools to BUILD a safe environment, you stop dominance from destroying psychological safety – ensuring everyone BELONGS and the whole team can finally BLOOM.

This isn’t just an inclusion problem – it’s a performance problem.

• The deep thinker whose best ideas come 24 hours after the ideation session, not during it.
• The high-impact contributor whose work is invisible to your review criteria.
• The person who holds the team together during a crisis but never takes credit.

These people are in your organization right now. Your system just isn’t built to see them – and that has a cost: in your delivery, your retention, and your results.

The fix isn’t asking individuals to adapt more, communicate better, or be more visible. And it isn’t making everything flexible – that’s just chaos with extra steps.

The real question is: where do you standardize, and where do you flex? Most organizations have never consciously asked that.

In this session, we’ll look at why well-intentioned inclusion efforts so often fail – and where the real lever for change actually sits. Then you’ll map your own organization, identify where the invisible barriers are, and walk away with one concrete change worth taking back.

This session maps to all three conference tracks:

• Bloom: stepping into leadership that creates real conditions for growth
• Build: practical tools for redesigning how organizations work
• Belong: creating environments where people don’t just fit in, they do their best work

In this lightning talk, I’ll share how I worked with a Product Manager to use AI to turn vague ideas into clearer, shared requirements. Together, we built a simple workflow that helped us ask better product questions, uncover edge cases, define acceptance criteria, and create stronger Jira tickets.

Rather than using AI to replace product thinking or make decisions for us, we used it as a collaboration partner – helping make invisible questions visible and creating a shared understanding between product, design, development, and QA.

It’s a small example of how AI can help us not only build faster, but work better together.

You discover that leadership doesn’t resist agility—they resist dogma that doesn’t solve their problems. When we learn to speak the language of risk, strategy, and business outcomes, Agile stops being a hard sell and starts becoming an essential advantage.

In this 7-minute lightning talk, let’s explore how to make Agile irresistible to leadership:

• Empathy for the business: Understanding the pressures leaders face so we can coach with real context.
• Outcome-driven value: Moving the conversation from framework compliance to measurable business impact.
• Expanding our seat at the table: How agility becomes the ultimate tool for strategic leadership.

Step into the room and discover how to bridge the gap between coaching heart and business mind.

Coming soon

The connection with Bloom, Build, Belong is mainly around the shift happening in product building with AI. When we can build almost anything faster and more easily, the challenge is no longer only what we can build, but how we make people feel about what we build.

In my keynote, I’ll explore how product teams can go beyond functionality and create products that make users feel seen, understood, surprised, supported, or even celebrated. I see this as an important part of building products that people don’t just use, but genuinely connect with and want to belong to.