How is System Training/Train-The-Trainer Handled in Agile/Scrum

Last post 07:46 am August 5, 2015
by Rudolf Jan Heijink
6 replies
05:18 am July 29, 2015


In my current project, system training/train-the-trainer is often requested for new features developed.
Currently it is handled by the development team before they move on developing for the subsequent features.

Would like to know how system training/train-the-trainer typically being handled in Agile delivery and it's ownership.
If it's by development team can we consider this as part of definition of done..?

Appreciate if anyone could help shed a light.

Thank you in advance.

02:18 pm July 29, 2015

> If it's by development team can we consider this as part of definition of done..?

Does training have to be given before an increment can be released? If so, then it might reasonably be incorporated into the team's Definition of Done.

08:04 pm July 29, 2015

Agree with Ian.

11:48 pm July 29, 2015

Agree with Ian.

In my experiences, an updated help file should be ready in the end of a given sprint.
An updated help file ready is part of the sprint’s DoD.

Trainer are invited to attend the sprint review on a regular basis.

At the end of a given sprint, PO might decide the “potentially shippable” to be shipped. Before next release planning, DT supports coaching and training to the trainer.

In my teams, training is not part of DoD but is part of release activity.

10:29 pm July 30, 2015

Thanks Ian & All .

@Ching-Pei : Yes, typically DT delivers Help Files as the end of every Sprints.
Having trainers invited/attended to Sprint Review sounds helpful enough in terms of understanding the increment. Thanks.

09:13 pm July 31, 2015

You are welcome.

I'm glad my experience could help you.

07:46 am August 5, 2015

We try (and often succeed) in getting business key users involved in the development. They help us refining the backlog, do some testing and give advice to the team. Because of this involvement they are perfectly capable to train and guide other system suers. For my team, users are mainly customer services or backoffice employees. Of course, this would be completely different if your users are consumer end-users spread all over the world. Yu may apply similar concepts there, for instance using the support forum and ollow experienced customers to give advice there. This increases customer engagement and saves a lot of money.