While I've been in the software QA field for over 23 years, at the age of 54, I'm always looking to learn new things. Kudos!

Thank you :)

Thank you

you're welcome. Thanks for watching.

Thanks. Glad you stuck with it and found some value :)

Thanks. I will - I'll try to write up a blog post on monday with the books shown and I'll recomment and let you know when I've done it.

Hi, I have added the list of books to the blog blog.eviltester.com/2017/11/what-is-agile-testing-the-books.html Thanks.

Thanks Alan - keep up with the great work!

You're welcome. Thanks for the prompt.

If it is just for a team then having the team create and outline of their current working practices can be useful early in the process because then in retrospectives the team can compare "did we work the way we said we wanted to work" and if the answer is no then they can evaluate why. Sometimes it will be fine, we were low on time and agreed that we wouldn't do practice X. Sometimes it won't be, we didn't do X and Y happened, we need to remember to do X. Ideally it should come from the team, but if the team are new to Agile then having someone work with them to describe working practices and explain them can help. Making a long detailed document is not really a good idea because no one will read it and it will go out of date quickly. If there are links to "and this is what this practice means..." then it is more of a training or onboarding document than a process description so I'd create two wiki pages (one for onboarding and reference, and one for the working practice). Also depends who the doc is for, is it for the team so they know what they are doing, or is it for stakeholders so they are more confident that the team know what they are doing? The flexibility will also come from team ownership of the outlined process, they can change it as necessary to reflect the way they work. So... creating an outline, that the team own, which is high level, might be useful. Which I think probably aligns with your set of guidelines.

@@EvilTester Many thanks for the detailed reply Alan :-)

Depends on who I am communicating to, and what communication formats are required. Typically no documents. But I document a lot of knowledge and communicate a lot of decisions, via email, wiki, notes on stories, etc.

Thank you for the comment :) I did have some on Amazon but Amazon removed because they didn't sell enough. I do have one design on teemill eviltster.teemill.com/ At somepoint I'll try and add some more designs - if I do, I'll announce it on my blog and newsletter and I'll create a promo video too :)

@@EvilTester Yes we need those "Evil Tester" T-Shirts back online please :) Ordering ASAP. I could only find the "I Test the F..ck out of IT" t-shirts, which are nice , but no match for the "Evil tester" logo....

Glad you like the videos. The logo will not change. This video might help vimeo.com/177222862#t=82

​@@EvilTester Thank you for the video. I can see, we have different points of view. As humans, we have free will. I agree testers should be free and innovative, but not 'evil'. I am also afraid the spiritual world is real and I think it is spiritually dangerous to identify with its dark side. I wish you all the best.