schedule Mar 19th 05:30 PM - 06:15 PM place Neptune people 1 Interested

While Agile organization started to appear in last 20 years, the key principles for how we organize is nothing new and have been with us for thousands of years. In this session, I am taking a martial art "Aikido" (Japanese: 合気道) as example and going through the key principles in leadership, learning and transformation approaches. In these principles, learning Aikido are very similar to build Agile organization. Leaders are practitioners and teachers. Learning is via practices and peer learning. Changes are done in people body and mindset. We need to learn the rules, break away from the rules and ultimately create our own rules fitting ourselves and organization (Shu-Ha-Ri). Aikido is a way of life, so Agile is.

 
1 favorite thumb_down thumb_up 1 comment visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/Structure of the Talk

"Everyone has a spirit that can be refined. A body that can be trained in some manner, a suitable path to follow" - O'Sensei, Morihei Ueshiba, Founder of Aikido

Aikido (Japanese: 合気道) is a modern Japanese martial art developed to defend individuals while also protecting their attacker from injury. Aikido is often translated as "the way of unifying (with) life energy" or as "the way of harmonious spirit".

I have been practicing Aikido for the last 4 years and am currently working towards black belt. Through years of practice, I have realized the similarities between Aikido and an Agile Organization. Here are some commonalities:

Lesson 1: Leaders are Teachers and Practitioners

Like many martial arts, the teachers are also the leaders in the organization. To become a teacher of the art form, one must undergo an arduous journey that requires changes in how they act as well as how they think. These are conducted within series of trainings for the new student. Only a few of these students, those that are the most passionate and talented students, are selected as teacher candidates. Once a candidate, only with further training will a student progress to an assistant coach position. Only after assistant coach is approved, will they become the formal teacher and be recognized as a leader of the dojo. However, all this effort and the recognition of mastery of the leader does not result in gaining hierarchical control over the students. Rather, their goal is to continue to teach others become better.

Within agile, the concept of a servant leader is one who recognizes the importance of working through others, engaging and empowering others to use and improve their own capabilities. An agile leader is not one who dictates what others should do, but rather creates a system and culture where the teams learn by themselves with an emphasis of ensuring safe working environment for the teams to inevitably fail and learn.

Lesson 2: Improve through Practices and Learn from Peers

There is very little class room training for Aikido. The learning is mostly via practicing. Typical training routine starts with a short demo of teacher and assistant coach. After the brief demonstration, students are then grouped as pair (“Uke” the Receiver” and “Nage” the thrower). Thrower and receiver need to work seamlessly, as it is important that receiver willingly falls so that the thrower can learn and practice the technique. On the other side, the thrower protects the receiver via giving him or her the space to fall and ensure his or her safety. In this practice there is no differentiation of old or young, junior or senior, student or assistant coach. Everyone can learn and can teach. Without the teamwork, there is no practice and improvement in Aikido.

In Agile organization, we focus at team and whole organization success. There is limit impact for individual agile. The ecosystem work together, by practicing, improving and taking care each other. The team and organization grow together. The ultimate form of Agile is high performance teams which deliver superior business outcomes. We are “in” it together to bring the organization to next level (generative culture). Teams are empowered to learn the rules and practices from the community and peers, not simply the coaches or teachers.

Lesson 3: Shi-Ha-Ri or Embracing – Diverging - Discarding

Aikido is a martial art which can be a lifetime practice. It is generally following 3 stages.

  • Stage 1 Shu – Embracing the kata (technique). Students starts with white belt, generally progress in the next few years studying the principles, techniques and how to work with their bodies.
  • Stage 2 Ha – Diverging from the kata (technique). Black belt is a good achievement after several years and however a new start too. After mastering the foundation, the students can now find out which techniques work best for themselves. Everyone is different with height, muscle power, their preferences. This is a stage to find own self, experiment and identify what is best which works for individual.
  • Stage 3 Ri – Discarding the kata (technique). Very few people can reach out this stage and are only the true master of this art. The ultimate mastery has reached and new technique can be created

