Linchpin Labs

Before we get into the topic ‘the purpose of QA’, we would like to admit that there are countless articles and books are been published to demystify the role of quality folks in every project and in every department of the organization. However, this is an attempt from our perspectives to find the answer and emphasis our propositions on what could be the role that a QA team must play in the organization. The Mantra! ‘ Practice the Prescriptive’ is the motto or mantra of QA facilitators. Many a times, there exist difference of opinions and altercations between the customer facing folks and QA folks are due to non-compliance to processes or standards. In most cases, project teams would focus only on fulfilling the customer requirements and expectations by skipping the processes and would not consider the quality of deliverable. In order to ensure a high quality and on time delivery of the product, project teams must be adopting ‘ Ambidexterity ’.    Let us iden...

1.    ‘Analytics’ On Artificial Intelligence 2.    Brimming’ Big Data’ & ‘Balanced Scorecard’ 3.    Crunching ‘Capability Maturity Model’ & Co-Creation 4.    Dreadful ‘Draconian’ Measures 5.    Eccentric ‘Execution’ 6.    Flabbergasted 'Future Of Work' 7.    Grudging ‘Ground Rules’ 8.    Hunting & Haunting ‘Histogram’ 9.    Informal ‘Innovations’ 10. Jettisoned Jargons Of ‘Jboss’ 11. Kama on ‘Kano Model’ & ‘Kansei Engineering’ 12. Love ‘Lean’ 13. Mesmerizing ‘Management’ Metaphors 14. Nagging & Nudging ‘New Initiatives’  And ‘Non-Linear’ Models 15. ‘Organic’ Organizations And ‘Operations’ 16. Plasmic ‘Protocols’ 17. Quenching ‘Quality’ 18. Rapid ‘Revenue Recognit...

It was the year 1970’s, the nascent stages of IT revolution across the globe and especially in India. The mainframe monopoly had just ended and broken with robust online transaction processing available on super mini computers running multi-executive kind of operation system. The PC revolution had just begun with word processors and spread sheets available on inexpensive computers. Therefore, it was known to the world, the demand for software applications would explode and there would be opportunities for companies specializing in customized software development from a country like India. Then in 1999, the “Y2K” fear gripped the U.S. Y2K refers to the year 2000, and the concern was that much of the existing software stores information on year using only two digits; 97 instead of 1997. The fear was that when a program advanced from December 31, 1999 to January 1, 2000, it would behave as if the year was actually 1900, potentially disrupting a huge amount of business and scientific ...