Evaluate Weigh the pros and cons of technologies, products and projects you are considering.

10 tech terms the business side needs to know

Scott McCarty, head of technical product marketing for containers at Red Hat, thinks we all just need to get along, and for that to happen we need to understand each other better.

With that in mind he’s pulled together a list of 10 tech terms the business side needs to understand. Perhaps you’ll want to print this out and hand it to your product manager or line of business person.

  1. DevOps: “At the end of the day it’s about devs and ops getting along better and having Ops architecture embedded in the dev process so that what devs put in to production already works right,” McCarty explained. It should be flexible, but it should also be sure to reward the ops people — the maintainers — as much as the developers — the creators — are rewarded.
  2. DevSecOps: All of the above plus security people actually working with developers and operations people. “They’re not there to say no, they are there to help the business,” McCarty said.
  3. BizDevOps: “This is the next logical step, bringing the business in with dev and ops and fine-tuning it all.” The bottom line: dev and ops need to be doing what the business needs so they all need to work together. And that’s BizDevOps.
  4. Linux containers: “These are my babies,” McCarty joked. But he’s serious about the need for business to understand the benefits of containers. “Containers make it easy to move the code and provision or update it in different places and that allows the business flexibility. But what they need to understand is it does take some investment to make it happen.”
  5. Microservices: “This is completely driven by the developers,” McCarty said. “This does nothing for the ops side.” Basically microservices break an app in to pieces making it easier to divide up the work and/or bring a new hire up to speed more quickly. “This is something that enables BizDevOps.”
  6. Automation: “This is a confusing one sometimes,” McCarty admitted. “This really enables business flexibility, like BizDevOps.” But it can be a two-edged sword. “Automation doesn’t necessarily make a project happen faster and it can throw a monkey wrench in to the works.”
  7. Orchestration: “Orchestration is to help ops teams in production manage their resources efficiently,” McCarty said. “It’s not about scaling headcount but scaling the business.”
  8. CI/CD: Continuous integration/continuous delivery builds on everything else that’s going on and brings in testing to the process, McCarty said. “Most companies are doing CI, but not many are truly doing CD. CI makes it a simple decision to put something in to production vs. waiting 10 hours, and that gives the business flexibility.”
  9. Agile everything: “I see business people abuse the word ‘Agile’ all the time,” McCarty complained. “Most business people aren’t Agile. Don’t call a process Agile without understanding what it really means.” In other words, if there aren’t standups, sprints and reviews, it’s probably not Agile.
  10. Infrastructure as Code: “This is another piece of DevOps,” McCarty said. The ability for programmers to manage data center provisioning through high level coding gives an organization a big leg up. “From the business side infrastructure as code costs a bit more in time and money to do but the benefits are massive.”

Join the conversation


Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

Do you plan on developing Windows 8 applications for your enterprise?
You cannot keep changing the platform so radically without offering easy migration of apps. Vista and Win7 were bad enough but Win8/9 are not on our horizon at all. Microsoft tells us it's a better customer experience but it's a developer's nightmare
Giving Linux and Android a serious look for the future.
I think it is fair to say that it is too early to judge Windows 8. Microsoft have made a very risky gambling with their new OS. It is a great initiative to combine Desktop application with mobile apps experience in one OS!
We do not wish to create a Windows 8 "only" app though so along with many, we try our hand at HTML5, JavaScript for the majority of platforms.
Win8 is horrible. we are in the middle of moving to web based solutions.
Windows 8, like Windows phone will not gain any sort of market share. Android and IOS (in that order) have an ever increasing market share. If Microsoft still want to be around in 5 years time, they need to start porting Office to Linux, seriously, they have proven several times that they don't take their customers seriously: Windows Me, Windows Vista, Windows 8.
Currently enterprise is just moving onto Win7 this quarter from Vista. Don't expect a fast move to Win8
I've invested 'too-many hours' in WPF apps :P
and still thinking that windows 8 UI isn't a go for serious business-apps.
but only if I don't have to use Metro controls. They are too confining. I need something like the MFC ribbon resource and MFC's top to bottom code accessibility to write production code for Win8. I love the refactored COM in winmd.