Topics In Demand
Notification
New

No notification found.

Are we paying attention to every SDLC phase to avoid unnecessary pressure on Teams towards the end?
Are we paying attention to every SDLC phase to avoid unnecessary pressure on Teams towards the end?

387

0

In this world of digital transformation, there is a strong competition to deliver fast and rich customer experience but in this entire process of delivery there is a lot of pressure being built up on teams to deliver fast with Quality.

So we need to pay high attention to planning of every single phase whether it is creating a SOW, providing high level estimates, extent of best practices being involved, Governance etc. to ensure that we are building in Quality and not leaving it for the end. Also, to ensure we do not end up building pressure on teams executing the project on the ground, we have to measure every phase diligently as even a single variable can lead to deviation of the entire roadmap.

For specifically Quality Assurance teams, QA Estimates should be done by taking into account all the attributes that can impact execution

  • What kind of Team structure you should/would have – Dev to QA ratio
  • What Team combination - novice, intermediate and expert members
  • Would you be using Open source or Licensed tools
  • What Testing Types you would cover for “In Sprint Testing” – Functional or Non Functional
  • Maturity of Framework w.r.t time
  • % of “In Sprint Automation” to be delivered – UI/API/Mobile etc.
  • Best Practices if any – Regression on every build which invokes maintenance and analysis, Rollback on deployment
  • Governance

Further, once the execution starts, we should identify areas of optimization in regular intervals and should create points for Short term and Long term improvement plan as everything cannot be optimized at once in fast pace deliveries. 

High level areas pointing to the need of quick action plan can be

  • Major requirement gaps being identified inside the Sprints even after grooming calls
  • Unit testing coverage with no relation to quality of code
  • Time consumption in locating web elements
  • Very less or No re-usability of code even after 10 Sprints
  • Regression failures – Scripts/functionalities/environment etc.
  • High Rework Effort – pointing to design issues, functional issues, optimization, no re-usability in design
  • Same RCA and action being identified for defects

Plan in the initial stages for Quality Assurance Engineers

  • Create Competency framework, assess, provide feedback and train in the required area
  • Create Estimation frameworks to help team in avoiding underestimation or overestimation
  • Align right skill at right position
  • Keep 1-2 shadow members for Risk Mitigation (Depending upon the size of your team)
  • Use tools like SelectorsHub and test case studio to save effort in Automation if needed. SelectorsHub and TestCase Studio (https://selectorshub.com/) combination is to generate not just Xpath but entire line of code and English language bases test cases.
  • Tools like Mabl, Testim.io, TestModeller.io etc. can be used
  • Test Execution Analytics to find the areas of improvement. Tools like ReportPortal.io or Azure DevOps Analytics can be used.
  • Unlearn old ways and Learn new/optimized ways of working is THE KEY TO SUCCESS

That the contents of third-party articles/blogs published here on the website, and the interpretation of all information in the article/blogs such as data, maps, numbers, opinions etc. displayed in the article/blogs and views or the opinions expressed within the content are solely of the author's; and do not reflect the opinions and beliefs of NASSCOM or its affiliates in any manner. NASSCOM does not take any liability w.r.t. content in any manner and will not be liable in any manner whatsoever for any kind of liability arising out of any act, error or omission. The contents of third-party article/blogs published, are provided solely as convenience; and the presence of these articles/blogs should not, under any circumstances, be considered as an endorsement of the contents by NASSCOM in any manner; and if you chose to access these articles/blogs , you do so at your own risk.


© Copyright nasscom. All Rights Reserved.