Pain Point: Often Trainings are done through a window of One week or a couple of days. This kind of concentrated training approach gives rise to specifically two points • Lesser retention in the long run as people tend to forget things that they do not practice • In case of countries/regions where language is a challenge between the trainer and the trainee, it results in discontent and often greater misunderstandings on the concept Fall out: As a result of this kind of approach, often when as Agile coaches we start sprint cycles with the teams, we often find multiple anti patterns cropping up very soon. This results in induced delay in team maturity improvements and not to mention the heart burns and escalations Resolution – The Model of Training that I am going to give an insight on through the talk as part of this conference is something that I call “Play and Learn” (a design to tap into the ever inquisitive child in an individual). It involves how to plan training in a scattered model spanning 2-3 sprints and how to adapt your training content based on the progress, understanding and preferred mode of learning by the team. It would involve a practice to quickly create a training content based on your observation as a trainer or a coach as to what training methods – visuals/activity based / audio based/or interactive game based is working for the team that you are working with. It works on the “Inspect and Adapt” principle of any Agile delivery. The added advantage to such a training schedule is that, even with the training going on the team can still deliver value to the market with the contents that they have albeit a bit slower
Piet Heinkade 179
Amsterdam 1019 HC
Netherlands
Sprints
Inspect and Adapt
Play and Learn