“The Continuous Delivery challenge needs to be viewed as one continuous process, not a set of different processes,” he said. “Not having a single end-to-end process introduces delays and errors.”
Recognize what your delivery needs are and understand the level of quality and risk that is acceptable to your organization,” said AppDynamics’ Butt.
“There is no one-size-fits-all rate of delivery. Some organizations might release several times in one day, some several times a week or even every month. The important thing to focus on is the ability to release incrementally with as much automation as possible, enabling agility,” he said.
Don’t let the tool get in the way. If it isn’t working, you are probably using the wrong tool, according to Wallgren.
“Technology obstacles refer to any system or technology that prevents the ability to create one end-to-end system that shepherds your code from check-in to delivery to avoid gaps in the automation,” he said.
Tools, technology and process may get in the way of Continuous Delivery, but one of the biggest obstacles is people, according CloudBees’ Labourey.
“Moving from a siloed organization to cross-cutting teams requires quite a bit of brain rewiring,” he said. “Some individuals might feel challenged in their habits and/or authority. But as General Eric Shinseki once said, ‘If you don’t like change, you’re going to like irrelevance even less.’ ”
Strong support from management can help organizations overcome these obstacles, but a clear understanding on why this is happening is also important, according to Atlassian’s Wittman.
“The team has to buy into this as a value. They need to see that this is something that is valuable to them and how it can help them build better software,” he said.