Applying Timeline Technique in Agile Transformation

This workshop is about how to apply the time line technique from Neuro-Linguistic programming (NLP) in Enterprise Agile transformation.

The timeline technique is a tool used in NLP to pre-write your future. It gives an individual all what he need to reach his goal.

This workshop is about learning the timeline concept and also understanding how it can be used in Enterprise Agile transformations.

1. Timeline technique helps the stakeholders to define realistic goals about their transformation.

2. This will also enable them to pre-write the future of the transformation.

 

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

Outline/structure of the Session

Introduction to NLP

Introduction to Timeline technique

Why it works : Why timeline works

When did it worked for us : Facilitator will help the audience to recollect and incident 

Exercise : Let's do it!

Debrief

How do we apply this technique in my organization! : Applications

Q&A

 

Learning Outcome

Basic understanding of NLP

Introduction to Timeline technique

How to use this technique in change management (even in personal life).

How to use timeline technique to improve an Enterprise Transformation.

 

 

Target Audience

Leadership, Agile coaches, Scrum masters, Product Owners

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Ravi Kumar
    By Ravi Kumar  ~  1 year ago
    reply Reply

    Hi Ebin,

    Thanks for the proposal and the topic looks interesting. I'm trying to understand how the technique is applied in the agile transformation but feel the majority of the talk is centred around NLP/Timeline based on the outline. I'm sure the details are worked out in your head. For the benefit of us reviewers to better understand can you please share a working copy of the slides.

     

    Thanks,

    Ravi

    • Ebin John Poovathany
      By Ebin John Poovathany  ~  1 year ago
      reply Reply

      Hi Ravi,

      Thank you for the comment. I am working on the slides. This is more of experiencial learning not a slide based discussion. But for ease of understanding and review, I am preparing a deck. I shall release it this week.

       

      Thanks,

      Ebin


  • Liked Pavel Dabrytski
    keyboard_arrow_down

    Pavel Dabrytski - Agile Economics: Contracts, Budgets, Capitalization

    Pavel Dabrytski
    Pavel Dabrytski
    Agile Coach
    Think Agile
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Advanced

    How much does one story point cost? Is Sprint 0 an expense or an asset? Can you run Scrum with a fixed-cost contract? Agile challenges the existing approach to financial aspects of running projects: i.e. budgeting, forecasting, financial planning and vendor contracts.

    Applying new financial models becomes increasingly important for larger organisations adopting Agile. While they are going through an Agile transformation, they also need to maintain transparent financial governance and reporting. Shareholders would not be too excited about messy Annual Financial Statements.

    Join me if you would like to know more about Agile Economics. No financial degree is required and all the content explained in plain English with plenty of pictures!

  • Liked Evan Leybourn
    keyboard_arrow_down

    Evan Leybourn - If you need to start a project, you’ve already failed #noprojects

    45 mins
    Talk
    Beginner

    I want to be controversial for a moment and propose an end to IT projects, project management & project managers. I propose that the entire project process is flawed from the start for one simple reason. If you need to run a project, you've already failed.

    By definition, an IT project is a temporary structure to govern and deliver a complex change (such as a new product or platform) into an organisation. However, to be truly competitive, an organisation needs to be able to deliver a continuous stream of change. Managed properly, this negates the need for a project and the associated cost overheads.

    This is fundamentally what #noprojects is. The approach, structure, tactics and techniques available to successfully deliver continuous change. At its core, #noprojects is predicated on the alignment of activities to outcomes, measured by value, constrained by guiding principles and supported by continuous delivery technologies.

    This presentation will introduce you to #noprojects. You will learn how to define an outcome and create an Outcome Profile. You will also learn how to manage change within the context of an outcome through the Activity Canvas.

  • Naresh Jain
    Naresh Jain
    Founder
    ConfEngine.com
    schedule 2 years ago
    Sold Out!
    45 mins
    Keynote
    Advanced

    On Agile teams, collaboration is the way of life. Our leaders want their team members to work closely with each other, have shared goals and even think as one entity. Why? Because we believe that collaboration leads to happier, more productive teams that can build innovative products/services.

    It's strange that companies use the word collaboration very tightly with innovation. Collaboration is based on consensus building, which rarely leads to visionary or revolutionary products/services. Innovative/disruptive concepts require people to independently test out divergent ideas without getting caught up in collaborative boardroom meetings.

    In this presentation, Naresh Jain explores the scary, unspoken side of collaboration and explains in what context, collaboration can be extremely important; and when it can get in the way or be a total waste of time.

  • Liked Ellen Grove
    keyboard_arrow_down

    Ellen Grove - Everything Is Better When We Stick Together: Building Team Working Agreements

    90 mins
    Workshop
    Beginner

    Whether a team is brand-new or seasoned veterans at working together, explicitly defining and/or refining a team working agreement will help the team to align on how they will work together effectively to meet their common goal. In this fast-paced hands-on session, participants will go through the process of building a team working agreement using LEGO Serious Play (LSP).

    Creating a team working agreement helps team members set the stage for effective communication and high performance by making assumptions about ‘what really matters to us’ and ‘how we will work together?’ explicit and negotiable.  Great working agreements address some difficult topics - what values do we share? how do we want to deal with conflict when it comes up? how will we handle problems within the team? - which are often challenging to discuss openly and honestly, especially when a team is first assembled.  

    This session will show you how to use LEGO Serious Play to encourage a frank and fearless discussion in order to kickstart these discussions so that a team can quickly create a powerful set of simple guiding principles for working together.  Participants will learn about the importance of team working agreements in creating team cohesion and common understanding of shared values and operational guidelines, and experience hands-on how to use the LEGO Serious Play cycle of build-share-reflect to have a participatory discussion to identify shared values, explore reactions to conflict, and build a set of simple guiding principles.

     

  • Liked Krishnamurty VG Pammi
    keyboard_arrow_down

    Krishnamurty VG Pammi - Lean Scrum - The need of the hour

    Krishnamurty VG Pammi
    Krishnamurty VG Pammi
    Agile Coach
    IVY Comptech
    schedule 2 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    The 2015 state of scrum report published by Scrum Alliance states that the outlook of scrum is highly favourable. Virtually all consider it likely that their organization will use scrum in future. While this is good, the survey also noted one of the key challenges observed by survey respondents as “Product owners and teams were just not willing and/or enthusiastic about Scrum best practices”. Thus, although scrum methodologies have greatly increased productivity, scrum is not without its problems. We need to quickly address this gap.

    Keeping scrum values at the core, scrum methodology is mostly visible to teams on the ground in terms of three pillars (1) Scrum roles (2) Scrum artifacts and (3) Scrum events. While Scrum has kept scrum roles and scrum artifacts lean, it has empowered teams on the ground to learn the art of performing scrum. Scrum prescribed guidance on scrum events with clear purpose, frequency, maximum duration and recommended attendees. It recommends teams to learn the art of performing scrum events through their experience stating “scrum is easy to understand and difficult to implement”

    While some scrum teams mastered this art, I find most of the scrum teams are still struggling in this process. I come across situations where teams are not finding scrum events interesting primarily because they find these events unproductive. The result is that we see less interactions and cooperation from the teams during scrum events. This is impacting basic agile manifesto “Individuals and interactions over processes and tools". In net, there is no surprise when product owners and teams were just not willing and/or enthusiastic about Scrum best practices.

    Lean Scrum is the need of the hour. As part of lean scrum, we will adopt scrum methodology at the core and we implement lean framework to address the pain areas witnessed by teams

    As part of this talk, I will share my experiential insights on

    1. Outlook of scrum is highly favourable. Although scrum methodologies have greatly increased productivity, scrum is not without its problems. We need to quickly address these gaps
    2. While scrum has kept scrum roles and scrum artifacts lean, it has empowered teams on the ground to learn the art of performing scrum events. Are we keeping these events lean and Valuable?
    3. Lean scrum – The need of the hour
    4. What is Lean Scrum
    5. Anti-Patterns/Most frequently faced challenges/ wastes experienced by scrum teams in each of the scrum events (case findings based on my experience)
    6. Where do the scrum teams stand on "expected scrum patterns" in each of the scrum events (case findings based on my experience)
    7. Leverage "Lean Framework" to craft scrum events towards value generation. How to draw "AS-IS" and "TO-BE" Value stream management maps for two scrum events.
    8. Leverage "Lean framework" to help scrum teams to learn the art of performing scrum events through realizing value and enhancing their reach on "expected scrum patterns".
    9. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software” The term value is increasingly becoming starting point of what we do. We need to keep questioning everything we do using customer value generation as the yard stick

    Unless, we drive scrum events towards value generation by continuously eliminating waste/ anti patterns, there is no surprise that “Product owners and teams were just not willing and/or enthusiastic about Scrum best practices” as observed by "The 2015 state of scrum" report.

    This is where Lean-scrum could prove to be powerful...

     

  • Liked Regina Martins
    keyboard_arrow_down

    Regina Martins - The Spiderman antidote to the anti-patterns of Agile leaders

    Regina Martins
    Regina Martins
    Agile Coach and Trainer
    agile42
    schedule 1 year ago
    Sold Out!
    90 mins
    Workshop
    Intermediate

    Leading in an Agile environment is all about mindset and understanding what motivates people. This interactive workshop will unpack the superhero archetypes of Agile leaders with their related Agile leadership anti-patterns.

    Many leaders come into an Agile environment and feel threatened by a perceived loss of control. Successful Agile leaders empower the team and acknowledge that they can choose their own work and solve their own issues, pull themselves out of the detail and focus on supporting the team, know that if the team succeeds they do too, and are emotionally mature and are not constrained by ego.

    The best paradigm to frame the concept of leadership in Agile is that leadership is encouraged at all levels. As such everyone working in an Agile environment is a leader. In smaller organizations this is probably easy to encourage. In larger organizations, where the “Title” or “Position” predominates defines who is a “leader” and who is not, anti-patterns tend to emerge which do not support an Agile culture, even if it is the organisation’s stated vision to become Agile.

    In this instance the physical manifestations of Agile are put in place such as physical boards, Scrum ceremonies and an attempt at co-location are put in place. The danger here is that the Agile adoption will be a shallow one and will remain superficial. When the awesome magic of implementing Agile right is not achieved then people blame Agile as being the problem. It is not Agile that makes teams, projects and adoptions fail; it is people that cherry-pick those aspects of Agile that they like and are easy to implement that put the adoption on the path to failure.

    All too often leaders dismiss Agile as something the development teams do, rather than as something which affects them too, and that their role is important for its successful adoption. The role of leaders cannot be underestimated to turn a shallow adoption of Agile and make it a deep and lasting change for the organisation’s benefit. In this case, adoption in a small team or program will start the journey toward the tipping point that will make it a lasting organizational change.

    This may cause confusion, manifested as cognitive dissonance, in the leader. They may be asking themselves these questions:

    - How am I supposed to behave in a changing environment?

    - What behaviors am I supposed show to support the values and principles of Agile?

    - How do I support support the teams now?

    This workshop is based on my learnings and experiences as line manager of a development team in a large organisation, and Agile coach in large organisations in how leaders can in many instances unknowingly "sabotage" Agile initiatives, as well as experiential insights on what the enabling leadership behaviours and characteristics are.

    As part of this talk I will share the following:

    • What are the superhero archetypes of Agile leaders.
    • What are the related Agile leadership anti-patterns?
    • Discover the antidote to these anti-patterns (or the good patterns to replace the anti-patterns).

     

  • Liked Ebin John Poovathany
    keyboard_arrow_down

    Ebin John Poovathany - When a religion is dead, it becomes ritualistic!

    Ebin John Poovathany
    Ebin John Poovathany
    Agile Coach
    GE Healthcare
    schedule 2 years ago
    Sold Out!
    20 mins
    Experience Report
    Advanced

    When we do rituals without sufficient understanding of the intent, it indicates something. Does Agile belong to that category now? 

    This talk will cover my experience with lot of organizations and teams. 

    The intention behind this talk is to re-emphasis the spirit of Agile mindset!