Managing your pipeline for quality assurance

How to create outlook signature

throughout my career as a quality assurance professional i've learned that having a robust qa process in place at the start of a project is key to a successful engagement hi everyone my name is rituja dunakar and i'm a lead qa analyst at working i'll take you through three of the top tips at working pro which can lead to an improved qa process tip number one make the quality of your product a priority people are increasingly expecting great seamless digital experiences when they don't get them it can impact brand loyalty and for our clients can harm the bottom line at working co we believe in building products that are designed in a way which is simple to understand and interact with this is the foundation for why working co has a fully dedicated quality assurance team great products are found through continuous trial and error until arriving at the most successful result tip number two involve qa members in every phase of the project our projects involve qa members as early as the tactics double phase enabling us to have transparent conversations about processes that should be implemented on the project this time is ideal to discuss configuration management for the project by meeting with your team and figuring out basic criteria like types of testing to be performed test plans whether automation is needed browser and device matrix uat releases exit criteria and maintenance here is a list of some of the tools that we use jira for project management test rail for managing tracking and organizing test cases figma is our design platform to build products and slack is a internal team collaboration the next phase is the design piece having qa involved allows the team to identify missing flows and accessibility issues before the next phase begins the development phase involves writing test cases and validating user stories we test the product holistically tracking the functionality of the user stories and making sure all possible scenarios are working as expected and important factor to discuss here is risk management it is our responsibility to collaborate with team members to identify assess prioritize monitor and propose mitigation strategies for these risks and last but not the least is the delivery and support base user acceptance testing is also a part of this case we make sure that our client is set up for success with complete handoff documentation to maintain the product tip number three continue to evolve processes to remain knowledgeable as technology evolves research and experimentation are a must along with working on projects qa team members also work in smaller groups to research experiment and document new tools learning and evolving are a part of our structure we frequently get together as a team to talk about what's working and what needs to be changed these tips have been fundamental in developing a robust qa process at working code and ensure we consistently deliver the best products i hope it helps you as well [Music] you