From monday to wednesday I had the chance to visit the Agile Testing Days in Potsdam. It was an awesome event: I met a lot of interesting people (delegates, speakers & tutors), had many interesting conversations, met former colleagues, listened to amazing talks, and learned a lot. Far too much to wrap everything up in one blog posting. Therefor I will use this article to list up all the articles about the Agile Testing Days 2011 (#agileTD), the list will be updated as a add articles, so drop in from while to while, or subscribe to the RSS-feed:
- Agile Testing and Test Management, Johanna Rothmann
- What Testers and Developers Can Learn From Each Other, David Evans
- Do agile teams have wider awareness fields?, Rob Lambert
- Who do You Trust? Beware of Your Brain, Linda Rising
- Product Management using Effect Mapping, Gojko Adzic
- Appendix A: Lessons Learned since Agile Testing Was Published, Lisa Crispin & Janet Gregory
- A Balanced Test Strategy Strengthens the Team, Anko Tijman
- Testing your Organization, Andreas Schliep
- Five key challenges for agile testers tomorrow, Gojko Adzic
One thing I also do as a teetsr is to help the team control scope. Most newbie agile teams over-commit, and they work on stories that are too big. Find ways to divide the work into small chunks or threads. Make sure testing estimates are included in story estimates. Sometimes features take longer to test than to code! When you see a story that looks too big, ask if it can be divided up. Sometimes the smaller piece may not deliver much business value, but the team needs to focus on getting one small story done at a time, including all the testing activities.