QA Anchor Advocate for Quality

Editor's Notes

• #4: 1. Mention agile, Kanban Continuous Delivery, Context and Behavioral Driven Dev = leading to Exploratory Testing Context and Behavioral Driven testing. 2. Tech QA = mid lvl dev and sr. QA in one role, BSA merges the BA role with the System Analyst role. 3. For various reason such as rapidly changing market place and new methodologies to answer the demand the market places on software products.
• #6: QA Anchor does and how this job function works? The QA Anchor infuses the software creation culture and ethos with quality behaviors and habits that will enhance the level of quality at every level of the creation of working software. The QA Anchor strives to be the glue that holds projects together. The QA Anchor collaborates with stakeholders and project team to identify needs and gather requirements. The QA Anchor Advocate and Evangelize for best practices like pair programming,  Test Driven Development (TDD), Behavioral-Driven Development (BDD), Continuous Integration (CI), Continuous Delivery (CD) and The QA Anchor Advocate automation of every part of the software delivery lifecycle The QA Anchor lets go of Functional testing and empower the entire team to own quality.
• #7: 6. Drive use of Open Source and share latest tools and trends across teams. 7. Coaching and enabling of project teams. 8. Learn something new every day.  9. The Quality Anchor is a integral part of a dynamic, collaborative, transparent, non-hierarchal, and ego-free culture where your talent is valued over a role title. 10. As a Quality Anchor, you will help us to create outstanding user experiences by assisting developers to validate the quality of their code.  In your role, you will perform exploratory testing and pair-program with another team member (Designer, Developer, Analyst) to complete a user story.  You will complete help developers with Test Driven Development (TDD) and potentially create automated test scripts to ensure a full suite of testing occurs.  You will work directly with the team in real time and will participate in the acceptance testing by the Product Owner to gain acceptance of the story.
• #9: Experience with open source test automation tools and frameworks. A rich breadth of experience in web and mobile fundamentals. An eagerness to do what it takes to get the job done. Whether that means going back to the drawing board with a problem or simply taking on different roles and responsibilities for a period of time - you thrive at adapting to changing environment Experience in mentoring and executing Agile, Lean, and Continuous Delivery best practices. A disruptive attitude towards technology innovation.
• #10: Skills/Experience: Communicates internal IT service quality control standards, policies and procedures. Monitors, evaluates, manages and executes audit processes to ensure compliance Works closely with Digital Services leaders to develop and implement an overall quality maturity roadmap and plan. Reviews progress toward the plan regularly with Digital Services leaders, technical teams and customers to make modifications as necessary Designs, monitors and analyzes performance metrics program for quality improvement initiatives. Conducts audits and analyses findings to develop appropriate corrective action recommendations. Coordinates and facilitates quality assurance activities for a product or set of products delivered by the Digital Services Team
• #11: The development environment must be dynamic and flexible. Creativity and intuition are allowed to guide the quality process. There is no fear of change as change equals opportunity!
• #14: Brief on QA Anchor focus on Exploratory test deliverable. Overview of Exploratory testing: Explain diff between Functional (Predictive / Verification test: “Are we building the product right?" The software should conform to its specification.) , and exploratory testing (Subjective/ Intuitive, Validation test:“ Are we building the right product?" The software should do what the user really requires.) The Exploratory test charters are used for keeping track of an exploratory test session’s findings. Exploratory testing itself is a documented approach to testing a system’s functionality with an architecture that is largely unknown. Ask for question after each section   Present the Exploratory testing doc and explain the sections
• #15: Engagement Walk about QA Anchor Engagement guidelines Exploratory test activities and test techniques we use: Paired exploratory testing. Time box: 3 min Recording , Video time box executions Compare with Exploratory template for EZ pay Demo recorded testing method. Demo paired testing with Bob. QA Anchor Engagement
• #16: The QA Anchor guides dev and org to quality practices. The QA Anchor empowers the team to own quality and freely transfer the traditional testing responsibilities to them. The QA Anchor not focused on doing testing but weaving testing and quality behaviors into the development culture. The QA Anchor is Advocate, Evangelist and Coach of the teams Culture of Quality. The QA Anchor is hands on in leading/ performing Exploratory testing and identifying/ introducing new tool and techniques to the team to enhance the quality of each release of the product