Looking deep into the three pillars of empiricism (transparency, inspection and adaptation), adaptation requires several things that an individual on an agile team can do and which direction the organization needs to steer towards. Is it the mind-set? or creating a safe environment for people to learn from failure? or is it many subtle to other glaringly obvious reasons? I found that adaptation requires gathering data to be inspected, use this data to identify areas of improvements, act on it and become a better individual. Organizations need to do the same thing in terms of identifying areas of improvements for individual safety, empowerment - act and create a better environment.

How do we do that? Is this an art or a science? What can we learn from Chameleons? Chameleons are best known for their ability to change their colors and several other characters of adaptability. What are some of the signs of a person who is adaptable? We will have an interactive discussion on this topic and learn what traits may best help us be adaptable? What do organizations need to do to support adaptability?

 
 

Outline/Structure of the Presentation

Introduction - 2 min.

  • Adaptability is important and needs experimentation, gathering of key data that can be applied to making improvements. How do you do that?

Three pillars of empiricism - 3 min.

  • Transparency, inspection and adaptation - all three pillars are key to gathering data points, using those data elements to gain knowledge useful in decision-making and focus on adaptation.

Organizational Safety, agility and adaptation - 5 min.

  • What are the areas that you have seen in your organization that helped provide that feeling of safety? How flexible were they in empowering people to make those decisions? Did they frown upon when things didn't work? or did they provide you the flexibility to learn from those failures (let people gather that data), and inspect & adapt?
  • Use the Scrum Tree that I created to build the conversation http://agilekingdom.com/scrum-tree/

Signs of an adaptable person - Interactive session - 20 min

  • Activity - Will go through table discussions and share ideas with the session participants:
  • Being open-minded?
  • Patience ,
  • Able to experiment,
  • Empowered to make decisions
  • Creative? Innovative?

What can an organization do to support adaptability? Interactive session- 10 min.

Summary - 5 min.

Learning Outcome

Participants will share their knowledge with each other about the importance of adaptation to be agile. Participants will also understand what an organization should do make this important shift by supporting these characteristics of adaptation.

Target Audience

Anyone who wants to learn to adapt

Prerequisites for Attendees

Agile basics

schedule Submitted 1 year ago

Public Feedback


    • Liked Raj Kasturi
      keyboard_arrow_down

      Raj Kasturi - Is Scrum good for solving big data challanges?

      Raj Kasturi
      Raj Kasturi
      President
      Qwerty Inc
      schedule 1 year ago
      Sold Out!
      45 Mins
      Presentation
      Intermediate

      Big data is huge! with billions and billions of data sets and a need to analyze and apply that to real-life problem-solving is a challenge. Are traditional

      Let's take a look at the current state of big data, if traditional methodologies are providing the necessary answers quick enough. Is Agile/Scrum a good fit for big data?

      - big data in any industry
      - high data availability, real time analytics, data warehousing
      - agile spectrum and where do my projects fall?
      - big data complexity and empirical process control theory
      - current industry trends
      - metrics
    • Liked Raj Kasturi
      keyboard_arrow_down

      Raj Kasturi - Top 10 Scrum Anti-Patterns to avoid

      Raj Kasturi
      Raj Kasturi
      President
      Qwerty Inc
      schedule 1 year ago
      Sold Out!
      45 Mins
      Presentation
      Advanced

      An anti pattern is a frequently used, but largely ineffective solution to a problem. The term was originally used to refer to a pattern gone wrong. As Scrum practitioners, we all know that Scrum has events, artifacts, roles and rules. If the core principles, foundation ideas or the agile manifesto is 'tweaked' hoping they would provide benefits because teams are not seeing immediate results, this may result in an anti pattern. This in turn may become an ineffective solution to a problem

      The founders and co-founders are right, in frame-works like Scrum are founded on empirical process control or empiricism and teams need to follow certain rules to be successful! In this interactive session, we will identify the anti patterns that some teams have developed and formed bad habits that made it difficult for them to go back to those fundamentals.

      We will discuss why the core principles are very important to the success of Scrum Teams and talk about specific anti patterns in terms of events, artifacts, roles and rules. Rules may be important, however is it important to apply the basic principles that may help us to do the right thing in any situation without resorting to rules? I want to share my experience of working with agile teams for the past 10 years and talk about real-life examples that I have seen in my experience. More importantly, the participants will identify and discuss the antipatterns they have observed in their daily life.