More Agile Testing: learning journeys for the whole team
This book speaks culture and how agile testing makes sense in large and middle size organizations.
Its definitely speaks about diversity and communication between different types of groups which most times are involved in software projects.
Authors discuss how to learn new methodology and technology and even describe methodology of creating test plans which include ATDD, BDD, TDD methods.
I totally agree that behind quality and automated testing should exist strong support from all evolved party’s: management, developers and other business related departments of the company which involved into the software project.
I totally agree that behind quality and automated testing should exist strong support from all evolved party’s: management, developers and other business related departments of the company which involved into the software project.
There is no silver bullet of solving bad software design and the authors of this book speak about that problem too, sometimes the organization of the teams must be changed in order to reached the promised qualities of agile development. Suggestion about creative developing of the testplan’s is very good and usable!
Authors of this book recommend to find a way to record user interaction with software , because in some more complex situation actual user behavior in relation to software decide whether project was developed as expected or the developers just ignored the user requirements and concentrated more on functional requirements , there should be balance.
This book discusses the Kanban too, which give pretty objective view with lots and lots of examples of the Kanban workflow.
Summary: After reading this book my views about software quality in enterprise software development were confirmed, but this book more about organizing teams it’s not about software development or testing, yes it discuss challenges in software development , but the main theme is how to organize teams so that they know what and how to test the software which they creating.
I can recommend this book to scrum masters, products owners, project managers.
The developers would feel bored during the reading of this book.