Re:The DevOps Phenomenon: An executive crash course
by solatic on Thursday June 06, 2019 @03:01AM
(#20112212)
You kind of answered your own question. Word documents aren't code. Take all these managers and get their concerns into code. That means dedicated engineers to turn non-code into code, lower management that can negotiate with stakeholders to figure out what to prioritize, and upper management to get stakeholders to play ball with lower management. Standard enterprise project management, really.
Re:The DevOps Phenomenon: An executive crash course
by Spooky23 on Wednesday June 05, 2019 @07:21PM
(#20110089)
You need to have the courage as a leader of such an organization to put accountability in a place that results in delivery and provide services and culture to get it done.
Re:The DevOps Phenomenon: An executive crash course
by cc81 on Thursday June 06, 2019 @04:55AM
(#20112756)
There is tons of accountability. That is why you have the delivery managers, the lengthy handovers, checklists and slow processes. So nothing goes wrong and those that are accountable can be cleared from any blame.
The target audience here is a large enterprise that has value cost and stability for years and has separate Dev and Ops (often not in the same country) and not only follows all those standard processes but has also added a lot of their own written Word documents to the pile. There are check lists, approvals, delivery managers, product managers and all kinds of other managers involved in every release.
How do they even start with your advice?