IT organizations are adopting DevOps practices to speed more frequent software releases to production and to not only accelerate time to market but to improve overall customer experience. But, adopting DevOps practices requires a cultural shift in terms of people, process and technology involved in development, testing and operations. Many organizations encounter significant challenges when embracing DevOps, particularly when implementing it in legacy areas, obstacles that have proven far more difficult to overcome compared with those encountered by digital-native companies.
There is a popular mindset that DevOps is about throwing away everything you have built so far and starting from scratch. That is untrue. More critical in large organizations is the need to improve communication and collaboration between IT team disciplines. Changing such behavior can be cumbersome especially when regulatory and audit compliance require existing organizational structures to remain as is.
Developers, testers and operations engineers typically play different roles, and have varying responsibilities, job descriptions, and working cultures in traditional IT organizations. All work in separate functional areas as distinct entities. Can testing teams play a key role in bringing various groups together under the DevOps flag and spur adoption? This session will answer that question and elaborate the approach.