In September 2017 the Ministry of Testing had a crowd-based knowledge sharing event called “30 Days of Agile Testing” with a small learning activity for each day of the month. As with the similar security event I set up a weekly schedule at work to meet for an time-boxed hour and discuss 3-5 selected topics each time.
Our score was 17 topics discussed – some more discussed than actually tried out. Hence the half marks on the poster on the window below. Me and my coworkers work on many different teams – so to dig into specific team tools and processes was out of scope.
Here is a few of our findings:
- Day 3 – YouTube is full of videos on agile, but our Chinese colleague cannot view them. They can though view videos locally on the Dojo and TestHuddle.
- Day 4 – We discussed the Agile Manifesto in relation to GxP/regulated projects. GxP and agile can work together, when you control your deliveries with for instance ATDD. See DevOpsDays Seattle 2017: Continuous Delivery Sounds Great But … and How to build agility into a regulated project?
- Day 12/26 – We need the test cases in many contexts, but do we need the Test Plan specifically. Perhaps we can reduce the test plan to “Requirements/scope”, “test cases” and “staffing” as in Plutora Test.
- Day 13: Perhaps not an IDE, but then learn some other technical tools that is not automation: See 30 Days Of Agile Testing! Day Thirteen and 6 Technical Testing Skills that Aren’t Automation
- Day 18 – Put the testers and test management tasks on the sprint board. Adjust the burn down for part time people. Keep all testers and other people in the project in the loop.
Links to “the Club” on some of the topics we selected:
- 30 Days of Agile Testing, Day 1: Agile testing books
- 30 Days of Agile testing, Day 2: Mindmap of what agile testing is
- 30 Days of Testing – Day 3 Videos
- 30 Days of Agile testing, Day 4: The agile manifesto
- 30 Days of Agile testing, Day 8: Talk to a developer, rather than creating a ticket
- 30 Days of Agile testing, Day 12: Test documentation
- 30 days of Agile Testing, Day 26: What does your Test Plan look like?
Complexity is a Matter of Perspective 