time and effort. Experience based and defect based test design techniques should be followed. Report Bugs only Testers should not test it but if bugs related to this risk arise during other tests, report those bugs. Based on the Risk Assessment Matrix (RAM), Risk Priority and Extent of Testing, we decide testing levels to be performed as a part of those risks as below. Test Level Definitions Test Level Owner Objective (s) Key Areas of Testing Unit Development - Detect Defective Code in Functionality and system (Scrum) units resource utilization - Reduce Risk of unit failure in Production Integration Development - Detect Defect in unit Functionality, data quality, (Scrum) interface unit interoperability and - Reduce risk of dataflow compatibility, performance and workflow failure in production System System Tester - Detect defects in use Functionality, data quality, (Scrum) cases and end-to-end performance, reliability, scenarios usability, system resource - Assisting mitigating risk utilization, maintainability, of unmet business instability, portability and requirements in interoperability production Acceptance UAT - Demonstrate readiness Functionality (Business) for deployment - Detect defects in user workflows All above matrices will be used to prepare QRA document in which identified risks are mapped with respective PBI’s and same is shared with BA and TL for Business Risk Assessment and Technical Risk Assessment. BA and TL provide Business Risk and Technical Risk ratings and related comments. At initial level, Risk Mitigation column is set to NO, however it will be set to YES once we deliver the PBI as a part of future sprints. This QRA document will look like as per below.
time and effort. Experience based and defect based test design techniques should be followed. Report Bugs only Testers should not test it but if bugs related to this risk arise during other tests, report those bugs. Based on the Risk Assessment Matrix (RAM), Risk Priority and Extent of Testing, we decide testing levels to be performed as a part of those risks as below. Test Level Definitions Test Level Owner Objective (s) Key Areas of Testing Unit Development (Scrum) - Detect Defective Code in units - Reduce Risk of unit failure in Production Functionality and system resource utilization Integration Development (Scrum) - Detect Defect in unit interface - Reduce risk of dataflow and workflow failure in production Functionality, data quality, unit interoperability and compatibility, performance System System Tester (Scrum) - Detect defects in use cases and end-to-end scenarios - Assisting mitigating risk of unmet business requirements in production Functionality, data quality, performance, reliability, usability, system resource utilization, maintainability, instability, portability and interoperability Acceptance UAT (Business) - Demonstrate readiness for deployment - Detect defects in user workflows Functionality All above matrices will be used to prepare QRA document in which identified risks are mapped with respective PBI’s and same is shared with BA and TL for Business Risk Assessment and Technical Risk Assessment. BA and TL provide Business Risk and Technical Risk ratings and related comments. At initial level, Risk Mitigation column is set to NO, however it will be set to YES once we deliver the PBI as a part of future sprints. This QRA document will look like as per below.
quality-strategies-in-agile.docx