With over 5 years in the practice of tango, I would like to use tango techniques to explain the nuances in communication between product team and dev team. It’s not often straight forward or easy.

Tango is an extreme dance in coordination and non verbal communication. it is also not the kind of dance that can be guided by strict rhythm like salsa. Instead, it’s a decision between both dancers on how fast or how slow they want to take it. It is also one of the few dances where pauses are encouraged and takes the form of regrouping.

I’ll be using experiential learning to demonstrate techniques in communication. (Note: it’s not a tango lesson but a communication workshop using tango.)

 
5 favorite thumb_down thumb_up 3 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

I'll be combine tango philosophy to explain the principles in communication nuances between leaders and followers.

 

The session is experiential so participants can participate in dancing and learning or observing by the side. There are 5 - 6 principles. Each principle is about 10 mins.

1) Set up and organisation / Introduction

2) The posture - posturing of product owner and development team, the similarity and the differences.

3) Synchronise in understanding - why we need it, what to do

4) Taking steps together - where to start, the posture to take and why

5) Leaders - what to look out for, what to be aware of and why

6) Followers - how to listen

Each principle is accompanied by a tango movement so the body remembers the experience and relate it to the lesson. 

I've already done this in Agile Tour Vietnam with positive feedback. 

Learning Outcome

Product owners to reflect and be mindful in their communication with development team. And the same for development team. 

Scrum master can learn the nuances and help to overcome barriers. Sometimes, Scrum Master can also use rhythm to help the team find back the path to communication. 

Target Audience

