The agile way, we work II (2 min read)

In last backlog grooming ceremony, our team re-assessed the priorities of items in the product backlog with product owner.

Team discovered and decided to change the priority of a story (“implementing an API to fetch unique products from past orders”) from middle of the backlog to top due to some dependencies.

As the tester in the team, I had to test this API which will be developed in this sprint.

Drew this decision table on developer’s table while having a quick chat with relevant developer. Identified areas to be tested within 7-10 minutes through this.

Took a clear photo of the decision table and attached it to relevant story in JIRA.

Now, developer and myself are in the same page. Also, developer is already aware of these test cases I am going to design in order to test this new API.

Plus, developer can use the attached decision table in JIRA to perform “developer testing” to prevent defects in test environment.

As the tester, I have designed around 20 test cases (by looking the attached decision table in JIRA) while developer implement the new API.

Once developer completed the API implementation, I have already automated test cases as well and those are running less than 1 minute.

What we have achieved?

• We have clarified the requirement initially. Therefore, it helps to prevent conflicts while developing or testing.
• Strong DEV-QA collaboration to achieve same objectives to deliver a quality product.
• Promoted defects prevention activities instead of finding defects in test environment.
• We have prioritized a working service (API) over comprehensive documentations (since we have not spent hours to create decision table documents using an application like MS Office)
• Since we have managed to automate all tests within the sprint, so that we can get early and frequent feedback on the quality of this service (API) in future.

The agile way, we work I

Husny Jiffry (CSM)

Senior Quality Engineer - Sysco LABS