Best Practices for Working Together to Achieve Software Quality

Java Development Research Library

 WHITE PAPERS   MULTIMEDIA 
SEARCH the Research Library: WHAT'S POPULAR
sponsored by CA Technologies.
Posted:  10 Jan 2014
Published:  10 Jan 2014
Format:  PDF
Length:  13  Page(s)
Type:  eGuide
Language:  English


ABSTRACT:
For too long, the relationship between development and operations teams has been adversarial. Many IT organizations deal with developers not testing before releasing and change managers who never approve any changes. If this sounds like trouble, it's because it is -- a gap in communication can lead to software defects, project overruns, and high costs.
But with DevOps, you can address these challenges by getting dev and ops teams on the same page and helping them understand each other's needs. But how and when should you go about using DevOps?
View this expert e-guide to find out why ALM consultant Howard Deiner says "a lot of DevOps teamwork should happen in the cusp right before deployment" and explore DevOps tactics for working together to achieve and maintain software quality.




BROWSE RELATED RESOURCES
Application Deployment | Application Development | Application Life-Cycle Management | Application Performance Management | Software Development Life-Cycles | Software Project Management | Software Quality Assurance | Software Testing

View All Resources sponsored by CA Technologies.

Library Home | Advertise with Us | Partner with Us
 
Powered by Bitpipe
 
Java Development Research Library Copyright © 1998-2010 Bitpipe, Inc. All Rights Reserved.
Designated trademarks and brands are the property of their respective owners.
Use of this web site constitutes acceptance of the Bitpipe Terms and Conditions and Privacy Policy.
webmaster@techtarget.com