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

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. 

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

Outline/structure of the Session

  • Agile transition will also follow idea diffusion curve
  • What are the characteristics of people in different group including innovators, early adopter, early majority, late majority
  • What are the tools to apply in agile transitions for based on group

The talk will be story based and we will derive these tools and principles from real life case studies. 

 

Learning Outcome

  • SNIPer coaching principles when introducing change to organization
  • Practical coaching tips for triggering the desire of individual and teams to pull idea from coach
  • Effective tricks and advice for enabling continuous improvement 

Target Audience

ScrumMaster, Agile Coach, manager, senior executives

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Daryl Chan
    By Daryl Chan  ~  1 year ago
    reply Reply

    Thanks Daniel.

    Is this framework something you've created yourself?

    • Teng Daniel
      By Teng Daniel  ~  1 year ago
      reply Reply

      Yes, when I dealing with different kinds of people in the organization and try to trigger/influence the change. So the talk will be mostly story driven. But from those stories, I refactored the concepts.

      • Daryl Chan
        By Daryl Chan  ~  1 year ago
        reply Reply

        Cool, thanks for clarifying.


  • Liked Joseph Yao
    keyboard_arrow_down

    Joseph Yao - No Return Value Driven Development

    45 mins
    Talk
    Beginner

    As a programmer, you most likely have written some functions which return a value, right? Do you know how to write code without any return value? Do you know what kind of design problem will come with the code which returns some value?

    This topic will show you the value of no return value code via some real code sample. It will show you the benefit about such no return value design as well as something deep in the object oriented design.

    If you're a programmer who wants to write better code, this is topic for you. Your development mindset might be stroke in this talk, please keep calm. :)

  • Liked Eric Byron
    keyboard_arrow_down

    Eric Byron - Game Outcomes Project

    45 mins
    Talk
    Intermediate

    In November 2014 an independent team of academic and industry leaders conducted a survey targeting the video games industry in an effort to understand the factors that distinguish successful teams from those that are less successful.  The results of the survey were dramatic and resulted in a series of 5 articles published on Gamasutra and numerous workshops and discussions within the games industry.  The results are presented here showing the statistical correlations that clearly identify things great teams do.  In March of this year, 2016, Paul Tozour, who lead the team in 2014, will be presenting a version of this presentation at the Game Developers Conference (GDC) in San Francisco.  

  • Liked Jas Chong
    keyboard_arrow_down

    Jas Chong - PRODUCT OWNER & DEVELOPMENT TEAM – A TANGO IN COMMUNICATION

    60 mins
    Talk
    Beginner

    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.)

  • Liked Lau Chun Yin Vincent
    keyboard_arrow_down

    Lau Chun Yin Vincent - How our Engineering team work as a Learning Organization

    Lau Chun Yin Vincent
    Lau Chun Yin Vincent
    Software Architect
    OneSky
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Beginner

    About how our startup Engineering team (~13ppl) learn, talk about the challenge, our philosophy and tactics. Inspired by different agile practice e.g. in spotify, enable interactions with processes. 


    It will be largely based on the blog post
    https://medium.com/translate-engineer-error/how-our-engineering-team-work-as-a-learning-organization-92aae2fbd26f#.jp183ulf9


    30mins should it be, when more time available it will be Q&A. 
     
    We believe

     

    • Passion is key
    • It’s about Process
    • Build expertise Inside the team
    • Maximize the diffusion rate
    • Be Measurable
    • Know the unknown unknowns

    We learn by

    1. Weekly Engineering Session
    2. OKR (Objective and Key Results) framework
    3. Expertise-based Chapter
    4. Hacking Github as a knowledge base
    5. Process for continuous and timely feedback
    6. Share often, at right channels.
    7. Stay connected with the world
    8. Nudge for good

     

  • Liked Stephanie Tong
    keyboard_arrow_down

    Stephanie Tong - The Marriage between Design Thinking and Agile

    45 mins
    Case Study
    Beginner

    Design Thinking is a human-centred way of solving the right problems that balances commercial and technical realities. Whereas, Agile is about requirements and solutions evolving through collaboration between self-organizing, cross-functional teams.

    Both have HUMAN at the core of it and it creates immense synergy to solve the right problems.

    I will go through a case study where my team has helped an international logistics company to solve its sales problems using Design Thinking and Agile.

  • Liked Nicolas Lassus
    keyboard_arrow_down

    Nicolas Lassus - UX and Agile - friends or foes?

    45 mins
    Talk
    Beginner

    The User Experience practice has many similarities to the Agile philosophy, yet the two come from different origins and are often implemented in parallel in different parts of the organisation. User Experience practitioners also often fall back to a waterfall-like methodology and fail to involve other non-design parties in the process.

    This talk aims at sharing the experience of implementing Agile to run the design and animation teams at GoAnimate, and how better user experience can be delivered by breaking down the walls between job roles: designers, developers, marketers, customer service representatives, all working together to deliver an outstanding product.

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

    We are going to share a case study of how we kick start a LeSS (Large Scaled Scrum) agile transition in FDA (Food & Drugs Administration) regulated organization. The product is a surgery X-Ray machine and the team include software engineer, mechanical engineer, electronical engineer. After one year journey, the product get shipped within one year comparing to 2.5 years of previous version. No bug was found after shipping the product so far and the build time reduced from 20+ hrs to 2.8 secs. What made these happen? One of the biggest challenges is how to enable cross-functional and self-managing team and to make it more challenging, everyone had to choose their role and teams. In this talk, I am going to share with you how we official launched the change and how we as agile coaches support in their agile journey. 

     

     

     

  • Liked Yun Ki Lee
    keyboard_arrow_down

    Yun Ki Lee - Avoiding Test Hell (with examples from FitNesse)

    Yun Ki Lee
    Yun Ki Lee
    Senior Development Specialist
    HSBC
    schedule 1 year ago
    Sold Out!
    45 mins
    Experience Report
    Beginner

    We are entering a world where everything must be done quicker. You must deliver code faster. You must deploy faster. How can you deliver and deploy faster without compromising your professionalism? How can you be sure you are delivering what your client has asked you?

    In short, testing is the only way to be sure you're delivering what someone asked you to. Often we use BDD Tools such as FitNesse which gained popularity over the recent years

    There are a number of integration / BDD test tools out there that help you deliver a high quality software through tests. Its easy to pick up any tool from just their tutorials and start writing tests. But as I found out the hard way, this can quickly spiral into a state where the tests are giving you and your team hell and are worth less than the value the tests are delivering.

    Using FitNesse and Junit as examples, I will share things that I have learnt working on large enterprise and vendor systems and help you avoid your own path to hell.

  • 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 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 Michael Mallete
    keyboard_arrow_down

    Michael Mallete - 5 Target Conditions towards Agile Adoption

    Michael Mallete
    Michael Mallete
    Agile Coach
    Odd-e
    schedule 1 year ago
    Sold Out!
    60 mins
    Talk
    Beginner

    In the book "Toyota Kata" by Mike Rother, highlighted the importance of a "target condition" towards Kaizen. Inspired by this, we had been working with multiple organizations of various sizes and plethora of domains in adopting Scrum and Agile Software Development guided by 5 Target Conditions. This talk will be about what these target conditions are, how we help organizations with these, and what results we had experienced.

  • 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 Joyce Ng
    keyboard_arrow_down

    Joyce Ng - Case studies: getting your team to scrum it

    45 mins
    Case Study
    Beginner

    In this talk I would like to give tips on how to transition your IT organization from doing waterfall development to scrumming successfully. I will also share about my own experiences in the past of introducing scrum into an existing organization. Points include:

    - Why scrum? Motivating factors to change to Agile/scrum

    - How (not) to beat a dead horse (aka your CTO) into joining the scrumwagon

    - Introducing Scrum philosophy into your workplace culture

    - Two case studies of transitioning from waterfall to scrum: encountered difficulties and obstacles and how to overcome

  • Liked Teun Hompe
    keyboard_arrow_down

    Teun Hompe - So you think you can Scrum?

    45 mins
    Talk
    Intermediate

    In this talk I'd like to share my experiences of introducing Scrum at funda. Hopefully our learnings can help you when introducing the methodology at your workplace.

    In 2012 product development (approx. 45 pax) at funda started doing Scrum. We bought post-its, we bought white-boards, we took more than the "1-per-trainee" agile card games from our agile training courses and we were good to go! Or not. Bugs messing up sprints, UX designers with never ending "design stories", developers that couldn't stop refactoring, "I'd say 3 points, because it's about 3 hours of work" and managers who feel "they're just doing whatever they want to do".

    Introducing Scrum turned out not to be as easy as we hoped. However, we kept going, kept learning and kept getting better at it. I'll share some of our mistakes, learnings and tips for others to take with them while introducing Scrum at their workplace.

  • 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.