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 tech team to adopt it.
Being a techie and  having 13years of experience implementing quality models from SEICMM, StageGate to Agile in software development, I learnt it on the job.
I have trained around 150 engineers and MBAs on Agile and Scrum models across 3 difference companies.
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.
Making the teams adopt it, is a different ball game!
Major concerns that come from team members is when and how to design the architecture. If we get stories in iterations then how do I design my system upfront. It will result in bad quality or rework. 
Through this session, the audience will get to:
 -Learn and hear real experience of how to move from teaching the tech 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.
 -Hear how we technical managers incorporated our best practices into the process lifecycle.
 -Learn how the team improvised to circle around road blocks and came up with the concept of presprint.
 -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 tech practices we followed. What were the problems and what was the wish list.

-Hear our experience from implementing Agile practices in a team that works on long running projects.

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

-Challenges we faced, both from people 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 delivery 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 us

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

Target Audience

All, leaders, team members, Agile evanglist in software development companies,tech managers

schedule Submitted 7 years ago