Product owner, developers, scrum masters

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Michael Chik
    By Michael Chik  ~  1 year ago
    reply Reply

    Hi Jas & Guillaume,

    Would it be possible to shorten your session to 45 min?

    Many thanks,

    Michael

    • Jas Chong
      By Jas Chong  ~  1 year ago
      reply Reply
      Hey,

      Sure. I think 60mins is more meaningful. 45mins is doable. Are there good breaks between sessions or is 45mins inclusive of people moving and getting into the session?

      Cheers,

      Jas



      On 29 Feb 2016, at 14:09, Agile HK 2016 <info@confengine.com> wrote:

      Dear Jas Chong,

      Your proposal PRODUCT OWNER & DEVELOPMENT TEAM – A TANGO IN COMMUNICATION has received a new comment from michael-chik

      Hi Jas & Guillaume,

      Would it be possible to shorten your session to 45 min?

      Many thanks,

      Michael


      Visit https://confengine.com/agile-hk-2016/proposal/1990#comments to respond to the suggestion OR simply reply to this email (Please make sure, you delete the previous comment's content from the email before replying.)

      Regards,
      Agile HK 2016 Team
      conf@agilehk.org
      https://confengine.com
      You are receiving this email from ConfEngine on behalf of Agile HK 2016. Thanks for using ConfEngine's Conference Submission System.
      Click here to unsubscribe from all email updates from ConfEngine.
      • Michael Chik
        By Michael Chik  ~  1 year ago
        reply Reply

        Thanks for your quick reply. I'd be great if you could adapt your session to 45 min.

        We are planning for 45 min time slots, with 15 min buffer time in between for the participants to chat and attend the next session and for presenters to set up and prep for their upcoming talks.


  • Liked Michael Chik
    keyboard_arrow_down

    Michael Chik - Test

    45 mins
    Talk
    Beginner

    Test

  • Liked Teng Daniel
    keyboard_arrow_down

    Teng Daniel - Awakening Change - Influencer's Toolbox to Make an Sticky Impact

    Teng Daniel
    Teng Daniel
    Awakener
    Odd-e
    schedule 1 year ago
    Sold Out!
    60 mins
    Talk
    Advanced

    If you give kids broccoli and tell them it is good for their health. Most likely, you will still get a no. The reason is quite simple, little kids don't care about being healthy. This broccoli principles applies to agile adoption as well. Simply telling and pushing new ideas and practices don't help very much because It is about changing people's mindset and way of thinking. Push and enforcement will always get resistance. The more push we have, the more resistance we will have as coach or change agent. To make it even worse, each individual, team and organization are so different, the culture is different, the business situation is different, the technology is different. Those are perfect excuses for not to change. One key factor for successful and sustainable adoption is to lit the desire to learn and improve, from individual, to team, to organization level. Rather than being pushed a lot of ideas, team will come for help and guidance, to pull idea from coach then apply in their context. 

     

    It is crucial to understand coachees based on their receptance of ideas. Who are the innovators, who are the early adopters, who are in the early majority and who are in the late majority. Based on the categories, as an agile coach, try to apply various tools to influence the change. 

     

    I presented early version of this talk at Scrum Gathering Paris and Beijing in 2013. 

  • Liked Marcio Sete
    keyboard_arrow_down

    Marcio Sete - From zero to happiness - A practical Kanban experience in an Ops Team

    Marcio Sete
    Marcio Sete
    Agile Coach
    Elabor8
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Beginner

    This talk is about a story of an OpsTeam, working in a multi-million Cloud project, looking for a Project Manager to support them. What did they get? An Agile Coach instead!

    I'll share how this experience has been, the bootstrapping, what worked well, what didn't, the peculiar challenges of an OpsTeam and how we are increasing our happiness index every day using the follow strategy:   

    #1 – Visualize the work

    #2 – Reduce batch sizes to improve flow

    #3 – Collaborate to win

    #4 – Make sure we are doing the right thing and just the right thing

    #5 – Collect tangible results

    #6 – Run different feedback loops 

    #7 – Celebrate quick wins

  • Liked Hugo Messer
    keyboard_arrow_down

    Hugo Messer - Why distributed teams don't work and what to do about it

    Hugo Messer
    Hugo Messer
    Entrepreneur
    Ekipa.co
    schedule 1 year ago
    Sold Out!
    45 mins
    Workshop
    Intermediate

    Based on 10 years distributed agile experience, Hugo's distilled 5 core problems in distributed software development. To find solutions, he's gathered data from hundreds of practitioners and wrote 6 books about remote teams. In this workshop, participants will learn practical solutions to make distributed teams work better. 

  • Siraj Sirajuddin
    Siraj Sirajuddin
    Co-Founder
    Temenos+Agility
    schedule 1 year ago
    Sold Out!
    90 mins
    Workshop
    Executive

    Enterprise Agile Transformation initiatives are BIG. Change at this scale of thousands is tough.

    The Leaders and Executives involved in these initiatives are going through their own personal transformation. Change at this scale of one is equally tough.

    Siraj Sirajuddin has worked with hundreds of executives leading enterprise agile transformation initiatives. These are their stories of personal growth and individuation. We will hear how transformation at a personal level is the leverage for transformation at a collective level. We will also learn of unique methods that activate personal transformation for leaders who are ready to step into their leader persona but are unable to get that from traditional leadership training and coaching methods.

  • Liked Joseph Yao
    keyboard_arrow_down

    Joseph Yao - Mutation Test - A New Way to Improve Code and Test - More Information

    45 mins
    Talk
    Beginner

    Mutation test is a way to put a "mutation" into your code, run the test and then see if the test fails or not. A mutation is a change to production code which should make it behave in a different way. The idea is, if the production code is just enough to pass the test, any mutation should make the test failed due to the behaviour change. If test failure doesn't happen, we will say that the test can't kill this mutation. Therefore, some test code smell or production code smell exists, which possibly leads to some learning and improvement of our code and test.

    By TDD, we should get "just enough" code that passing all the test. But, how do we know this? Sometimes, since writing test and code is so interactive in TDD, we may not choose the smallest baby step to pass the test. This means we may write some code which is not driven by current test (code smell). On the other side, we may even miss some important test or create some “weak” test by TDD because the code is too “obvious" to us (test smell). By applying Mutation test mindset and methodology, we can identify such code smell and test smell and then help us improve the quality of our code and test.

    In this topic, I will first introduce what mutation test is and why we can use it to create some learning of and improve our code and test. Then, I will share a real code example in which I tried the mutation test and some learning I got. Finally, based on what I learned so far, I will have a summarisation about the code smell and test smell which can be detected by mutation test.

  • Liked Cedric Mainguy
    keyboard_arrow_down

    Cedric Mainguy - Play your way to Agile: Self-organizing agile transformations

    60 mins
    Talk
    Advanced

    How to reduce time-to-market in retail banking?

    Design your agile transition and leverage game-based activities to help agile beginners adopt practices in various contexts, business areas, projects types and countries.

    This presentation is a feedback session from a large-scale agile deployment in two of the largest retail banks in the world. This approach puts design thinking and innovation games at its core as a mean to adapt deployment to an organizational context. Games helped us facilitate selection, adoption and ownership of new agile practices in various business areas, projects types and countries. Multiple countries were involved in the transformation and we were able to collect a large amount of valuable information to support the scaled adoption in a short period. The result of our action opened new possibilities to engage people and experiment better ways to work!

  • Liked Danielle Jabin
    keyboard_arrow_down

    Danielle Jabin - Measuring Team Performance At Spotify: From Gut Feel To Hard Data

    Danielle Jabin
    Danielle Jabin
    Agile Coach
    Spotify
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    How do we actually know if our teams are doing well? Is gut instinct enough? Furthermore, in a rapidly growing organization such as Spotify, how can we ensure some sort of consistency in our baseline level of Agile knowledge across the technology, product, and design organization? 

    In this talk, I’ll discuss techniques we have developed and use at Spotify to benchmark health and performance for our teams and some tactics we use to bring them closer to—and beyond!—being the best teams they can be. I’ll explain frameworks that can be used to give us tangible evidence about how we’re doing as teams, as Agile Coaches, and as managers of people and product. Furthermore, I’ll tell you about the organization-level methods we use at Spotify to share knowledge and maintain alignment of our agile practices as we scale in order to bring music to people all around the world

  • Liked Timothy Lok
    keyboard_arrow_down

    Timothy Lok - Making use of both Scrum & Kanban

    45 mins
    Talk
    Intermediate
    1. What is Scrum and Kanban?
    2. Comparing between Scrum and Kanban
    3. How to get the best of both worlds? Scrumban
    4. What are the best practices in Scrumban?
    5. Q&A

     

  • 60 mins
    Talk
    Executive

    The world is going through a revolution, a metamorphosis that creates a new paradigm. This talk is an exploratory journey into human-centered strategic innovation: Design Thinking and Innovation Games and how these approach and techniques can support your organization to build a roadmap for changing the world! 

    Design is used to create new products; Design Thinking is the way of thinking of designers applied to a broad spectrum of areas like customer experience, services, corporate strategy or even large-scale systems. Design Thinking and Agile share common founding principles and mutually reinforce each other. Design Thinking places empathy and collaboration at the heart of the innovation process and offers a roadmap to create true change in the world.

    Innovation Games are a shortcut to innovation. We learn best and are more effective when we have fun and play and an increasing number of organizations have realized the enormous potential of game-based activities. Innovation Games can also be applied to a broad spectrum of areas like training, hiring, generating new ideas, making meetings more effective, generating feedback about a product or service, improving communication, avoiding common decision-making pitfalls, feature prioritization, vision sharing, SWOT analysis, strategy building, reflect and learn sessions and change management... The list goes on.

    Organizations like Google, IBM or the United Nations use Design thinking and Games on a regular basis. Not a single month passes without a book, article, conference or training about these increasingly popular topics.

    The growing success of Agile methods, which put a strong emphasis on people interactions, fun and build a creativity-friendly environment, have made Design thinking and Innovation Games even more popular.

     

  • Liked Guillaume Duquesnay
    keyboard_arrow_down

    Guillaume Duquesnay - From Developer to Scrum Master : 5 keys for starting

    Guillaume Duquesnay
    Guillaume Duquesnay
    Agile Coach
    Palo IT
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    New Scrum master coming from the technical world, this session is for you.
    Regarding code, architecture, configuration, you're learning continuously. But there comes a role whose essence is absolutely not technical, and suddenly learning seems hard. And by the way, your teammates are counting on you, not to mention your boss. Feeling some pressure, dude ?

    Based on the difficulties that new Scrum Masters usually faces, heres a few recommandation to get you a maximum confidence at start. Most are focussed on the retrospective facilitation, but the underlying principles can be applied to your whole action in the project.

  • Liked Guillaume Duquesnay
    keyboard_arrow_down

    Guillaume Duquesnay - 5 powerful practices that are little known but work out-of-the-box

    Guillaume Duquesnay
    Guillaume Duquesnay
    Agile Coach
    Palo IT
    schedule 1 year ago
    Sold Out!
    45 mins
    Experience Report
    Beginner

    At the beginning was the Book of Agile. From there people learnt and teach agile practices. Along the way a natural selection has come, brought by continuous improvement. Some practices were improved, some abandoned, some new one introduced.

    As an agile coach I consider a personal duty to observe and contribute to this natural selection. What are the practices that works the most ? What are those that are hard to catch or don't bring much result ? Am I bringing teams the best for them ? 

    Looking back at my years of practicing and coaching, something struck me : some of the best practices I've seen working are just dead simple, but little known. And most them are roughly universal, no chit-chat, no bickering, no learning curve, you pick them and they're useful in your context 95% of the time.

    So as a way to push forward the natural selection of practices, I'd like to share my top 5, the easiest-to-get-but-most-powerful practices I’ve seen working. As an attender, I expect you to come with all your critical mind, we're here to raise natural selection, right ? So If you hear something that didn't work for you, raise your voice, I've saved 15' of Q/A just for that.

  • Liked Jas Chong
    keyboard_arrow_down

    Jas Chong - Don't waterfall your agile transformation

    Jas Chong
    Jas Chong
    Agile coach / Scrum Master
    IBM
    schedule 1 year ago
    Sold Out!
    30 mins
    Talk
    Beginner

    The stories of agile transformation are many, some funny, some painful, some frustrating, some motivating. It feels like colours of the wind and often I'm inspired to write books about the adventures in change management. 

    Very often, when a bunch o friends and colleagues sat together to share camp fire stories of agile transformation, 2 phrases circulate in my retrospection of the many stories. 

    From Einstein who said: The very definition of insanity is doing the same thing over and over again expecting a different outcome. 

    From Sun Tze who said: know yourself and know your enemy. 

    The main challenge is that if you've only known waterfall method, then you are likely to do agile transformation in a waterfall way. How can you know what you don't know and implement that which you are learning to know? And then naturally, you'll fulfil what Einstein said, doing something in the way you know over and over again expecting a different outcome. 

    Even agile practitioners are not spared in this trend. It's often easy to recognise software development cycles that are waterfall or agile. But in change, when the impact is team set up, stakeholders management, it's not easy to recognise when you had used waterfall and when it is agile. 

    For eg. If in your agile transformation, you have not used a pilot to test assumptions, you've probably don't it waterfall. 

    For eg. If in your team set up, you've written the job descriptions by yourself or by your HR, you've probably not used agile in your transformation. 

    I'd highlight some blindspots we have, gathering all the camp fire stories from friends and colleagues to share and help us be more aware of it. 

  • Liked Sylvain Mahe
    keyboard_arrow_down

    Sylvain Mahe - How to gain control by letting go? A toolkit to shift from manager to leader

    45 mins
    Talk
    Intermediate

    I used to work as a Program Manager on a large waterfall project. I spent my day assigning tasks to people, tracking progress and trying to prevent the next crisis. I thought that was the normal life of a Program Manager.

    I was wrong. Agile proved me it can be different.

    In this talk I will share the tools, books and trainings that helped me change my perspective and become a better person in the process:

    • Why let it go from the command and control mindset?
    • Which tools can you use as an Agile leader?
    • Why trust is the foundation?
    • Why self-awareness is key as an Agile leader?
    • Am I a roadblock in the Agile adoption initiative?
    • Why we have no choice (the generation Y is knocking at the door)?
    • How can I become the coolest boss?

    This talk is part of the Toolkit series.

  • Liked Sylvain Mahe
    keyboard_arrow_down

    Sylvain Mahe - The day I discovered I was not (yet) an Agile coach

    20 mins
    Talk
    Intermediate

    I remember that morning, 6 or 7 years ago. I had been practicing Agile for a couple of years and I had decided to update my LinkedIn profile. I opened my profile, edited my headline and replaced “Scrum Master” with “Agile Coach”.

    That was a lie. But I didn’t know it at that time. I really believed I had become a coach. In reality I was a consultant, a trainer, sometimes a mentor.

    A few years later I decided to go back to school -a coaching school- and it changed my life.

    In this talk, I will share my personal journey to become an (Agile) Coach and share what I’ve learned along the way:

    • What is the difference between consulting, training, coaching and why we should care?
    • Why by calling ourselves coaches we are not doing any good to the coach profession?
    • What can we do about it?
    • How did I become a coach?
    • What are my coaching tools?
    • Does your organization really need a coach?
  • Liked Christophe Muratet
    keyboard_arrow_down

    Christophe Muratet - Let's practice Kanban for software, let's play getKanban!

    120 mins
    Workshop
    Intermediate

    GetKanban is a an empirical introduction to kanban through board gaming.

    2 teams of 6 people team up as 2 startups competing (~3hours) to build a new 'revolutionary' app as fast as possible. What team will shorten time to market and win it all?! But wait things don't come easy, delay penalty, evil test manager and sick developer will spicy up the challenge.

    On same principle of MiT beer game, getKanban is ideal introduction to pull scheduling, WiP limit, lead time, in others words "K"anban for software.

    https://getkanban.com/

    Note: not sure this workshop fits in agile conf agenda, perhaps for a coming meetup instead