As the VP of Client Service for Zephyr, Sanjay brings over 15 years of leadership experience in IT and Technical Support Services. Throughout his career, Sanjay has successfully established and grown premier IT and Support Services teams across multiple geographies for both large and small companies. Most recently, he was Associate Vice President at Patni Computers responsible for the Telecoms IT Managed Services Practice where he established IT Operations teams supporting Virgin Mobile, ESPN Mobile, Disney Mobile and Carphone Warehouse.
Hardware and software have become a necessary part of virtually every company and household, and the vendors that serve these audiences must ensure that their products work as they should. Sanjay Zalavadia looks at the difference between software testing and hardware testing.
Agile software development is a complex initiative to undertake, especially when a dispersed team is involved. Organizations must establish a unified agile methodology to ensure that everyone is on the same page and understands what is expected of them in these efforts.
For test teams, throwing every test case in the book at a project isn't practical or necessary. By understanding test design techniques and what to look for in a good test case, teams can choose the ones right for their requirements and improve their testing efficiency.
Many software professionals think they won't get anything out of retrospective meetings and want to cut them out entirely. However, retrospective meetings are a necessary part of project progression, and they can significantly improve your team's software quality efforts.
To be truly effective, QA teams have to choose the right agile testing tools for their needs and ensure that it has the required features to ensure quality and bolster testing efforts. Sanjay Zalavadia outlines a few things to consider as you search for the best solution for your QA team.
Although there's a lot of practice evolution that happens with agile transitions, legacy code can still be a major obstacle to agile success. A few risks and considerations emerge when scaling agile while still managing legacy code barriers.
With agile software development, users are involved from the very beginning and are provided a minimum viable product to critique. A QA tool can be used to gather and organize user feedback while planning the next move. Sanjay Zalavadia highlights the benefits of collecting feedback early.