![\"Switching](\"https:\/\/devoteam.info\/wp-content\/uploads\/2024\/12\/devops-agile-transformation-devoteam.png\")
<\/a><\/figure>\n\n\t\t\n\t\tModern concepts are helping us to see the overall IT landscape in order to have a better understanding of relationships between domains. However, that doesn’t necessarily mean accurate spotting of blockers, bottlenecks, gaps and improvement areas. As usual, the devil is in the details. Some old timers still use their personal skills and experiences to spot these issues, though that doesn\u2019t guarantee efficiency or accuracy.<\/p>\n
Delivery Rationalization Framework<\/strong><\/h2>\nLast year the Delivery Rationalization Framework (DRF) team was asked to design and develop Continuous Integration & Delivery (CI-CD) and Test Automation implementations for one of the big telecom providers in Europe. For that they have used the DRF to assess and analyze this enterprise\u2019s needs. During that exercise it was clear to the DRF team that they were lacking the bird\u2019s-eye view of the IT delivery process. This shortcoming had affected the team\u2019s judgment, analysis and consequently the DRF assessment results. As a result the DRF team then recommended a new approach to IT Process Reengineering. This approach has been well received by the client management.<\/p>\n
Dividing the IT processes into functional and logical steps<\/strong><\/h2>\nThe new approach boils down to dividing the IT processes into functional and logical steps (up to a certain granularity). Then one defines the input & output contracts for each step, as well as the tasks performed during that step. This might seem normal or similar to any ordinary workflow, but the advantage of this approach is that it adopts many modern aspects inside the process such as automation, self-sustainability, process enforcement and governance in a correct harmony. In addition, the team has coupled the process with a responsibility matrix that links each detailed action inside the input, the output or inside the step itself to a responsible team or function. Since the client was moving from a waterfall mindset to Agile, this was one of the most important advantages of this IT Process. Why so? Because this process could cater for both waterfall and agile by only switching roles to functions.<\/p>\n
Benefits<\/strong><\/h2>\nThe benefits of this process were not visual to the DRF team until they started to use it as part of the DRF service offering for new clients. Only then did the team started to see the real impact, based on the customer\u2019s feedback. Surprised yet satisfied, 100% of our clients that have seen this process admitted that they don\u2019t have anything like it. They indicated that they need something similar. Over 50% of these clients admitted that they believe that most of their problems could have been solved or mitigated just by having a similar process.<\/p>\n
The Eagle\u2019s-eye view<\/strong><\/h2>\nWhat give this process incredible impact? The answer is: Perspective. By shifting the focus from a zoomed in step to a wider range of end-to-end activities, bottlenecks are easily identified and addressed. In a typical Continuous Integration \/ Delivery assessment the assessment team would be more concerned about the technical build, deployment and testing. In theory this is enough to design a CI-CD cycle but not enough to anticipate potential risks or find hidden bottlenecks. But in our new process the view is different since we widen the horizon and vision to include the whole IT delivery process from End to End. Diving into details to certain level that reveals the hidden factors and potential problems which are real and are impacting the delivery process and the successful implementation of CI-CD. And that is why we call it Eagle\u2019s-eye view.<\/p>\n
The new approach boils down to dividing the IT processes into functional and logical steps (up to a certain granularity). Then one defines the input & output contracts for each step, as well as the tasks performed during that step. This might seem normal or similar to any ordinary workflow, but the advantage of this approach is that it adopts many modern aspects inside the process such as automation, self-sustainability, process enforcement and governance in a correct harmony. In addition, the team has coupled the process with a responsibility matrix that links each detailed action inside the input, the output or inside the step itself to a responsible team or function. Since the client was moving from a waterfall mindset to Agile, this was one of the most important advantages of this IT Process. Why so? Because this process could cater for both waterfall and agile by only switching roles to functions.<\/p>\n
Benefits<\/strong><\/h2>\nThe benefits of this process were not visual to the DRF team until they started to use it as part of the DRF service offering for new clients. Only then did the team started to see the real impact, based on the customer\u2019s feedback. Surprised yet satisfied, 100% of our clients that have seen this process admitted that they don\u2019t have anything like it. They indicated that they need something similar. Over 50% of these clients admitted that they believe that most of their problems could have been solved or mitigated just by having a similar process.<\/p>\n
The Eagle\u2019s-eye view<\/strong><\/h2>\nWhat give this process incredible impact? The answer is: Perspective. By shifting the focus from a zoomed in step to a wider range of end-to-end activities, bottlenecks are easily identified and addressed. In a typical Continuous Integration \/ Delivery assessment the assessment team would be more concerned about the technical build, deployment and testing. In theory this is enough to design a CI-CD cycle but not enough to anticipate potential risks or find hidden bottlenecks. But in our new process the view is different since we widen the horizon and vision to include the whole IT delivery process from End to End. Diving into details to certain level that reveals the hidden factors and potential problems which are real and are impacting the delivery process and the successful implementation of CI-CD. And that is why we call it Eagle\u2019s-eye view.<\/p>\n
What give this process incredible impact? The answer is: Perspective. By shifting the focus from a zoomed in step to a wider range of end-to-end activities, bottlenecks are easily identified and addressed. In a typical Continuous Integration \/ Delivery assessment the assessment team would be more concerned about the technical build, deployment and testing. In theory this is enough to design a CI-CD cycle but not enough to anticipate potential risks or find hidden bottlenecks. But in our new process the view is different since we widen the horizon and vision to include the whole IT delivery process from End to End. Diving into details to certain level that reveals the hidden factors and potential problems which are real and are impacting the delivery process and the successful implementation of CI-CD. And that is why we call it Eagle\u2019s-eye view.<\/p>\n