DevOps in more than software development lifecycle. How about “Architectural Design” ?

By | 2020-07-06T05:42:43+00:00 July 5th, 2020|Insights & Perspectives|

DevOps beyond SDLC. Can DevOps be used in Architectural Design ?

How digital-native businesses use technology

Sure almost every company uses an ERP or a few apps either customer focused or enterprise focused. But that does not build a digital-native business.

  1. What’s more valuable for you ? Is Bottom Line Savings or Top Line Growth Valued? Bottom line savings is essentially cost cutting. Top line growth is growing the revenue of the business. Most enterprises claim to support both but in many cases the beancounters are empowered to reduce costs at the expense of growth.
  2. How Often Do You Release to Production ? Frequent releases are incredibly important to innovation because features often take many iterations before they’re perfected. If a feature takes four iterations to perfect and you’re releasing quarterly, it’ll be a year before that feature is generating value. If you release daily, it could take as few as four days before that feature is generating value.
  3. Can Developers Consume Cloud Resources Independently ? Digitally native organizations allow developers to consume cloud resources as they need them. If a developer wants to use DynamoDB from AWS, he or she can provision some capacity without further approvals. Traditional enterprises would never allow this, but to succeed developers need freedom to make bottom-up technology purchasing decisions. Innovation requires freedom.
  4. Is IT Governance Able to Differentiate Between Different Types of Software ?Enterprises that can successfully apply different models of governance to different types of software are well on their way to being digitally native.
  5. Is There a Parallel Manager/Individual Contributor Track ? The only way to “succeed” (higher pay, higher status, etc) in most traditional organizations is through advancing up the manager track. This pulls top technical talent out of their roles into roles they didn’t necessarily want and aren’t especially suited for. Good individual contributors should be allowed to stay in their roles and contribute to the organization through their individual contributions, with pay and status being equal to managers.
  6. Do You Pay Market Rates for Top Talent ? Many top developers earn hundreds of thousands of dollars per year. Yet many traditional enterprises will balk at that level of pay. A VP of Finance may make 20 lakhs a year but a senior cloud architect may demand 30 lakhs. Justifying that discrepancy to a CEO is hard, but needs to be done.
  7. Is Software Purchased Bottom Up or Top Down ? Most enterprises buy software like they’re buying new real estate or a multi-million dollar piece of manufacturing equipment – from the top down. This model of procurement is completely antithetical to how digitally native enterprises operate. When your orientation is innovation and time to market, it makes far more sense to allow individuals to make the initial procurement decisions. Especially now when software is just so easy to consume with SaaS.

Ask yourself these questions.

  • How can principles used by digital native businesses apply to your industry? Which pain points in your industry are ripe for transformation ?
  • If you could achieve any dream for how your business operates or how it changes the lives of your customers, what would you make happen? Dream big, and then consider how data and machine learning can bring you a step closer to this reality.
  • Which teams in your company are ready to transform themselves? What processes might they redesign? Who can lead the project? Who will champion it? Who will benefit from it?
  • What can your IT resources accomplish with more time? How can enhanced security pay off for your IT team?

No matter how near or far down the path of evolving your company you are, IMSS Cloud and Low-Code Practise can guide you toward the future while learning from the past.