Comments
Puppet Labs Teams With Networking & Storage Vendors
Newest First  |  Oldest First  |  Threaded View
AbeG
50%
50%
AbeG,
User Rank: Black Belt
6/28/2014 | 5:11:43 PM
Re: Functionality vs. Quality Adaptability
DevOps, like project management software, is great in theory but it also adds another layer to an existing process and requires a certain amount of time to get up to speed on and to nuture the habit of using it.
MarciaNWC
50%
50%
MarciaNWC,
User Rank: Strategist
6/25/2014 | 11:14:15 AM
Re: Functionality vs. Quality Adaptability
I think you may be right Brian. Startups are agile to begin with, while shifting to a DevOps model in an established IT organization faces a lot of challenges, perhaps making actual gains more elusive. 
Brian.Dean
50%
50%
Brian.Dean,
User Rank: Ninja
6/25/2014 | 7:31:25 AM
Re: Functionality vs. Quality Adaptability
Marcia, good point and I have a feeling that new IT organizations that are successful, have a solid business model and deliver high value apps, don't activity consider the level of DevOps in their model, because from the beginning, their firms were born into the DevOps model.

As for old firms, some IT organizations have attempted to focus on building competency around the spectrum (non-specialization model), rather than, out-source support function to the Cloud with firms that own economies of scale and focusing on their core specialization. This results in a situation where the organization is dealing with multiple layers, and they can't focus on their core competency -- making DevOps, to only look good on paper.
MarciaNWC
50%
50%
MarciaNWC,
User Rank: Strategist
6/24/2014 | 8:43:59 PM
Re: Functionality vs. Quality Adaptability
The DevOps promises of communication and collaboration are certainly promising, but according to an InformationWeek DevOps survey released early this year, adoption so far has been sort of tepid and the results mixed.
Brian.Dean
50%
50%
Brian.Dean,
User Rank: Ninja
6/24/2014 | 3:48:27 PM
Functionality vs. Quality Adaptability
A firm can lock their programmers into a room, hand over a list of desired functions and set a deadline. The result will be a software that works (at times), because neither would the programmers fully understand the problems that the software is trying to address, and neither can the firm foresee and create a comprehensive list of desirable functions because, functions, requirements and objectives, evolve with time.

DevOps can bridge these gaps by using communication and collaboration between the teams that are creating the software and the teams that will be utilizing/operating it. 


White Papers
Register for Network Computing Newsletters
Cartoon
Current Issue
2014 State of Unified Communications
2014 State of Unified Communications
If you thought consumerization killed UC, think again: 70% of our 488 respondents have or plan to put systems in place. Of those, 34% will roll UC out to 76% or more of their user base. And there’s some good news for UCaaS providers.
Video
Slideshows
Twitter Feed