What does it take to do SmartQA? Smart Thinking, Smart Understanding, Smart Design, Smart Plan, SmartQA Test Organisation and Smart Planning. A pictorial article on this is what this week’s beEnriched article “7 Pictures to Doing SmartQA” is.

In this week’s SmartBites “Lean thinking & Agility“, Tathagat Varma outlines how Agile inspired by lean thinking is accomplishing agility in SW development.

Isn’t it amazing that earth just goes about the job quietly, of revolving around the sun a whopping distance of 940 million kms every year? A joy it is to pause and ponder the amazing cosmic wonder, and celebrate as it commences another revolution around the sun. On this happy occasion of a new beginning, enjoy the poem that I wrote titled “Bless us all”.

What does it take to do SmartQA? Thoughtful pause, multidimensional thinking, sensitivity and awareness and designing for robustness/testability. A short crisp article continuing from the prior article outlining five more thoughts on what it takes to do SmartQA. Doing SmartQA is about visualising the act in one’s mind and taking steps to being robust and enabling rapid easy validation, outlined in this crisp article FIVE *more* thoughts on ‘Doing SmartQA’ in the expandMind section.

In this edition of SmartBites, listen to two great pieces of advice from Vivek and Shivaji on ‘reinvent yourself’ and ‘staying in sync’ in today’s rapid dev as “Smart Advice #2“. In the nanoLearning section Jawahar Sabapathy helps us understand containerisation & microservices and its role in today’s architecture.

What does it take to do SmartQA? Thoughtful pause, multidimensional thinking, sensitivity and awareness and designing for robustness/testability. A short crisp article continuing from the prior article outlining five more thoughts on what it takes to do SmartQA. Doing SmartQA is about visualising the act in one’s mind and taking steps to being robust and enabling rapid easy validation, outlined in this crisp article FIVE *more* thoughts on ‘Doing SmartQA’ in the expandMind section.

In this edition of SmartBites, listen to two great pieces of advice from Vivek and Shivaji on ‘reinvent yourself’ and ‘staying in sync’ in today’s rapid dev as “Smart Advice #2“. In the nanoLearning section Jawahar Sabapathy helps us understand containerisation & microservices and its role in today’s architecture.

What does it take to do SmartQA? How can I do less and accomplish more? What parts of this are human-powered & machine-assisted? It takes a brilliant mindset, intelligent exploration, diligent evaluation, keen observational skills, tech savviness and continual adjustment. It is about being logical yet be creative, it is about being disciplined yet be random, it is about exploring the breadth and depth, it is about understanding deeply and also finding blind spots about being bundled by time but be unlimited/unbounded with the possibilities. Doing SmartQA is about doing mindfully, in a state of brilliant balance, outlined in this crisp article five thoughts on ‘Doing SmartQA’ in the expandMind section.

In this edition of SmartBites, listen to Zulfikar Deen on “Expectations of end users & management from IT team”. In the nanoLearning section Shivaji Raju outlines four key aspects of “What is Digital Testing”.

“A typical accident takes seven consecutive errors” states Malcolm Gladwell, this notion is reflected in Mark Buchanan’s book “Ubiquity”too. The article in the beEnriched section “Seven consecutive errors = A Catastrophe” dwells upon ‘How do you ensure that potential critical failures lurking in systems that have matured can still be uncovered?’

Unilever had a problem. They were manufacturing washing powder at their factory near Liverpool in the northwest of England in the same usual way – forcing boiling hot chemicals through a nozzle at super high levels of pressure. The problem was that the nozzles didn’t work smoothly, they kept clogging up. A crack team of mathematicians, dug deep into problems of phase transition, derived complex equations and after a long time came up with a new design. But it was inefficient. Then the company turned to its biologists, who had no clue of phase transition or fluid dynamics, but they solved it!

 The biologists took tens copies of nozzle, applied small changes in each and subjected them to failure by testing them. After 449 failures they succeeded. Progress had been delivered not through a beautifully constructed master plan but by rapid interaction with the world. A single outstanding nozzle was discovered as a consequence of testing and discarding 449 failures. Check out the book “Black box thinking” in the expandMind section.

“A typical accident takes seven consecutive errors” states Malcolm Gladwell, this notion is reflected in Mark Buchanan’s book “Ubiquity”too. The article in the beEnriched section “Seven consecutive errors = A Catastrophe” dwells upon ‘How do you ensure that potential critical failures lurking in systems that have matured can still be uncovered?’

In this edition of SmartBites, listen to “A mosaic of testing” from NINE practitioners around the world on failures, tools, unit test, clean code, Agile, TDD, feeling & relationship.

In the nanoLearning section Raja Nagendra Kumar outlines the role of refactoring, unit testing in producing clean code. He states this very interestingly as “Technical debt is fat, clean code is liposuction” and crisply explains the act of producing clean code.