meet the cat! · cat –certified agile tester isqi als zertifizierungsstelle firmensitz: potsdam...

Meet the CAT!

Werner LieblangCAT Trainer, Díaz & Hilterscheid GmbH

CAT – Certified Agile Tester

iSQI als Zertifizierungsstelle

Firmensitz: Potsdam & Erlangen

6 Kontinente, 6 Sprachen

2004 als Tochtergesellschaft des ASQF e.V.

(Arbeitskreis Software-Qualität und -

Fortbildung e.V.) gegründet

1000 Vereinsmitglieder DACH: (z.B. Microsoft,

SAP, Siemens, Bundesbank, O2, HP,

Fraunhofer FOKUS, Hochschule Bremen)


Díaz & Hilterscheid Unternehmensberatung GmbH

Mittelständiges Beratungshaus, Berlin, gegründet 1998

Financial Services (bankfachliche Beratungsthemen)

IT Management & Quality Services (IT Beratung für die Industrie)

Prozesse und Projekte

Softwaretesten und Testmanagement

Software Architektur und Sicherheit

Training services (ISTQB, IREB, ISSECO, CAT etc.)

Events & media

Magazine und Veröffentlichungen (z.B. Testing Experience, Agile Record)

Kongresse und Konferenzen (z.B. Agile Testing Days, Testing & Finance)

Wie alles begann – die Situation 2009

Unsere Kunden aus Industrie und Unternehmensberatung standen vor

folgenden Problemen:

Wachsende Zahl von agilen Projekten, kleine Anzahl von Experten

„Klassische“ Tester haben Integrationsprobleme in agilen Teams

Unsere Partner brauchten dringend ein Training speziell für Tester in

agilen Projekten


Wie alles begann – das Problem

Existierende Tester Trainings

Kursinhalt zu theoretisch, kaum Fokus auf praktische Fähigkeiten des

Testers

Prüfung mit Multiple Choice Fragen, kein Nachweis praktischer

Kenntnisse und Fähigkeit zur selbstständigen Problemlösung

Existierende agile Trainings

Kaum Fokus auf die Rolle des Testers im Projekt

Keine unabhängige Prüfung, kein Nachweis erworbener Fähigkeiten

Industrievertreter fragten iSQI, ob Entwicklung einer neuartigen Prüfung

möglich wäre


Wie alles begann – die Idee

Ist das zu schaffen? Wir sind sicher: Ja – das können wir!

Agil + Standards = maximaler Projektnutzen!

Agile Projekte brauchen klare Strukturen, Disziplin, eine gemeinsame

Sprache und Methodik

Ein Team gut ausgebildeter Individuen ist der Schlüssel zum Erfolg

agiler Projekte

Konsens bei täglichen Arbeitsmethoden führen zum Projekterfolg


Wie alles begann – die Zielgruppe

CAT ist genau das Richtige, wenn Sie...

als Tester in agilen Projekten anfangen wollen

bereits als Tester in agilen Projekten arbeiten und die Effektivität der

eigenen Arbeit steigern wollen

sich für Testen in agilen Bereichen interessieren (z. B. als Manager,

SCRUM Master, Entwickler)


Wie alles begann – das Rahmenwerk (2010)

Ziele des Trainingsprogrammes: Das Training…

ist praxisorientiert, Hands-on, mit Workshop-Charakter

basiert auf Teamwork

lässt Teilnehmer agil Arbeiten, statt Frontalunterricht

berücksichtigt individuelle Stärken und Fähigkeiten

Wie kann eine Prüfungs- bzw. Zertifizierungsmöglichkeit aussehen?


Wie alles begann – das Rahmenwerk

Ziele der Zertifizierung: Die Prüfung bewertet…

Soft Skills in Teamarbeit

Wissen über agile Methoden und Begriffe

angewandtes Testwissen in einem agilen Projekt

praktische Fähigkeiten in den Bereichen persönliche

Weiterentwicklung und Umgang mit Kundenfeedback


Wie es weiterging – die starken Partner


Wie es weiterging - Kursdesign

Kursinhalte und -ziele:

Prinzipien der agilen Herangehensweise bei Softwareentwicklung

Differenzierung der Tester Rolle in agilen und nicht-agilen Projekten

Herausforderungen und Schwierigkeiten bei nicht-testspezifischen

Aktivitäten in agilen Teams

Soft Skills des Teammittglieds in agilen Projekten

Kursinhalte über Lernziele definiert

Zentrale Schulungsunterlagen für alle Trainingsanbieter


Wie es weiterging - Prüfungsdesign

Um CAT zu werden, müssen Kandidaten eine dreiteilige Prüfung

bestehen:

Soft Skills Assessment zur Teamfähigkeit

Schriftliche Prüfung – keine Multiple Choice Fragen!

Praktische Prüfung – Nachweis des praktischen Könnens des Testers

