Tech Talks With Greg Goldshteyn

From the introduction of most basic websites to the use of generative AI and machine learning technologies, the tech landscape has gone through a dynamic shift. With more and more users being associated to the digital concept, the need for creating more intuitive yet humanized experiences have grown.  

Though developers and business analysts across the globe constantly work to yield sustainable innovation, creating the ultimate user experience and meeting performance benchmarks require immediate access to quality assurance solutions.  

Since embracing the concept of quality with the rapid innovation need people from software testing backgrounds to actively communicate and exchange perspectives, this time, our in-house expert, Vivek Rana, QA Lead, BugRaptors interacted with Greg Goldshteyn, Manager Quality Assurance, Fox Networks Group.  

With over 25 years of experience in the industry, Greg carries hands-on experience building automation frameworks, both SaaS-based or on-premises for large-scale enterprise applications. More importantly, Greg holds a great grip on test planning and managing complex software projects with intuitive QA team handling.  

Moreover, his knowledge set includes the latest QA methodologies and techniques, Lean & Agile development (XP, SCRUM, KANBAN), knowledge of Rational Unified Process®, Six Sigma, CMMI. Over the years, he is constantly working on guiding offshore and in-house QA teams on test projects that involved API, SaaS, Mobile (Android, iOS), etc.  

Also, his expertise expands across diverse industry verticals namely Mortgage, Banking, Financial, B2B/C2B, CRM (Salesforce.com/ SFDC), Security, eCommerce, Communication, EDA, social media, Streaming Media and Embedded Software applications. 

With all those insights into Greg’s career, let us quickly jump to the interview to explore Greg’s perspective on changing QA practices, agile success, workload management, and more.  

Vivek: According to you, what is the secret weapon for project success? 
Greg: In my opinion, the secret weapon for project success in quality assurance is a comprehensive and well-planned testing strategy. 
 
A good testing strategy involves identifying the goals and objectives of the project, defining the scope of testing, and creating a detailed test plan that outlines the specific tests that need to be performed, the testing environment, the testing schedule, and the responsibilities of each member of the testing team. 
 
To ensure project success, it's also important to have a skilled and experienced testing team that can execute the testing strategy effectively, identify and report defects in a timely manner, and work closely with the development team to resolve any issues that arise. 
 
Additionally, using the right testing tools and technologies can also be a valuable asset in achieving project success in quality assurance. These tools can help to streamline the testing process, improve testing efficiency, and provide valuable insights into the overall quality of the project. 
 
Overall, a strong testing strategy, skilled testing team, and effective testing tools are all key components of a successful quality assurance project. In my opinion, the secret weapon for project success in quality assurance is a comprehensive and well-planned testing strategy. 

Vivek: What do you think about changing QA practices? 
Greg: I believe that changing quality assurance practices is important in order to keep up with the evolving needs and demands of the industry, as well as to stay ahead of the competition. The world is constantly changing, and technology is advancing rapidly, which means that quality assurance practices must also evolve to keep up with these changes. 
 
One example of this is the shift towards more agile and DevOps-oriented approaches to software development. This has resulted in a greater emphasis on continuous testing and automation, and a move away from traditional, manual testing methods. 
 
Another important trend in quality assurance is the increasing use of artificial intelligence (AI) and machine learning (ML) technologies to automate testing processes and improve the accuracy and efficiency of defect detection. 
 
However, it's important to note that any changes to quality assurance practices should be carefully planned and implemented to ensure that they are effective and don't disrupt the project or negatively impact product quality. It's also important to involve all stakeholders, including developers, testers, and management, in the decision-making process and to provide adequate training and support to ensure that everyone is on board with the new practices.  

Vivek: According to you, what are the key metrics that are most effective in an agile environment? 
Greg: In an agile environment, the key metrics that are most effective in measuring project progress and success include: 

• Velocity: Velocity is the measure of the amount of work completed by the agile team during a sprint. It is a useful metric for tracking progress and predicting how much work the team can complete in future sprints. 
• Lead Time: Lead time is the time it takes for a feature or user story to go from concept to production. Measuring lead time can help identify bottlenecks and areas for improvement in the development process. 
• Cycle Time: Cycle time is the time it takes to complete a single unit of work, such as a user story or feature. Measuring cycle time can help identify opportunities for process improvement and increase efficiency. 
• Sprint Burndown: The sprint burndown chart shows how much work is left to be completed in a sprint and how much time is left to complete it. It provides a visual representation of progress and helps the team to stay on track to meet their sprint goals. 
• Defect Density: Defect density is the number of defects found in a specific amount of code. Measuring defect density can help identify areas of the code that need improvement and help the team to improve the overall quality of the product.
• Customer Satisfaction: Customer satisfaction is a key metric for measuring the success of an agile project. It is important to gather feedback from customers regularly and use this feedback to make improvements to the product and the development process. 

