What should be in a tutorial on agile testing? For an overview, see ContentTutorial.

For a short description on the set up of such a tutorial, see TutorialGeneral.

Anko thinks (121204) there are two types of Attendees:

1) experienced, traditional trained testers. They are 'poisened' by IEEE, ISEB, BCS and CMM. They are supporting the thoughts of the QualityPolice? and FactorySchool?.

2) more or less experienced ' agilists ' who want to know more about agile testing in general, maybe even thinking about taking on the tester's role.

It looks quite difficult right now to write a tutorial that is interesting fopr both groups.

So far we have these main topics:

- TheAttitudeOfAnAgileTester

- TheRoleOfAnAgileTester

- TheSkillsOfAnAgileTester

Anko thinks he feels quite safe on the attitude topic (paradigm shift!) and the role topic (ContextDrivenTesting?!), but not on the skills. What hardcore testing skills should an agile tester have? I think usage of tools is of great importance, but I'm not (very) experienced on that one.

Can we come up with a set of ToolsforAgileTesters?

I'm not sure what a good way is to set this up, there are several possibilities:

1. What is agile@? use the four values of XP as the basic layout
2. What is different@? take off from a traditional point of view: what is different when following the phases Planning&Control, Preparation, Specification, Execution and Completion. This is the TMAP model (www.tmap.net) and is very familiar in the Netherlands.
3. What is written@? take the layout of Lisa's book as a road map
4. ...suggestions?

Back to AgileTesting