Useful book for those QA specialists who face the Agile transition but have no clue from where to start.
Each section starts with the concise schema that gives good structural idea about what is going to be discussed in the section and also can be used later on as reference to remind main points. Throughout the whole book the authors give suggestions what practices turned to be success in their own team but always remind that what worked out for one company and team not surely will work for another – so everyone should try and see what suits the best for their team purposes.
I personally find there also the Manifesto for Agile Software Development:
We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is? While there is value in the items on the right, we value the items on the lift more.
Another interesting thing that is described in this book are the Agile Testing Quadrants. Each of four quadrants is in details explained throughout the book.
The main points that I took from the book: members from Agile team are multifunctional- all are doing mutual, interchangable staff regarding QA-ing; communication is th ekey element of Agile process: no communication - no agile; automation supports the agile effort - without it tasks will be delayed and even impossible to complete; invest in time for knowladge gaining and learning of new technologies and tools - to be an agile team you should use ad hoc; spend time on process improvement and do not be stack with manual work
I liked this book as I have found quite a lot of useful and new information for myself.