Re-Zertifizierung nach 36 Monaten (Interview / Dokumentenreview)


Wie es weiterging - das CAT Training (2011)

Fünf Tage, die das tägliche Arbeiten der einzelnen Teammitglieder in

agilen Projekten wiederspiegeln:

Täglich: Daily Scrum und Soft Skills Assessment

Tag 1: Geschichte und Terminologie: Agiles Manifest, Prinzipien + Methoden

Tag 2: Planung, Anforderungen, Schätzung und Strategie

Tag 3: Entwicklerkontext, Testen und Retrospektiven

Tag 4: Testgetriebene Entw., Testautomatisierung, nicht-funktionale Tests

Tag 5: Praktische Beurteilung und schriftliche Prüfung


Eindrücke aus dem Trainingskurs…

[email protected]

[email protected]

Certified Agile Tester

Version 1.0.4

Course extractsWerner Lieblang

Introduction

Copyright © 2010 iSQI GmbH – SIG “Agile Testing”

Let‟s start being agile

• Time boxed Introductions – 1 minute

• Write a user story to describe what you want to achieve

from the workshop

Structure of a User Story

As a [person in a role]

I want to [perform some activity]

So that [some goal is achieved].

http://tynerblain.com/blog/2009/02/02/user-stories-and-use-cases/


My user story for this tutorial

• As the instructor I want to provide the course attendees with the

knowledge and skills to become certified Agile testers so that they

can return to their work environment confident that they can

contribute value to the team


Daily Scrum Meeting

• Held every day during Sprint

• Same location and time

• Team members report to each other and not the Scrum Master

• Opportunity for the team members to synchronise their work

• Answer 3 questions during meeting

• Maximum 15 mins in length


Our Daily Scrum Meeting

1. What did you do to prepare for this course?

2. What do you expect to do today?

3. What is preventing you from making the best use

of your time?


Assessment

Practical

Assessment

Written

Assessment

Soft Skills

Assessment

throughout

the course

+ +

Total assessment will be broken down:

10% 30% 60%

Models and Principles


Agile Manifesto

We are uncovering better ways of developing

software by doing it and helping others to do it.

Through this work we have come to value:

That is, while there is value in the items on the right,

we value the items on the left more.

Individuals and interactions

Working Software

Customer collaboration

Responding to change

Processes and tools

Comprehensive documentation

Contract negotiation

Following a plan

over


Agile is not!

An Agile Method is Not:

1. Compressing the project schedule

2. Removing all existing software development processes

3. Throwing out all documentation

4. Writing code up to the last minute

5. An excuse for doing anything


The most common agile methods

• Scrum (Ken Schwaber, Jeff Sutherland, Mark Beedle)

• Extreme Programming (XP) (Kent Beck, Eric Gamma, & others)

• Lean Software Development (Mary & Tom Poppendieck)

• Kanban (David Anderson)

• Dynamic System Development Method (DSDM) (Dane Faulkner and

others)

• Adaptive Software Development (Jim Highsmith)

• Crystal Methods (Alistair Cockburn)

• Feature Driven Development (Peter Coad & Jeff Deluca)

• Agile Unified Process (Scott Ambler)

Agile Process


Moving from traditional to agile

Process Waterfall

Development

Iterative &

Incremental

Agile

Development

Measure of

Success

Management

Culture

Requirements

& Design

Coding &

Implementation

Test & Quality

Assurance

Planning &

Scheduling

Conformance

to plan

Response to change,

working code

Command &

control

Leadership collaborative,

empowerment of teams

Big & upfront requirements &

design documentation

Continuous / emergent /

just in time elaboration

Code all features in parallel.

Test code later

Code & unit test,

deliver serially

Big, planned / test late Continuous & concurrent

testing starting early

PERT / detailed / fix scope,

estimate time & resources

Two-level plan / fix date,

estimate scope

Scalin

g S

oftw

are

Agility

: Best P

ractic

es fo

r larg

e O

rganis

atio

ns –

DeanLeffin

gw

ell 2

007


The Core Agile Process

Story

Constraint

Defect

Elaborate and Design the

solution (define it)

Evaluate it meets

acceptance tests

(test it)

Fa

il a

cce

pta

nce

tests C

od

e s

tory

(bu

ild it)

Story

Constraint

Story

Product

Backlog

Pass Acceptance Tests

Pull Story from backlog


The Scrum Process

Daily 15 Minute Scrum Meeting to Discuss progress

Product Backlog

Selected Features For Sprint

Tasks required to complete the selected Features

Every 24 Hours

Every 30 Days

New functionality demonstrated at the end of

each sprint

Sprint Planning Meeting

Release Planning Meeting

Sprint Review

Daily Scrum

Retrospective


Adapt the „ideal‟ Scrum Process

• Read the scenario in the manual

• Discuss the constraints

