Through tutorials, session and workshops you can learn Agile concepts. But "Spoiler alert" , what they don't tell you is that they are not sufficient to get/enable your team to adopt it.
I have trained around 150 engineers and MBAs on Agile and Scrum models in last 13years
Atulya has trained 100+ guys in similar time frame so together we have a wide experience of what kind of perspectives come when people get exposed to Agile. Many of these attendees were team leads or managers and for them learning this themselves is easy.
But making the teams adopt it, is a different ball game!
Through this session, the audience will get to:
-Learn and hear real experience of how to move from teaching the team to a stage where you can even become a bad cop and question them why do you use a practice.
-Reach a stage where team revolts if you ask them to go back to old ways of doing it.
-Learn how the team is empowered to improvise to circle around road blocks
-Hear our story of how team went from Ohh no to a new process to WOW it works!

Outline/Structure of the Experience Report

-Background context: We will share the setting, nature of work and process model as it was. What were the problems and what was the wish list.

-Hear our experience from implementing Agile practices in a team.

-We will share How we spread it to other Scrum teams. What ideas/techniques and tools we used.

-Challenges we faced, both from people, mgmt and tools. Like one of the challenge was that people were very used to old tools and needed the continuity of data. Other challenge was the wrong assumptions about Agile like go live date cannot be derived.

-Improvisations team did to work around roadblocks like the concept of presprint.

-How does the picture look now. How the current setup works. How with this being success the bottlenecks have been removed and team is now self organized and empowered to drive the releases

-Summary : In the end we plan to give a step by step guide that worked for us to empower the team and foster the culture of self-organize.


Learning Outcome

Post this session you can retrospect your approach VS what worked for me

Take home a real example of a team that did it togather

(PS: link to slides is not for this session but presentation slides I used for Agile training to software engineers)

Target Audience

All, leaders, team members, Agile evanglist

schedule Submitted 7 years ago

  • Naresh Jain
    Naresh Jain
    schedule 7 years ago
    Sold Out!
    45 Mins

    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.