You have been doing agile for a few years now.

With a regular cadence you have retrospectives and a lot of problems and great improvement opportunities are raised but nothing seems to really improve. Stop doing retrospectives!

Can we shift form collecting problems and start improving? Create the habits of continuous improvement.

It can be done is time to start using Toyota Kata!

Toyota Kata is two behavior patterns, or Kata’s, that is the foundation in Toyota’s continuous improvement work.


Outline/Structure of the Talk

- What is Toyota Kata

- What is IK and CK

- Toyota Kata in Practice

- - How Toyota Kata is beneficial instead of sprint retrospective

Learning Outcome

In this session you will get a introduction to Toyota Kata. You will see how a team goes through the two Kata’s and improves its way of working.

Target Audience

Scrum Master, Agile Practitioners, Agile Coaches,

schedule Submitted 6 years ago

  • Vijay Bandaru

    Vijay Bandaru - Scrum Master - The Team Spirit Guardian

    Vijay Bandaru
    Vijay Bandaru
    Agile Coach
    IVY Comptech
    schedule 5 years ago
    Sold Out!
    45 Mins

    Lord Krishna was our first Scrum Master who helped "Pandavas" to win the "Kurukshetra" war without using a single weapon. On top of it, he was the almighty with so many invisible powers, but he still guided the "Pandavas" through his servant Leadership.

    Inspired by this concept, I have created a session to highlight the role of a "Scrum Master" and how can we make a Scrum Master a true "Servant Leader" without so much depending on authority or tools rather concentrating on simple things that can make his contribution to the team a true differentiating factor.

    In this task, I am going to cover the following topics:

    - Understanding the team formation stages

    - 5 dysfunctions of teams

    - Gauge the team members' behaviours

    - How a Scrum Master can make his team GREAT

    - Soft skills for Scrum Master

    - How a Scrum Master help his team in various situations

    - Importance of learning for a Scrum Master

    - Scrum Master's backlog for his team's improvements

    - Scrum Masters checklist

    I will also cover anti-patterns of Scrum Master in this session along with suitable remedies.

  • 60 Mins

    Active Product Management is about focussing more on the active backlog items, i.e items planned for the shorter increment (Potentially Shippable Increments), rather than focussing on the complete backlog set planned for the whole release.

    Many Organizations over the past few years have embraced agile and have experienced good results. Even after this transition to agile and following for several years, Organizations still face difficulty to release the software to the customers as per the commitments.

    Would like to discuss the general problems with the traditional way of doing release planning and how "Active Product Management" can reduce the risks in delivering the commitments.

  • Madhavi Ledalla

    Madhavi Ledalla - The essence of Product Ownership

    Madhavi Ledalla
    Madhavi Ledalla
    Agile Coach
    schedule 5 years ago
    Sold Out!
    60 Mins

    Scrum introduces a very vital role called the Product Owner who is the key person responsible for the product success; he is one who is accountable for the customer delight.

     In this session we would be doing a deep dive at this role, the essential characteristics, the prime responsibilities, challenges and how can this role be scaled in a scaled environment where we would be discussing some of the structural and coordination patterns.

    The key take away of this session would be the last part where the participants would build a story map using “Jeff Patton’s” story mapping technique to visualize how a day of the Product Owner looks like.

  • Sanjay Kumar
    Sanjay Kumar
    Agile Coach & Trainer
    schedule 6 years ago
    Sold Out!
    60 Mins
    Case Study

    Agile design or emergent design relies heavily on timely refactoring efforts that aim to improve existing design. Yet often, when the code base grows or when someone else's code is handed over to us, there is a reluctance to refactor existing code - despite an obvious design smell. While the reasons to avoid refactoring may be well-grounded – lack of time, lack of understanding or fear of breaking it – in the long term, delaying code refactoring makes the code rot further. And, as a result, technical debt continues to pile up.

    This session begins by reviewing common design smells, discusses five key features of good code and then discusses a common yet often overlooked design smell in detail – big methods. Using an example of a big method, it proposes a refactoring strategy that will ensure that a refactoring effort does not cause any negative side effects. During the session, participants are walked through a real code refactoring example – step by step.

    Though the session focuses on one particular design smell (big methods), the proposed refactoring strategy should apply equally well to other design smells too.

  • 45 Mins

    The session will start with introducing agile estimation (5 mins), and differentiate it from traditional estimation approach and the same will be demonstrated by an activity (15 mins)


    Conflict management is a continuation to the agile estimation technique, sometimes due to conflict also we cannot arrive at a useful estimation. How agile coaches handles conflict management (5 mins), we will do an activity to understand conflict management and its resolution (15 mins)

    conclusion and questions (5 mins)