INFORMAZIONI SU QUESTO EPISODIO
In this fourth and final discussion, Laurel and Paul discuss how IBM has transformed their own software engineering approach with new devops processes, tools and culture. This is a topic that will interest our Government clients as they learn about and adopt devops in their their departments and agencies, but really clients in all industries will enjoy and use the information in this last podcast. Joining Laurel and Paul are David Leigh, Jeanette Deupree, Xavier Segovia and Irene Penney from IBM who share their stories of DevOps adoption and important lessons learned.
Inglese
Stati Uniti
IN QUESTO EPISODIO
TRASCRIZIONE 🔗
Are you the producer of this podcast?
Add a podcast transcript
Need Audio-to-Text?
Transcribe with Listen411 in Just 60 Seconds
CERCA TRA GLI EPISODI PASSATI
Cerca gli episodi passati di IBM Rational software podcast series.
ALTRI EPISODI IN QUESTO PODCAST
Continuous Engineering is an enterprise capability that speeds delivery of increasingly sophisticated and connected products by helping businesses to evolve their engineering practices to adapt to the accelerating pace of business change. Continuous engineering isn’t “continuous” in the sense that…
Defects are many times less expensive to rectify the earlier they are caught in development cycle. In this podcast you will learn about an IDE that provides automated tools to quickly create high quality code during the implementation of software that addresses this issue by moving defect resolutio…
Companies are realizing that they must become more productive to remain competitive. For most, this means pushing out more sophisticated applications faster, and in order to do this they often must extend their backend IBM i systems to multi-platform front ends. We’ll cover the application develop…
Collaborative development enables teams to work together across tools to deliver quality software faster. Speakers, David C. Myers and Kimberly Gist
Poor requirements management is among the significant contributing factors in the failure of a project. Improper requirements management can lead to disconnected teams, wasted time, out-of-control costs and unsatisfied customers. If you use documents, spreadsheets, emails, wikis and other conventio…
Dichiarazione di non responsabilità: Il podcast e la grafica incorporati in questa pagina provengono da IBM, che è di proprietà del suo proprietario e non è affiliato o approvato da Listen Notes, Inc.
MODIFICA
Grazie, ci hai aiutato a mantenere aggiornato il database dei podcast.
