For global corporations, it does not lack the management framework and standard for best practice. In the last few years we have seen the digital transformation initiative where most of the great enterprises and their chief have put DT first in their top priority. Simply go cloud computing where you do not make your enterprise DT-ed. There are two missing links here in the equation.
One is the business innovation, where you either have it or you don’t, and that also touches on the external market and competition, not just the company. Another missing link is to put the cloud computing work for the strategic intent you bid on the business innovation. We keep saw some company said their productivity breakthrough to 100x or more, if you look insight carefully, you will notice where that 100x or more where they come from, it come from the automation, by the process automation or make use of the robotic process automation (RPA), artificial intelligence (AI) for chatbot and technology automation, where this few years, devops or secure devops or devsecops is become popular, where next era is value stream management (VSM).
Depending on the entire continuous integration and continuous delivery CI/CD tool chain your enterprise is using for operation.. The more seamless automation that for auto DevOps (or auto DevSecOps if the security testing process is also automated), that portion will free up a lot of employee time to wait the process or someone before continuing the next process in the seamless automated manner. Typically that will reduce a lot of enterprise development and operation time from performing anything manual, this is where the promise of devops for. Do not get me wrong, manual and highly professional expert penetration testing and red team operations remain useful and need to be carried out from time to time, what is discussed here is the daily development, operations and security automation.
From adoption of best of class for each CI/CD toolchain product and then integration or simply just replacing all in a single app to perform all the CI/CD for the DevSec or DevSecOps to free up the time and cost of ownership, is where the most is doing. Most of the CI/CD toolchain can be open source and free in nature, if your enterprise knows how to integrate them else get the full auto DevOps commercial package. The important thing is not just to do DevOps or DevSecOps just for the shake to do it, you need to have the digital transformation initiative or strategic theme for it. Generally to speak, the more users enroll into the auto DevOps process, the more time it free up, it particular for the enterprise with internal software development, this is why it always need to involved source code management (SCM), CI/CD, application security testing (AST), to project management and issue management, as part of the business use case.
TOGAF now in version 9.2: it is a method to capture and transform Enterprise Architecture (EA). It remains one of the main standard and best practice interactions of the stakeholders with the architecture of an enterprise and the proposed opportunities or solutions needed to create value in a business, in particular for the solution architecture (SA) to follow. The process focuses on use of a standard, or consistent, process model to measure and develop your enterprise architecture (EA). Agile is an umbrella term used to bring together and organise several development methods including software development into a collaborative and cross functional manner.
Regardless of TOGAF, Agile to DevOps, you can not use them in isolation from others to make it work. You need a proper documented enterprise architecture (EA) first. It is particularly important to resolve issues of this type at their source and even seek re-approval of an in-progress program if a significant stakeholder has not committed their support, the bigger the organization, in particular for global in nature, this you need to get it right first. A detailed check using the TOGAF Architecture Design Method (ADM) should be able to help find all the information needed and avoid missing parts for solution architecture (SA) that make sure for solution delivery that puts the strategic theme and intent first before the operation. Else, the enterprise is most likely efficient but not effective, because it is missing to get what matters to put first.
Using the TOGAF version 9.2 ADM model across the Architecture Landscape, recheck steps A to D to identify missing architectures, systems and stakeholders. This may require that the Preliminary and Requirements Management records require change to add or include any missed information. Also, consider using DevOps value stream mapping methods to cross check that your enterprise architecture fits your product needs.
In modern projects most are adopting an agile development process for DevOps. For agile development, requirements arrive from the enterprise architecture as epics. These need storyboarding and aligning with the product vision before features and tasks are created that fit into sprint cycles. Using sprint cycles to deliver work offers significant benefits as, at the end of each sprint, a working product is released.
During implementation of large features, get your stakeholders to accept and agree that it is unlikely that one epic or feature will fully exist after a single sprint. There is significant benefit with this approach as at the end of each sprint, the stakeholder can decide if a feature is “complete enough” to meet their needs based on the commit time, resource and quality. This removes waste as functionality that is not needed is not implemented, again, helps you get away from being efficient but not effective.
When it comes to DevOps, some projects work this way, some do not. Some products and features are suitable for seamless DevOps release methods of continuous integration (CI) and continuous delivery (CD) whereas others are not. For example, cloud-first, cloud native and central cloud hosted solutions are often suitable for CI/CD processes. But remote, off-internet, and on-premise solutions might be more challenging to get work and benefit from the DevOps, due to some extent, it is full of docker containers and microservices. Nevertheless, the market is expected to shift left earlier, if possible, implement CI/CD early in the implementation process (for example, in early sprints of development, so CI/CD set up activities can be entered into the features and tasks of agile development sprints).
E-SPIN Group in the enterprise ICT solution supply, consultancy, project management, training and maintenance for corporation and government agencies did business across the region and via the channel. Feel free to contact E-SPIN for your project requirement and inquiry.
Other post you may be interest:
