July 28, 2016

In traditional software development, the professionals who were responsible for building a company's applications were referred to as development. The team that tested the applications was QA management. At this point, the program would be handed off to operations, which would then be responsible for maintenance and update management. This methodology was called waterfall development, and it had obvious shortcomings.

>Read the source article at dzone.com

Related Resources: 

VectorCAST for DevOps Testing - In the age of Internet of Things (IoT) product development, more than ever, time to market is critical. Reducing the code-to-deployment time requires much greater collaboration between teams. Yet surprisingly, many organizations are still operating in silos when it comes to product development

The Phenomenon of Technical Debt - The technical debt metaphor is gaining quite a bit of traction in the software development world. This term was coined by American Ward Cunningham in a report at the OOPSLA conference (Object-Oriented Programming, Systems, Languages & Applications, an annual ACM research conference) in 1992; he said, "Shipping first time code is like going into debt. A little debt speeds development, so long as it is paid back promptly 

Posted under
DevOps News