The quarterly publication of the International Legal Technology Association
Issue link: http://read.uberflip.com/i/11430
BEST PRACTICES QA Program Elements • Requirements testing Involve QA resources in requirements reviews to determine if requirements are testable and to help identify requirements gaps. • Quality Throughout the Systems Development Lifecycle Incorporate quality concepts in all stages of the project, starting with defining a test strategy in the requirements definition phase. • Unit Testing in Applications Automate unit tests and execute frequently by incorporating them in the build and deployment processes. • Functional Testing Plan and execute repeatable acceptance tests for systems, integration and users to confirm the implemented solution meets requirements. • Test Data Define test data as a separate deliverable to ensure coverage of functional and performance requirements. • Performance / Scalability Testing Establish performance and scalability requirements and verify deployment readiness using performance testing tools and environments. • Automated “Smoke Testing” Automate tests of core functionality and execute as part of build and deployment processes; these can also be run on a daily basis for catching production issues before end users do. • Regression Testing During the development phase, create tests, data and environments for applications that are reusable for future releases. ILTA IMPROVE OVERALL CLIENT SERVICE Well documented, objective reporting using consistent metrics develops trust between project managers and the firm’s partners. An effective quality program establishes well monitored certification activities for all project stages that are intended to demonstrate to the firm that focus is appropriately aligned with higher business goals and objectives. These activities can include independent, third-party oversight to ensure procedures are being followed. In the end, the attention to quality begets higher overall productivity for all concerned, and allows the firm’s leadership to focus on their jobs rather than on technology problems. COMPONENTS OF AN EFFECTIVE QUALITY ASSURANCE PROGRAM Make sure the implemented solution meets the customer needs the first time. Rework dramatically drives up time and costs, so it is paramount to employ the right checks to catch problems early. Note this should not be confused with an iterative “spiraled” approach to project lifecycle. In fact, an iterative approach, where appropriate, plays directly into improving quality as it carves the project into smaller, more manageable segments. Each cycle of requirement, build and deploy can easily be managed in a well designed process. Instill a quality mindset throughout the development, deployment and support lifecycle. The later a problem is discovered, the more costly it is to fix. Stakeholder reviews of key deliverables, formal testing efforts and a focus on future support costs during development are important success factors for reducing overall costs and increasing quality. Quality assurance programs require management- level support and often involve resources who are specifically responsible for providing quality assurance services across the organization. Standard operating procedures are used to implement best practices throughout the firm. Effective QA focuses not just on the firm’s activities, but also is extended to the firm’s vendor suppliers. Firms should demand of their software vendors that they have a rigorous QA program as part of their development lifecycle processes. Service providers should be able to articulate their strategy for managing projects and reviewing work product for defects before it is delivered to the customer. If a provider cannot demonstrate a QA focus, then you can almost surely expect problems in that vendor’s products or services. 18 www.iltanet.org Peer to Peer