Any large team starts with one member at a time and the practices and the underlying culture is critical right from the beginning. This session is about practical ways of using Agile practices for doing knowledge transition. 

Three levels of knowledge transition continues to happen in a self organising team

A. Transitioning roles within teams such as developer to analyst, scrum master transition, analyst to developer, any new team member onboarding

B. Transitioning knowledge inter teams such as bringing a new team upto speed, domain or technology

C. Handing over Transition such as one vendor to the other, one geography to the other

Discuss best practices, practical tips and important anti-patterns to watch for


Outline/Structure of the Talk

Transition Framework consists of Planning, Transition, Assisted, Primary phases. During all the four phases its important to have demo/review along with a retrospective to have a clear understanding of gaps and the bright spots.

Key areas to watch for during any transition (such as)

1. Is the expectation set between the team (member) taking transition and the team (member) giving transition

2. Capacity planning

3. Metrics (During Transition, Assisted and Primary phases)

How does transition differ in the three levels of transition and managements' role in all the three levels of transition (within team, across teams, across vendors/geographies)

Anti patterns to watch for

Learning Outcome

Participants would have a clear understanding of 

- A clear framework to use in the various transition needs while using agile

- Ability to understand and gauge transition preparedness

- Get a view of scaling practices and create a visual board for scaled transition practices

Target Audience

Analyst, scrum masters, managers, leaders


schedule Submitted 4 years ago

Public Feedback

    • Vishweshwar Hegde

      Vishweshwar Hegde - Mindfulness: Cultivating Agile Minds

      20 Mins

      Agility starts with Mind. It’s about open, curious, energetic mind constantly looking for doing better things and in better ways. Such Agile Minds manifest in proactively sensing market/customer opportunities/needs early, quickly adopting to changes  to create new value in the changing contexts, continuously learning, exploring & experimenting new things. It requires courage, self-drive and taking people along. If we notice, all these characteristics are distilled in Agile Values & Principles.

      But how to develop Agile Minds? Typically our education system and corporate trainings  are predominantly IQ oriented; whereas Agile Mind is about Emotional Intelligence (EQ) – self awareness, self regulation, self motivation and empathy. EQ is an essential ingredient for a culture of self-organizing, collaboration and servant leadership – which are the tenets of good Agile culture. Mindfulness is a practical & effective toolset to cultivate EQ and create Agile Minds. 

      Being a Mindfulness practitioner, this talk will cover my experiences of consulting & coaching on Mindfulness in organizations driving Enterprise Agility.

    • Shiv Sivaguru

      Shiv Sivaguru - DevOps and the Software lifecycle - in 10 aspects

      20 Mins

      There has been a lot of expectation around DevOps and discussion on what DevOps is and is not. 
      While most of the buzz is around tools, culture, automation etc, there is not much on the impact on the software delivery life cycle.
      In this session, I propose to overlay the implication of DevOps thinking on the lifecycle - from concept [backlog] to delivery [to the user]

    • Gayatri Devi Kalyanaraman

      Gayatri Devi Kalyanaraman - How to continuously improve your team dynamics using Retrospectives?

      45 Mins

      One of the key constructs of Agile is imbibing the 'Kaizen' model of continuous improvement and customize it for the product side of the delivery and the process side of team environment. The best part of Agile is using 'Retrospectives' at its core where teams use the formal meeting to understand what can be done better and what we are doing well.

      This session is to harness other ways of conducting or facilitating retrospectives that would make it even more engaging and deepen the sense of purpose along with the relationship established with the team.

      First one would be to use Johari Window's construct to widen the shared understanding and reduce the blindspots for not only the team members  individually but reduce the vulnerabilities within the team.

      Second one is to use Futurespectives to set a vision for the product/program using design thinking tools and elevate the understanding of the  goals and objectives in order to bring alignment between business, IT and operations stakeholders.

      Third part of the workshop would be to identify anti-patterns in agile practices and how to smell the first whiff and nip those practices quickly. This would be done using retrospective as a tool to identify the root cause for anti-patterns

    • Paramu(Parameswaran) Kurumathur

      Paramu(Parameswaran) Kurumathur - Agile Mindset – Nature or Nurture?

      45 Mins

      In this session we establish that the Agile Mindset of self-organisation is a natural set of attitudes, in-born in people, rather than a learnt one. We also establish that hierarchical approaches like the waterfall model are ones imposed on practitioners’ minds by existing practices and environments.

      Understanding that the self-organising way is more natural, we look at various ways to unlearn the learnt hierarchical mindset and get back to the natural self-organising mindset