The Gap Between DevTest and the Business

1. The Gap Between Business Risks and Software: How Teams Measure Non-functional Requirements

2. Software Development Lifecycle Trends Every business demands: Acceleration of the software development lifecycle Innovative software that bonds customers to its products and services Speed Quality Speed and quality are no longer tradeoffs: modern organizations must have both

3. Speed and Quality: What Does That Mean? Different parts of the organization think about speed and quality differently I’m not done testing yet! Are we done yet? Is the user story complete? Business Person Developer Tester NFRs We must understand the business risk of a release candidate

4. What Is a Non-functional Requirement (NFR)? NFRs describe how the overall system should behave • Application resiliency • Accessibility • Availability • Reliability • Testability • Regulatory compliance NFR Examples

5. Parasoft Study Explored the Evolution of Quality across Dev Methodology Only 38%of Agile-ish and Agile teams are monitoring NFRs… “Yes, my team monitors compliance to non-functional requirements (NFRs)” Agile-Ish Agile 59% …compared with Iterative of Waterfall teams who do so Hybrid Waterfall 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% To explore the impact of the accelerated SDLC, Parasoft conducted a survey asking software developers about functional and non-functional requirements

6. Is Agile Compromising Quality in Pursuit of Speed? Agile’s quick iterative approach focuses test teams on bottom up user stories The Result Non-functional requirements are deprioritized Testers focus on new user stories * The Business Risks of the Release Pipeline Survey Results: How Teams Measure Non-Functional Requirements, 2016; commissioned by Parasoft

7. Study Findings – INVERSE Correlation Between SDLC Pace and NFR Measurement Agile Waterfall Discover Sprint 1 Design Sprint 2 Develop Test Sprint 3 • Agile’s speed leaves little time for testing NFRs • Waterfall’s slower pace leaves more time for testing NFRs • Inverse correlation between Agile methodologies and the likelihood that teams will measure NFR compliance

8. Measurement of NFRs ! • Developers and testers do not believe that NFRs are being appropriately defined and measured Management and business analysts are 7x more likely to believe that NFRs are measures and monitored consistently

9. Gap Between the Business and Dev Team The Business Dev Team Deadline pressures result in ignoring: • Holistic user experience • Impact of change on the broader system • NFRs Assumes business risks are being mitigated—but neglected NFRs can expose the company to: • Bumpy user experience • Erratic system behavior • Standards and regulatory compliance risk Software quality

10. Closing the Gap Between the Business and the Dev Team • Jointly defining business risks at project’s onset • Understanding KPIs and acceptance thresholds • Automatically measuring and monitoring NFRs • Reviewing and continuously improving mitigation of business risk Better Software Quality

11. Recommendations for Quality @ Speed • Ensure all parties understand risks and tradeoffs • Continuously train on the impact of failure • Establish quality gates • Implement escalation processes • Adopt a continuous improvement mindset To rapidly assess the risks of releasing applications: Security Availability Reliability Compliance Quality

12. Teams Must Collaborate to Mitigate Risk • Business risks drive quality activities • Teams collaborate on the definition of risk • All team members are trained on risks and mitigation tasks • Baseline and threshold criteria are measured and monitored • DevTest team activities are prioritized per risk definition Policy NFRs KPIs and Acceptance Thresholds Automated Measurement and Monitoring

13. To learn more Download Report www.parasoft.com