It is same for the Agile organization. We learn and apply the basic principles and organization structure so that we can start. There is no end state, however a vision to get close. Lay the foundation, practice over and over, team work. Over time we can be faster, better and feel more contented

Agile, a way of life..

Learning Outcome

I see these three lessons of learning Aikido are very similar to Agile transformations.

- Lesson 1 Leader are teachers and practitioners

- Lesson 2: Improve through Practices and Learn from Peers

- Lesson 3: Shi-Ha-Ri or Embracing – Diverging - Discarding

Agile transformation is a mindset and behaviour change which requires no only knowledge, but also self-awareness and regular practicing. The important part is to master the foundation (with patience) and know when it is time to diverge and create, which is taking time. With a right vision and determination, we will progress forward, step by step.

Target Audience

Agile Practitioner, Coach, Business/Technical Leaders, Agile Team Member

schedule Submitted 1 month ago

Public Feedback

comment Suggest improvements to the Speaker
  • Tathagat Varma
    By Tathagat Varma  ~  1 month ago
    reply Reply

    Marc, thanks for your proposal. I think it will be a very good conceptual framework for agile coaches, and even though most of the coaches claim that they *know* shu-ha-ri, the reality is quite different. So, I think your session could help in clarifying some of these longheld ideas.

    Do you have a video from a past talk that you could link us to?


    • Liked Anita Sengupta
      keyboard_arrow_down

      Anita Sengupta - The Future of High Speed Transportation

      45 Mins
      Keynote
      Intermediate

      In the global marketplace that transfers knowledge at the speed of light, we have a massive time delay and that is modern transportation methods. The hyperloop is the first new mode of transport to be created in over 100 years. The motivation is to connect people, reduce congestion, and protect our planet by eliminating CO2 emissions from terrestrial transport. The hyperloop can best be described as space travel on the ground - a magnetically levitating, electromagnetically propelled, passenger vehicle in a vacuum tube. With the elimination of aerodynamic drag and surface friction, power consumption plummets, speeds can reach 700 mph, and waste and cost are minimized. With the use of autonomy the service is on demand and delays become a thing of the past. Dr. Sengupta will discuss how space-age tech coupled to the VC funded innovation environment are enabling the revolution in green transportation from suborbital rocket flights, to electric airplanes, to space travel on the ground with the hyperloop.

    • Liked Dave Farley
      keyboard_arrow_down

      Dave Farley - Taking Back "Software Engineering": Craftsmanship is not Enough

      45 Mins
      Keynote
      Advanced

      Would you fly in a plane designed by a craftsman or would you prefer your aircraft to be designed by engineers? Engineering is the application of iterative, empirical, practical science to real-world problems. Craftsmanship is a wonderful thing, and as a reaction to the terrible abuses of the term Engineering in software development Software Craftsmanship has helped in our learning of what really works.

      The term "Software Engineering" has gained a bad reputation. It implies "Big up-front design" and "Mathematically provable models" in place of working code. However, that is down to our interpretation, not a problem with "Engineering" as a discipline.

      In recent years we have discovered what really works in software development. Not everyone practices approaches like Continuous Delivery, but it is widely seen as representing the current state-of-the-art in software development. This is because at its root CD is about the application of an iterative, practical, empirical, maybe even science based approach to solving problems in software development. Is this a form of software engineering?

      Software isn't bridge-building, it is not car or aircraft development either, but then neither is Chemical Engineering, neither is Electrical Engineering. Engineering is different in different disciplines. Maybe it is time for us to begin thinking about retrieving the term "Software Engineering" maybe it is time to define what our "Engineering" discipline should entail.

    • Liked Chad Fowler
      keyboard_arrow_down

      Chad Fowler - The Future of Software Development

      Chad Fowler
      Chad Fowler
      CTO
      Microsoft
      schedule 1 month ago
      Sold Out!
      45 Mins
      Keynote
      Intermediate

      From autonomous vehicles, 3D printed rocket engines, and “affordable” consumer-owned satellites to rapid advances in AI and secure, decentralized electronic currencies, the past several years have shown us that the only prediction we can confidently make about the future is that it will arrive more quickly than any of us imagined. Yet with all of these major technological advances, the way we develop, test, deploy, and manage software has been incrementally changing over the years. Many of the most forward-thinking paradigms, practices, and technologies are based on concepts and even implementations created decades ago.

      How can software development itself benefit from the disruptive changes in technology in recent years? This talk will explore influences, tech trends and coming innovations which will change how we as an industry approach to software creation, maintenance, management, and even employment.

    • Liked Doc Norton
      keyboard_arrow_down

      Doc Norton - Tuckman was wrong

      Doc Norton
      Doc Norton
      CEO & Founder
      OnBelay
      schedule 2 months ago
      Sold Out!
      45 Mins
      Talk
      Beginner

      Stable Teams have long been a known and accepted leading practice in agile. And Tuckman's stages of group development proves the need for stable teams, right? But what if that's not correct? Doc posits that Tuckman's is actually a disproven theory that none-the-less mysteriously persists. What if, by stabilizing teams, we solved a completely different problem? And what if by de-stabilizing teams we could better solve other problems?

    • Liked Jorgen Hesselberg
      keyboard_arrow_down

      Jorgen Hesselberg - Unlocking Agility: A Change Leader's Guide to Enterprise Digital Transformation

      Jorgen Hesselberg
      Jorgen Hesselberg
      Head of Strategy
      Comparative Agility
      schedule 1 month ago
      Sold Out!
      480 Mins
      Workshop
      Executive

      Embrace Change, Execute with Purpose

      Unlocking Agility is based on the concepts from the Addison-Wesley book by Jorgen Hesselberg, an agile transformation executive at companies such as Nokia, McAfee, and Intel. In this interactive workshop, change leaders are invited to learn what it takes to create sustainable change and embed a digitalization mindset in large organizations. Participants will leave with a set of concrete actions to pursue at their organizations and a copy of Unlocking Agility for further study.

    • 45 Mins
      Talk
      Advanced

      21st century problems cannot be solved with 20th century software architectures. So why is the starting point for so many projects built on the assumption of a simplistic monolithic, three-layer architecture sat on top of a RDBMS? Hardware has progressed. It has changed many of the assumptions that such architectures were built upon. Modern systems are distributed, deal with massive throughput of data and transactions. Users expect 24/7 service.

      The Reactive Manifesto describes what it takes to build systems that meet these demands. Such systems are Responsive, Resilient, Elastic and Message Driven. What does this mean in terms of software architecture and design? This presentation will introduce these ideas and describe how systems built on these principles work.

    • Liked Hillel Wayne
      keyboard_arrow_down

      Hillel Wayne - Designing and Testing Distributed Systems

      Hillel Wayne
      Hillel Wayne
      Author
      Practical TLA+
      schedule 1 month ago
      Sold Out!
      45 Mins
      Demonstration
      Intermediate

      Distributed systems are hard. How do you test your system when it's spread across three services and four languages? Unit testing and type systems only take us so far. At some point, we need new tools. Enter TLA+. TLA+ is a specification language that describes your system and the properties you want. This makes it a fantastic complement to testing: not only can you check your code, you can check your design, too! TLA+ is especially effective for testing concurrency problems, like crashes, race conditions, and dropped messages. TLA+ is so effective for this that both AWS and Azure teams consider it essential to their work. It keeps subtle, serious bugs out of their code and helps them optimize without losing correctness. And it's not just for the cloud: engineers have used TLA+ to verify everything from business workflows to video games. This talk will focus on why we need special tools to deal with distributed systems, how TLA+ fills that role, and how it's useful for real-world problems.

    • Liked Todd Little
      keyboard_arrow_down

      Todd Little - KMP-I: Kanban System Design

      Todd Little
      Todd Little
      CEO
      Lean Kanban Inc
      schedule 1 month ago
      Sold Out!
      960 Mins
      Workshop
      Beginner

      This 2-day Foundations-level Kanban training class, certified by Lean Kanban University, is for managers, developers, and anyone wanting to learn the fundamentals of the Kanban Method. The class includes the use of a Kanban simulation as well as exercises to design an actual Kanban system.

      Lean Kanban University Certification

      Are you looking for an internationally recognized certification in the Kanban Method? Delivered by experts accredited by Lean Kanban University, this course satisfies one requirement toward the Kanban Management Professional (KMP) credential. The KMP II: Kanban Management Professional class will complete the KMP status requirement.

    • Liked Brian Robertson
      keyboard_arrow_down

      Brian Robertson - Experience Holacracy

      Brian Robertson
      Brian Robertson
      Pioneer
      Holacracy
      schedule 1 month ago
      Sold Out!
      480 Mins
      Workshop
      Beginner

      Experience Holacracy for yourself!

      The workshop introduces the theory and practice of Holacracy, a new way of structuring, governing, and running a company. Holacracy fundamentally changes how decisions are made and how power is distributed. The goals of Holacracy are bold: make your organization more agile and responsive, increase clarity —that means to determine who does what, expects what, and decides what—minimize 'office politics', and enable deeper employee engagement and empowerment.

    • Liked Diane Zajac
      keyboard_arrow_down

      Diane Zajac - Stop Building Useless Software

      Diane Zajac
      Diane Zajac
      Agile Enabler
      OnBelay Consulting
      schedule 2 months ago
      Sold Out!
      90 Mins
      Workshop
      Beginner

      Useless \ˈyüs-ləs\

      use·less: not fulfilling or not expected to achieve the intended purpose or desired outcome.

      [Synonyms: futile, to no avail, (in) vain, pointless, to no purpose, hopeless, ineffectual, ineffective, to no effect, fruitless, unprofitable, profitless, unproductive]

      If you want to stop building useless software, then you have to start understanding your customers. Unfortunately, there’s no magic trick for reading their minds. But there is a simple technique that can help you gain insights and build empathy for them.

      Empathy mapping is a simple activity for your team, stakeholders and anyone else who is responsible for delivering products and services. It allows you to collectively explore what your customers see, hear, say & do, as well as consider what they think and feel. This leads to insights about their pain and potential wants which are the keys to building more useful software.

      In this session, Diane guides you through building an empathy map, showing you how to use silent brainstorming to encourage everyone to contribute. You will see, first-hand, how easy it is to work collaboratively to create a shared understanding of the customer. And that is the first step to start building software that customers find useful.

    • Liked Doc Norton
      keyboard_arrow_down

      Doc Norton / Diane Zajac - Escape Velocity - Better Metrics for Agile Teams

      Doc Norton
      Doc Norton
      CEO & Founder
      OnBelay
      Diane Zajac
      Diane Zajac
      Agile Enabler
      OnBelay Consulting
      schedule 2 months ago
      Sold Out!
      480 Mins
      Workshop
      Intermediate

      If your team uses velocity for planning but you don't find it very useful, this workshop is for you.

      If your manager or scrum master or other pseudo-authority figure keeps obsessing over your velocity, this workshop is for you.

      If you want to know about better ways to forecast when a piece of work will be done or how to gather data that actually helps your team, this workshop is for you.

      In this interactive workshop, Doc and Diane share insights into metrics and how they can be used to improve your team's performance. From cumulative flow diagrams to lead time distribution charts to forecasting using Monte Carlo simulation and more, you'll come away with the ability to better forecast when work will be done and better diagnose issues with your process.

    • Liked Deborah Hartmann Preuss
      keyboard_arrow_down

      Deborah Hartmann Preuss / Ellen Grove - Facilitating for Effective Collaboration...One Nudge at a Time

      Deborah Hartmann Preuss
      Deborah Hartmann Preuss
      Co-Founder
      Agile Coach Camp
      Ellen Grove
      Ellen Grove
      Agile Coach and Trainer
      Agile Partnership
      schedule 1 month ago
      Sold Out!
      480 Mins
      Workshop
      Intermediate

      Are you fed-up with participating in unproductive meetings that waste time, energy and enthusiasm? We believe everyone deserves well-facilitated meetings and events that make the most of everyone’s knowledge in the room - or the video call. Overcoming old patterns and habits for group interactions can be challenging, but by making small changes to how people are set up to work together you can create surprising improvements!.

      In this workshop, we will share facilitation techniques for nudging group interactions towards increased participation, self-organization, and better decision-making. Together we’ll explore what it means to ‘hold space’ and give control back to the group while maintaining focus on getting things done together. In addition to learning about facilitation itself, you’ll learn in two additional ways - in the morning, by being facilitated by us - and in the afternoon, by understanding how we facilitated you, and why it works. You’ll also receive a resource list, so you can follow up on the methods that interest you.

      Whether you lead meetings or just participate: you can influence your group’s interactions by introducing simple facilitation hacks. You will leave with a concrete next step, and a set of activities and techniques to start using right away, to enliven your meetings and achieve more satisfying outcomes.

    • Liked Hillel Wayne
      keyboard_arrow_down

      Hillel Wayne - Test-Driven Architecture

      Hillel Wayne
      Hillel Wayne
      Author
      Practical TLA+
      schedule 1 month ago
      Sold Out!
      480 Mins
      Workshop
      Intermediate

      Traditional architecture techniques are ill-suited to the fast iterations of agile development. Agile architectures need to evolve continuously based on the customer's needs, which requires flexibility and automated verification. Our diagrams and UML provide neither.

      We can do better, though: just as we have test-driven development, we also have test-driven architecture. By using a specification language we can quickly design complex systems, verify their properties, and explore the effects of new features. Best of all, we can do this all before adding new code, catching design bugs at the beginning of our sprints instead of the end.

      This workshop will introduce you to the Alloy specification language and through it the idea of Test-Driven Architecture. Some experience with design and testing is highly recommended. Familiarity with database design and predicate logic will be helpful but not necessary.

    • Liked Dave Farley
      keyboard_arrow_down

      Dave Farley - Acceptance Testing for Continuous Delivery

      90 Mins
      Tutorial
      Beginner

      Writing and maintaining a suite of acceptance tests that can give you a high level of confidence in the behaviour and configuration of your system is a complex task. In this session, Dave will describe approaches to acceptance testing that allow teams to:

      • work quickly and effectively
      • build excellent functional coverage for complex enterprise-scale systems
      • manage and maintain those tests in the face of change, and of evolution in both the codebase and the understanding of the business problem.

      This workshop will answer the following questions, and more:

      • How do you fail fast?
      • How do you make your testing scalable?
      • How do you isolate test cases from one-another?
      • How do you maintain a working body of tests when you radically change the interface to your system?
    • Liked Dave Farley
      keyboard_arrow_down

      Dave Farley - Advanced Deployment Pipeline Techniques

      Dave Farley
      Dave Farley
      Independent Software Consultant
      Continuous Delivery Ltd
      schedule 2 months ago
      Sold Out!
      480 Mins
      Workshop
      Intermediate

      The Deployment Pipeline is a central concept in Continuous Delivery. It represents an effective, controlled channel through which all changes destined for production pass.

      A defining objective in CD is to work so that our software is always in a "releasable state". By applying high levels of automation to our development process, in the form of a Deployment Pipeline, we pass all changes to our production systems through this channel and evaluate them prior to release.

      This means that the pipeline quickly becomes a strategic resource.

      As our use of this important tool grows, the performance of the pipeline, in terms of the rapidity with which it can give valuable feedback on the quality of your work, becomes a central concern.

    • Liked Diane Zajac
      keyboard_arrow_down

      Diane Zajac / Doc Norton - Collaboration Contracts

      90 Mins
      Workshop
      Beginner

      Not all team decisions need to be made by the entire team. There. Someone said it. In some cases, we can trust a single individual to make the decision because they have the most experience and insight. In other situations, we want a variety of interests and perspectives included to ensure a well-considered, unbiased decision. But how do we decide who and what and when?

      Put down the RACI chart - there's a better way! A Collaboration Contract is a simple tool that allows team members to opt into conversations and decisions. With a Collaboration Contract, teams identify the decision makers, and through an open selection process, establish their desired level of autonomy. This is a not a decision-making tool, but a tool for assembling the decision making team with clear expectations and agreements.

      Join Diane and Doc in this hands-on workshop where you will learn what it takes to run your own Collaboration Contract. Learn this powerful technique today and establish clearer decision making for your team tomorrow.

    • Liked Dave Farley
      keyboard_arrow_down

      Dave Farley - The Rationale for Continuous Delivery

      45 Mins
      Talk
      Intermediate

      The production of software is a complex, collaborative process that stretches our ability as human beings to cope with its demands. Many people working in software development spend their careers without seeing what good really looks like. Our history is littered with inefficient processes creating poor quality output, too late to capitalise on the expected business value. How have we got into this state? How do we get past it? What does good really look like? Continuous Delivery changes the economics of software development for some of the biggest companies in the world, whatever the nature of their software development, find out how and why.

    • Liked Doc Norton
      keyboard_arrow_down

      Doc Norton - Escape Velocity - Better Metrics for Agile Teams

      Doc Norton
      Doc Norton
      CEO & Founder
      OnBelay
      schedule 2 months ago
      Sold Out!
      45 Mins
      Talk
      Intermediate

      If your team uses velocity for planning but you don't find it very useful, this session is for you.

      If your manager or scrum master or other pseudo-authority figure keeps obsessing over your velocity, this session is for you.

      If you want to know about better ways to forecast when a piece of work will be done or how to gather data that actually helps your team, this session is for you.

      Doc Norton briefly addresses some issues with velocity, looks at root causes for said issues, and then dives into other, better metrics. You'll be able to better forecast when work will be done and you'll be better able to diagnose issues with your process and work toward correcting them.

    • 45 Mins
      Case Study
      Beginner

      The Principles in the Agile Manifesto provide us guidance on how to have an Agile mindset in our organizations. Principle 11 within the Manifesto states "The best architectures, requirements, and designs emerge from self-organizing teams". While this works well for autonomous teams, it proves to be challenging for large organizations with dozens or even hundreds of teams who need to share common architectures and design patterns.

      This talk will present a case study of a large retail organization and explore their journey from a highly centralized/governance-based technology organization to a more distributed/collaborative one and explore their lessons learned and success/failure patterns along the way. In the end, we'll answer the question about whether or not Principle 11 scales!

    • Liked Dave Farley
      keyboard_arrow_down

      Dave Farley - Farley's Laws

      45 Mins
      Talk
      Intermediate

      We are not as smart as we think we are. Even us software developers!!

      What we think of as reality isn't. When we think we are being rational, we are not. When we listen to experts and trust in their wisdom, we are fooling ourselves.

      Meanwhile, software development is one of the more complex tasks that we mere mortals undertake. So what does it really take to overcome the limitations of our biology? How do we overcome our desire to jump to conclusions and guess at solutions?

      This mildly humorous, entertaining talk explores some of the fallibilities inherent in our biology and addresses what it takes to solve genuinely complex problems in the face of our propensity to make wild guesses?

      To put it another way, what do you need to understand to completely grasp how agile, lean development, DevOps and Continuous Delivery really work?