• Make suggestions for adapting the “ideal” process

• Present your ideas


Discussion

• Why do we need Automation on an Agile project?


Test Automation

• Continuous Integration and Environment readiness

• Longer term reduction in the cost of testing

• Accelerate time to market

• Reduce cost of quality

• Consistency

• Coverage

• Reduce cost of testing

• Increased confidence

• Job satisfaction

• Testability


Discussion

• So how do we determine what needs to be automated?

Summary


Final Testing Practical

• This is where you consolidate all your learning and experience

• Final Preparation for the Assessment

• Trainer to walkthrough the principles of the practical and the

guidelines

• Please take notes of learnings on the page provided in your manual


Sprint Planning – Sprint 7

• Walkthrough the user stories for Sprint 7

• Adding Multiple Items

• Removing Individual Items

• Review Order

• Design specifications for each user story

• Test

• Sprint Review meeting

• Retrospective within the Teams

• Defects Discussion


Summary

• Introduction

• Models and Principles

• Agile Process

• Iteration 0 and Estimation

• Planning

• Iteration

• Story Testing

• Tools and Debt

• Agile Teams


Release Planning ….

Ti

me

Iteration 1, 2, 3 ...


Daily 1

Daily 2

Daily ...

Review

Retrospective

Iteration 0

Summary – Agile Testing Process

Release Planning Meeting(Estimation Meeting)





Release Planning ….

• Introduction to the Product Owner's

(PO) User Stories and business

Product backlog

Review

Business Value

Support the PO in formulate fitting

Acceptance Criterias

Estimate the Story Points

Planning poker

Put it on the time line (Release Plan),

package it

Release Themes

Feature

User Stories

Summary – Release Planning Meeting



Iteration 0


Daily 1

Daily 2

Daily ...

Review

Retrospective

• Become familiar with the SUT &

related artefacts

• Prepare for required skills (tech.,

process)

Technical excellence

Design to testability

Determine the process

Design your taskboard

Define definition of done

Defect handling process

Elect your Scrum Master

Necessary documents (beside

Scrum-related docs)

Determine Test specifics

Strategy, process, tools,

infrastructure,

Coverage (test end criteria)

Summary – Iteration Zero



Iteration 0


Daily 1

Daily 2

Daily ...

Review

Retrospective

• Review user stories (including

acceptance criterias!)

Derive design / (Re-)Estimation

Negotiations regarding the planned

sprints (priority)

Derive test tasks

Test driven development (TDD)

Spikes

Balanced test automation

Select the product backlog Items

(Selected backlog)

Velocity

Feedback to the PO

Influences the release plan

Committed!

Rolling wave adaption of the

Release Plan

Summary – Sprint Planning Meeting



Iteration 0


Daily 1

Daily 2

Daily ...

Review

Retrospective

• Daily scrum

3 answers

move your task

adapt your sprint burn down chart

Continuous build / integration

Ask developers for a new tag

Smoke test / check list

Test activities

check acceptance test criterias

do explorative testing (session

sheets)

business value

adapt your auto tests

maintain the integration suite

Summary – A working day in a sprint


• Demonstration to the PO

• Follow the acceptance

criterias

• Show the (most severe)

known bugs in context of the

business value

• → build trust


Iteration 0


Daily 1

Daily 2

Daily ...

Review

Retrospective

Summary - Review



Iteration 0


Daily 1

Daily 2

Daily ...

Review

Retrospective

• Inspect and Adapt

Test Strategy

Criterias: Definition of done

Roles

Impediments

Adapt the known velocity

→ Define actions

Summary - Retrospective

Impressions


Impressions – practical exercise


Impressions – a task board


Impressions – time table for a sprint


Impressions – mind maps


Impressions – before the exam


Impressions – after the exam

Danke! Fragen?

[email protected]

[email protected]


Course Outline

Introduction

Daily SCRUM

Problems with

Traditional

Agile Manifesto

& Principles

Agile Methods

Agile Process

Option

Roles

Intro to Agile

Exercise

Sample

Questions

Day 1

Agile Methods

and Process

Requirements &

Specifications

Iteration 0

Release

Planning

Task Board

Test Strategy

Estimation

Iteration

Planning

Burndown

Charts

Sprint Practice

Exercises

Continuous

Integration

Version

Management

Pairing

Acceptance

Criteria

Regression

Testing

Defect

Management

Testing

Exercises

Sample

Questions

Test Automation

Non Functional

Testing

Debt Technical

& Testing

TDD

Teams

Agile For Large

Projects

Summary

Testing Exercises

Sample

Questions

Practical

Assessment

Written Exam

Revision

Written

Examination

Day 2

Planning

Day 3

Testing

Day 4

Teams

Day 5

Assessment

Sample

Questions

meet the cat! · cat –certified agile tester isqi als zertifizierungsstelle firmensitz: potsdam...

Documents