Stories
Slash Boxes
Comments

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 17 submissions in the queue.
posted by on Monday January 16 2017, @05:47PM   Printer-friendly
from the bingo! dept.

Submitted via IRC for TheMightyBuzzard

In today's fiercely competitive environment for customer satisfaction and brand loyalty, agile and DevOps are driving happier customers and employees. Results from a new CA Technologies global study reveal that advanced users of agile or DevOps realized significant increases of up to 52 percent in customer satisfaction and up to 50 percent in employee productivity.

The results showed a 30 percent advantage in employee recruitment and retention for companies that used agile and DevOps together to improve the working atmosphere for their employees – a huge benefit when you consider the shortage of talent in IT and the costs associated with attracting and retaining the best employees.

I guess I can't argue against it since I've been doing it nearly everywhere I've worked since the late 90s. Having separate Dev/Ops teams in SMBs [Small and Medium Businesses] is a pretty hard sell.

Source: https://www.helpnetsecurity.com/2017/01/12/devops-adoption/


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by Thexalon on Monday January 16 2017, @11:30PM

    by Thexalon (636) on Monday January 16 2017, @11:30PM (#454601)

    Where I am, DevOps means that devs have access to infrastructure and can provision what they need. It takes good tools to give that kinds of access without worrying about whether devs understand the nuances, sure. But we have good tools, mostly based on AWS.

    Then what it sounds like you are doing isn't DevOps, what you're doing is outsourcing a lot of the "Ops" side to Amazon. That can certainly work, but that's not the same thing as having nobody focused on infrastructure: Just because the people doing it aren't working for your company does not mean nobody is doing it.

    I agree that devs could and quite possibly should develop the infrastructure scaling code. But the ops side should be designing the specifications of said infrastructure scaling code, as well as having input on the specifications for the code being scaled so that it does so more easily. And that still leaves ops plenty of other things to do, like hardware maintenance (if you have any of your own hardware), security management, backups / disaster recovery, and of course figuring out how to best give the devs what they need to fulfill the latest silly requirements imposed by marketing.

    --
    The only thing that stops a bad guy with a compiler is a good guy with a compiler.
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2