Agile Principles 101
So too is that excruciating inner desire of wanting to teach all of the things (especially the things that took me a long time, and I learned the hard way)! But you only get a few minutes, hours or days in the lives of those whom you wish to help and there is a limit to how much of an impact you can make in those few short moments of time!
Now for some truth of this widely used, common, dare I say - standard or best practice - approach...
In a nutshell, the pro's of this approach are:
- The trainer gets at least a 6 minute break
- The trainer can "tick the box" on the "we covered the basics" section / poorly defined learning outcomes
- Only 1 slide!
- Only 1 page to print for the pack for the attendees
- Lots of nods from the trainees - the words do seem sensible - which makes all trainers feel good inside!
- Very few questions (in 4 minutes) if any, and, no time to get into any real detail of either the trainer's experience(s) or learners' experience(s) - so only quick superficial answers or "park that one" statements to move along!
The con's of this approach are:
- Zero positive effect on the learners
- Sometimes negative impact on the learners as they begin to logically unpack and envision applying in their own organisation and discover stumbling blocks with all or nearly all of the principles!
- Learners feel rushed
- Learners realise the trainer might not be a good one or that the training content might not be good
No one can apply anything that is read from a densely packed and boring slide like this! The agile principles are too concise and need expansion/discussion to help people interpret them correctly singly and collectively, and within the context of the learners which is unique from group to group, team to team and individual to individual. It's a subjective perspective thing!
I suggest don't teach or try to learn the agile principles this way, please. It's simply a waste of time and energy. I have many more experiences and ideas which I am sharing on What Is Agile For