1 / 1

Can Speed and Quality Coexist in the SDLC?

Different roles in an organization think about speed and quality differently. They also define and measure functional and non-functional requirements differently. Discover what this means for the evolution of “quality” in the era of Continuous everything. Visit http://bit.ly/28NGOzP to learn more. <br>

Parasoft
Download Presentation

Can Speed and Quality Coexist in the SDLC?

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Can Speed and Quality Coexist in the SDLC? There’s a gap between business expectations and DevTest activities The Business DevTest Team Poor Software Quality Parasoft conducted a survey asking 780 software developers about functional and non-functional requirements (NFRs) 5 KEY TAKEAWAYS 1 A majority of organizations are unable to assess the real business risks associated with a software release candidate 55% NFRs of teams do not measure compliance to NFRs 2 Reducing the risk of application failure requires much more than functional testing *Types of software development methodologies employed 3 There is an inverse correlation between more ‘Agile’ methodologies and the likelihood that teams measure NFR compliance 38% 58% of Agile-ish and Agile teams are monitoring NFRs of Waterfall teams VS *Types of software development methodologies employed 4 Organizations that rely too heavily on developers and testers to de?ne ‘quality’ will cultivate a rift with the business The Business DevTest Team 5 The shift to DevOps requires organizations to clearly de?ne and automatically measure the acceptance criteria for a software release candidate 4 ACTIONS FOR TEAMS Jointly de?ne business risks at project’s onset Understand KPIs and acceptance thresholds for NFRs Automatically measure and monitor NFRs Review and continuously improve the process of risk mitigation Better Software Quality Get the full report with critical action items now Copyright © 2016 Parasoft

More Related