Overall, these metrics can provide valuable insights into the progress and success of an agile project, and can help the team to identify areas for improvement and make data-driven decisions to optimize the development process.  

Vivek: What kind of techniques do you use to manage your workload? 

Greg: 

• Prioritization: Prioritize your tasks based on their importance and urgency. Identify the critical tasks that need to be completed first and focus on them. 
• Time management: Time management techniques such as setting goals, creating schedules, and delegating tasks can help you to use your time more efficiently and effectively. 
• Communication: Effective communication with stakeholders such as the development team, project managers, and other departments can help to manage expectations and ensure that everyone is on the same page regarding project goals and timelines.  
• Automation: Automating repetitive tasks such as test execution and reporting can help you to save time and focus on more strategic tasks. 
• Continuous learning: Keeping up with industry trends, new technologies, and continuously learning new skills can help you to work more efficiently and effectively, and manage your workload more successfully. 
• Agile methodologies: Adopting Agile methodologies can help you to manage your workload more efficiently by breaking down tasks into smaller, more manageable chunks and working in sprints. 
• Team collaboration: Encouraging collaboration and communication within the QA team can help to share workload and ensure that tasks are being completed efficiently.  

Vivek: If you were sitting next to a leading expert in your field, what would you ask them? 
Greg: If I were sitting next to a leading expert in the Quality Assurance field, I would ask them: 

• What are the emerging trends and technologies in the Quality Assurance field, and how do you see them shaping the future of software testing? 
• What are some of the biggest challenges you have faced in your career as a QA expert, and how did you overcome them? 
• How do you ensure that your team stays motivated and engaged in their work, and what are some effective team management strategies you have used? 
• How do you approach test automation, and what are some best practices for implementing automation in a testing project? 
• How do you balance the need for speed and agility in software development with the need for thorough testing and quality assurance? 
• How do you measure the success of a QA program, and what are some key performance indicators you use to track progress and ensure continuous improvement? 
• How do you ensure that your testing processes align with industry standards and compliance regulations, and what steps do you take to maintain quality and compliance in your testing efforts? 
• How can you apply the latest trends in the industry towards improving efficiencies in QA   

Vivek: Do you have any books to recommend?  
Greg: Yes, there are several latest books that I would recommend for quality assurance: 
 
"Agile Testing: A Practical Guide for Testers and Agile Teams" by Lisa Crispin and Janet Gregory - This book provides practical guidance and real-world examples of how to incorporate testing into an Agile development environment. 
 
"The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations" by Gene Kim, Jez Humble, Patrick Debois, and John Willis - This book covers the principles and practices of DevOps, including how to integrate quality assurance into the DevOps process. 
 
"Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation" by Jez Humble and David Farley - This book provides guidance on how to build a continuous delivery pipeline that incorporates automated testing and quality assurance. 
 
"Quality Code: Software Testing Principles, Practices, and Patterns" by Stephen Vance - This book provides a comprehensive overview of software testing principles, practices, and patterns, including how to incorporate testing into the software development lifecycle. 
 
"How Google Tests Software" by James A. Whittaker, Jason Arbon, and Jeff Carollo - This book provides an inside look at how Google approaches testing and quality assurance, including their use of automation, tools, and best practices.  

Vivek: What's the best way to find and contact you going forward?  
Greg: LinkedIn: https://www.linkedin.com/in/gregorygoldshteyn 
Email: goldshteyng@hotmail.com 

When it comes to digital success, quality assurance works as a path to advanced development with integrated access to the essentials of sustainable development like Agile, DevOps, Automation, and more.  

From bringing together the community to practicing the most accurate testing techniques, we at BugRaptors never miss out on anything that is vital to generate value to the world. 

For more such interesting updates on quality assurance, stay connected with us by subscribing to our blog.   

In case, you need any expert advice, suggestions, or professional testing assistance, feel free to drop your queries at info@bugraptors.com