Join a panel of Agile Coaches for a discussion as to what we've seen, both the good and bad, in organizations they've been coaching. And, what you can do about it, no matter where you are in your organization. Plus, bring your own questions to ask this panel, and take from the experiences of coaches including Glenn Waters, Ellen Grove, Omar Bermudez, Jesus Mendez, John Tobin, and Michael Kaufman.

In this session, I will walk you through some areas of my childhood, introduce you to my father and explain you how I've used facilitation skills to fight back daddy's illness (alcoholism). During this session, you'll learn more about who I am, and if you pay attention or participate, maybe you'll take away two or three facilitation techniques combined with an inspiring and personal happy ending story.

In this session, I will walk you through some areas of my childhood, introduce you to my father and explain you how I've used facilitation skills to fight back daddy's illness (alcoholism). During this session, you'll learn more about who I am, and if you pay attention or participate, maybe you'll take away two or three facilitation techniques combined with an inspiring and personal happy ending story.

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! 

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! 

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! 

Ben Linders said: "if you want to solve the problems that you are having, and deliver more value to your customers, you have to change the way you do your work. That is why agile promotes the usage of retrospectives: To help teams to solve problems and improve themselves!" 

In this workshop, I will walk you through the reasons, concepts, phases, tips and tricks of behind the scenes of retrospectives, in a practical, engaging, fun and interactive manner.

Are you ready for the challenge?  

Ben Linders said: "if you want to solve the problems that you are having, and deliver more value to your customers, you have to change the way you do your work. That is why agile promotes the usage of retrospectives: To help teams to solve problems and improve themselves!" 

In this workshop I will walk you through the reasons, concepts, phases, tips and tricks of agile retrospectives and everything that happen behind the scenes. We'll share the space and learn together how to make this event a great one in a practical, engaging, fun and interactive manner.

Are you ready for the challenge?  

In this talk, Jesus invites you to take a closer look about how curiosity has transformed his professional carreer into an unlimited source of inspiration that supports his Agile journey. This inspirational talk, is a deep retrospection about live and the value of being authentic when establishing relationships with others.This experience-report has been formated in chronicles that will hopefully inspire you to connect with your authentic-self and lead you to greatness.

In this experience report, Jesus Mendez and Robert Pragai will navigate the audience through some of their inspiring experiences with teams that have had those moments that have marked their evolution towards the high-performance sustainability nirvana. By sharing their reflections about what the've called "Pivotal team "break/make" moments", Jesus and Robert will show you how to spot and process those special moments to empower and influence the team's journey to thrive.