Agile Testing Manifesto

In juli 2015 is er door (o.a.)  een Testing Manifesto gemaakt:Agile Testing Manifesto

(bron: Growing Agile)

Later is er door  ook een versie gemaakt:

We are discovering better ways of creating value for our customers and for our organizations through new testing approaches.

Through this work we have come to value:

Testing Driven Development

Over

Development Driven Testing

Thoughtful Testing

Over

Scripted Testing

Business Driven Testing

Over

Requirement Based Testing

Delivering voice of customer

Over

Being a critique

Highlighting Risk

Over

Acting as gatekeepers

Testing Understanding

Over

Checking Functionality

Good Enough

Over

Total Conformance

Preventing Defects

Over

Detecting Defects

Delivering Value

Over

Criticizing The Product

Testing With Others

Over

Testing Alone

Improving Our Craft

Over

Following Standard Practices

Timely Reporting Of Progress

Over

Weekly Reporting Of Progress

Reporting When Needed

Over

Reporting When Told

Listening To People

Over

Analysing Quality Metrics

Testing Throughout

Over

Testing At The End

Collaborative Elaboration

Over

Speedy Automation

(bron: Agile Testing Alliance)

Onlangs een aardige plaat gevonden over de situationele context van het gebruik van Scrum (bron: blog.crossbolt.com).

When to use Scrum

When to use Scrum

Dit is een afgeleide van The Stacey Graph van Ralph Douglas Stacey

Stacey Graph

Stacey Graph, uit: Strategic management and organisational dynamics: the challenge of complexity. 3rd ed. Harlow: Prentice Hall, 2002. University of Hertfordshire,