The Magic of Perception
In this interactive session, we’ll explore how each of us views the world differently and how our perception is shaped by everything we've previously experienced. Through magic, illusions, and an interactive exercise, Jeff reveals the ways our perceptions and biases influence our reality and how our individual realities are unique.
Discovering your distinct personal perspective by understanding how biases impact how we make sense of the world around us, we can learn to better understand others. We can gain insights which inform our interactions with customers, colleagues, and competitors.
You'll leave this session with an appreciation for working with others, and approaches to team problem solving in our complex world. No magic spells required.
Outline/structure of the Session
This session will include multiple magic tricks/illusions to illustrate a few common biases and perceptions people hold. Each trick will be connected to one (or two) of these, illustrating how the magic works and is able to fool the audience, and how this applies when working in teams, or with people in general.
Without giving away the magic tricks performed, a rough timeline is as follows:
- 10 mins: provide the framework of the talk; intro to perception through audience exercises
- 25 mins: biases, perceptions, demonstrated through magic, and connected to work & people
- 10 mins: participant exercise
- 10 mins: connection to the start of the talk, additional bias/perception through magic
- 5 mins: question, answer, discussion
Please note: this can be easily adapted to a 45-minute session, as required to fit in the program.
By being aware, and talking about common biases and perceptions we have, we are in a better position to identify our own blind spots, helping us with our interactions with others. In addition, participants will gain an appreciation of the motivations of others when interacting with them.
This interactive talk and workshop is appropriate for anyone & everyone who has to interact, work with, talk to, collaborate, or compete, with other people.
schedule Submitted 10 months ago
People who liked this proposal, also liked:
What we've learnt as Agile CoachesJeff KosciejewEllen GroveSue JohnstonArdita KarajLee EllottAndrew AnnettJeff "Cheezy" Morgan
schedule 10 months agoSold Out!
Join a panel of experienced Agile Coaches for a discussion and Q&A of their experiences as coaches. Each of the panelists has a different background, and a unique journey into their role as an Agile Coach. Along the way, they've each built up a wide and diverse set of skills, from their careers, interactions, and experiences.
What have some successes been?
How do we even define success for ourself, as an Agile Coach?
More importantly (and hopefully more entertaining), will be some of the lessons learned... We'll explore what was tried, but had a surprising and unexpected outcome.
And, we'll discuss some of the ways experienced coaches continue to learn, share, grow, and develop everyday!
IT has embraced agility ... what about the rest of the business?Jesus Mendez
schedule 10 months agoSold Out!
3.5 years ago Seedbox Technologies decided to embrace agile methodologies as its way to develop web based products, get them out faster, survive and thrive competition.
It's all started in a traditional fashion: external consultants were hired to teach employees the agile mindset and how to use agile methodologies like Scrum and Kanban when developing web based products. Project Managers got trained and became Product Owners, experienced Scrum Masters were hired to get development teams to their highest level of performance as fast as they could, developers got trained and developed experience around their team development processes, engineering managers supported agility across the company, and stakeholders directly involved in product development got invited to collaborate with software development teams through agile processes, once they got fully implemented.
That's right, Engineering got agile quite right but by doing so:
- What happen with the rest of the organization?
- What about peoples mindset?
- Is them vs Us or vice versa?
- Are they able to collaborate, inspect and adapt like the engineering teams and people related to agile projects do?
- How do we get everyone in the organization to communicate when we don't share the same vocabulary?
- How do we fill the gap and avoid old management treats get in the way of the companies transition to something bigger than just the teams?
- Shall we wait until they realize that we all need to change or shall we help them get there?
- How do we use are know-how to turn this mess into a big opportunity for the organization to grow?
- Do we need help?
Well, if this experience report gets accepted, I will share what I've learned about:
- The challenges & flaws that we faced when transitioning from team based agility to organizational agility
- Some of my reflections as an inside observer
- How to use the lessons learned as a wake up call
- What can be done to help the organization to thrive
Let's walk together through a nurturing experience report that might ignite your sens and get you inspired to give the extra mille!
Running with the Mob: Extreme collaboration with Mob Programming
Mob programming is collaboration taken to the extreme, eliciting the best from every member of the team. In this session, you will experience the dynamics of mob programming and learn how to use this technique successfully in your own environments.
After mobbing with over two dozen teams, we've seen definite patterns emerge, that we'll discuss here.
As a GOAT Conference participant, I need to write better User Stories
That's the most important question to answer. And, did you notice? I specifically didn't do it.
As a GOAT Conference participant, I need to write better User Stories.
What's missing is the "why". That's so important, because writing better User Stories could mean so many things to different people. And if you're going to attend this session, you really ought to know what you're going to get out of it. That's the 'why'.
It's more of an art, than a science. Writing great User Stories, that is.
Why have I been told to use a the funny "As A / I Want / So That" format?
How big is too big, and why should I spend time splitting stories?
Isn't a user story the same as a WBS item?
Good questions, indeed. You likely have more. Excellent.
In this interactive session, we'll explore the fundamentals of writing good user stories. And we'll try to make those good user stories, better. We'll also look at alternatives to user stories, and find ways to represent ideas as product backlog items in other ways. We'll explore why the Card, Conversation, and Confirmation, are so important, and why it's worth the time to INVEST in meaningful stories.