All the best!<\/p>\n\n\n\n
Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n
All the best!<\/p>\n\n\n\n
Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n
Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n
All the best!<\/p>\n\n\n\n
Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n
If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n
Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n
All the best!<\/p>\n\n\n\n
Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n
A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n
If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n
Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n
All the best!<\/p>\n\n\n\n
Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n
A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n
A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n
If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n
Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n
All the best!<\/p>\n\n\n\n
Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n
Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n
A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n
A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n
If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n
Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n
All the best!<\/p>\n\n\n\n
Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n
Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n
Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n
A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n
A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n
If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n
Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n
All the best!<\/p>\n\n\n\n
Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n
So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n
Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n
Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n
A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n
A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n
If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n
Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n
All the best!<\/p>\n\n\n\n
Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n
How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n
So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n
Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n
Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n
A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n
A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n
If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n
Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n
All the best!<\/p>\n\n\n\n
Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n
My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n
How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n
So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n
Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n
Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n
A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n
A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n
If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n
Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n
All the best!<\/p>\n\n\n\n
Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n
A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n
My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n
How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n
So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n
Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n
Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n
A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n
A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n
If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n
Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n
All the best!<\/p>\n\n\n\n
Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n
One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n
A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n
My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n
How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n
So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n
Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n
Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n
A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n
A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n
If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n
Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n
All the best!<\/p>\n\n\n\n
Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
![\"\"](\"https:\/\/www.pm-powerconsulting.com\/wp-content\/uploads\/2014\/11\/MSDN-DevOps-cycle.png\")
<\/p>\n\n\n\n
Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n
One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n
A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n
My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n
How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n
So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n
Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n
Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n
A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n
A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n
If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n
Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n
All the best!<\/p>\n\n\n\n
Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n
<\/p>\n\n\n\n
Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n
One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n
A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n
My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n
How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n
So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n
Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n
Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n
A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n
A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n
If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n
Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n
All the best!<\/p>\n\n\n\n
Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
In a DevOps model, non functional requirements will include the considerations for successful deployment in production.<\/p>\n\n\n\n This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
By then, code freezes would have happened and the Dev teams busy with updating documentation or creating Easter eggs.<\/p>\n\n\n\n In a DevOps model, non functional requirements will include the considerations for successful deployment in production.<\/p>\n\n\n\n This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Next, the rigor of testing and the stage in which this testing is done. Which, usually is towards the release event.<\/p>\n\n\n\n By then, code freezes would have happened and the Dev teams busy with updating documentation or creating Easter eggs.<\/p>\n\n\n\n In a DevOps model, non functional requirements will include the considerations for successful deployment in production.<\/p>\n\n\n\n This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
So, the first point to consider when computing the cost of testing should be against what is the desirable level of testing.<\/p>\n\n\n\n Next, the rigor of testing and the stage in which this testing is done. Which, usually is towards the release event.<\/p>\n\n\n\n By then, code freezes would have happened and the Dev teams busy with updating documentation or creating Easter eggs.<\/p>\n\n\n\n In a DevOps model, non functional requirements will include the considerations for successful deployment in production.<\/p>\n\n\n\n This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Even most critical applications today, may not be subject to the breadth and depth of testing needed to make them production quality and be reliable and available to meet business goals.<\/p>\n\n\n\n So, the first point to consider when computing the cost of testing should be against what is the desirable level of testing.<\/p>\n\n\n\n Next, the rigor of testing and the stage in which this testing is done. Which, usually is towards the release event.<\/p>\n\n\n\n By then, code freezes would have happened and the Dev teams busy with updating documentation or creating Easter eggs.<\/p>\n\n\n\n In a DevOps model, non functional requirements will include the considerations for successful deployment in production.<\/p>\n\n\n\n This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
By now, you would be getting the drift of what I am hinting at.<\/p>\n\n\n\n Even most critical applications today, may not be subject to the breadth and depth of testing needed to make them production quality and be reliable and available to meet business goals.<\/p>\n\n\n\n So, the first point to consider when computing the cost of testing should be against what is the desirable level of testing.<\/p>\n\n\n\n Next, the rigor of testing and the stage in which this testing is done. Which, usually is towards the release event.<\/p>\n\n\n\n By then, code freezes would have happened and the Dev teams busy with updating documentation or creating Easter eggs.<\/p>\n\n\n\n In a DevOps model, non functional requirements will include the considerations for successful deployment in production.<\/p>\n\n\n\n This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
The most popular development approaches among DevOps teams \u2013 Agile and Lean \u2013 do not define a clear role for an architect.<\/p>\n\n\n\n By now, you would be getting the drift of what I am hinting at.<\/p>\n\n\n\n Even most critical applications today, may not be subject to the breadth and depth of testing needed to make them production quality and be reliable and available to meet business goals.<\/p>\n\n\n\n So, the first point to consider when computing the cost of testing should be against what is the desirable level of testing.<\/p>\n\n\n\n Next, the rigor of testing and the stage in which this testing is done. Which, usually is towards the release event.<\/p>\n\n\n\n By then, code freezes would have happened and the Dev teams busy with updating documentation or creating Easter eggs.<\/p>\n\n\n\n In a DevOps model, non functional requirements will include the considerations for successful deployment in production.<\/p>\n\n\n\n This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
This can happen only when the architecture takes these requirements also into account.<\/p>\n\n\n\n The most popular development approaches among DevOps teams \u2013 Agile and Lean \u2013 do not define a clear role for an architect.<\/p>\n\n\n\n By now, you would be getting the drift of what I am hinting at.<\/p>\n\n\n\n Even most critical applications today, may not be subject to the breadth and depth of testing needed to make them production quality and be reliable and available to meet business goals.<\/p>\n\n\n\n So, the first point to consider when computing the cost of testing should be against what is the desirable level of testing.<\/p>\n\n\n\n Next, the rigor of testing and the stage in which this testing is done. Which, usually is towards the release event.<\/p>\n\n\n\n By then, code freezes would have happened and the Dev teams busy with updating documentation or creating Easter eggs.<\/p>\n\n\n\n In a DevOps model, non functional requirements will include the considerations for successful deployment in production.<\/p>\n\n\n\n This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
But then, as anyone who has developed software would know, the non-functional attributes need to be \u2018baked-in\u2019 and not bolted on.<\/p>\n\n\n\n This can happen only when the architecture takes these requirements also into account.<\/p>\n\n\n\n The most popular development approaches among DevOps teams \u2013 Agile and Lean \u2013 do not define a clear role for an architect.<\/p>\n\n\n\n By now, you would be getting the drift of what I am hinting at.<\/p>\n\n\n\n Even most critical applications today, may not be subject to the breadth and depth of testing needed to make them production quality and be reliable and available to meet business goals.<\/p>\n\n\n\n So, the first point to consider when computing the cost of testing should be against what is the desirable level of testing.<\/p>\n\n\n\n Next, the rigor of testing and the stage in which this testing is done. Which, usually is towards the release event.<\/p>\n\n\n\n By then, code freezes would have happened and the Dev teams busy with updating documentation or creating Easter eggs.<\/p>\n\n\n\n In a DevOps model, non functional requirements will include the considerations for successful deployment in production.<\/p>\n\n\n\n This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Even with all this, some aspects related to security ad vulnerability is rarely considered as part of the testing.<\/p>\n\n\n\n But then, as anyone who has developed software would know, the non-functional attributes need to be \u2018baked-in\u2019 and not bolted on.<\/p>\n\n\n\n This can happen only when the architecture takes these requirements also into account.<\/p>\n\n\n\n The most popular development approaches among DevOps teams \u2013 Agile and Lean \u2013 do not define a clear role for an architect.<\/p>\n\n\n\n By now, you would be getting the drift of what I am hinting at.<\/p>\n\n\n\n Even most critical applications today, may not be subject to the breadth and depth of testing needed to make them production quality and be reliable and available to meet business goals.<\/p>\n\n\n\n So, the first point to consider when computing the cost of testing should be against what is the desirable level of testing.<\/p>\n\n\n\n Next, the rigor of testing and the stage in which this testing is done. Which, usually is towards the release event.<\/p>\n\n\n\n By then, code freezes would have happened and the Dev teams busy with updating documentation or creating Easter eggs.<\/p>\n\n\n\n In a DevOps model, non functional requirements will include the considerations for successful deployment in production.<\/p>\n\n\n\n This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
The non functional testing is usually considered as a job for the specialists and is taken up in many cases as an after thought.<\/p>\n\n\n\n Even with all this, some aspects related to security ad vulnerability is rarely considered as part of the testing.<\/p>\n\n\n\n But then, as anyone who has developed software would know, the non-functional attributes need to be \u2018baked-in\u2019 and not bolted on.<\/p>\n\n\n\n This can happen only when the architecture takes these requirements also into account.<\/p>\n\n\n\n The most popular development approaches among DevOps teams \u2013 Agile and Lean \u2013 do not define a clear role for an architect.<\/p>\n\n\n\n By now, you would be getting the drift of what I am hinting at.<\/p>\n\n\n\n Even most critical applications today, may not be subject to the breadth and depth of testing needed to make them production quality and be reliable and available to meet business goals.<\/p>\n\n\n\n So, the first point to consider when computing the cost of testing should be against what is the desirable level of testing.<\/p>\n\n\n\n Next, the rigor of testing and the stage in which this testing is done. Which, usually is towards the release event.<\/p>\n\n\n\n By then, code freezes would have happened and the Dev teams busy with updating documentation or creating Easter eggs.<\/p>\n\n\n\n In a DevOps model, non functional requirements will include the considerations for successful deployment in production.<\/p>\n\n\n\n This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
But, has the limitation that a Dev influenced life cycle has.<\/p>\n\n\n\n The non functional testing is usually considered as a job for the specialists and is taken up in many cases as an after thought.<\/p>\n\n\n\n Even with all this, some aspects related to security ad vulnerability is rarely considered as part of the testing.<\/p>\n\n\n\n But then, as anyone who has developed software would know, the non-functional attributes need to be \u2018baked-in\u2019 and not bolted on.<\/p>\n\n\n\n This can happen only when the architecture takes these requirements also into account.<\/p>\n\n\n\n The most popular development approaches among DevOps teams \u2013 Agile and Lean \u2013 do not define a clear role for an architect.<\/p>\n\n\n\n By now, you would be getting the drift of what I am hinting at.<\/p>\n\n\n\n Even most critical applications today, may not be subject to the breadth and depth of testing needed to make them production quality and be reliable and available to meet business goals.<\/p>\n\n\n\n So, the first point to consider when computing the cost of testing should be against what is the desirable level of testing.<\/p>\n\n\n\n Next, the rigor of testing and the stage in which this testing is done. Which, usually is towards the release event.<\/p>\n\n\n\n By then, code freezes would have happened and the Dev teams busy with updating documentation or creating Easter eggs.<\/p>\n\n\n\n In a DevOps model, non functional requirements will include the considerations for successful deployment in production.<\/p>\n\n\n\n This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
This is good.<\/p>\n\n\n\n But, has the limitation that a Dev influenced life cycle has.<\/p>\n\n\n\n The non functional testing is usually considered as a job for the specialists and is taken up in many cases as an after thought.<\/p>\n\n\n\n Even with all this, some aspects related to security ad vulnerability is rarely considered as part of the testing.<\/p>\n\n\n\n But then, as anyone who has developed software would know, the non-functional attributes need to be \u2018baked-in\u2019 and not bolted on.<\/p>\n\n\n\n This can happen only when the architecture takes these requirements also into account.<\/p>\n\n\n\n The most popular development approaches among DevOps teams \u2013 Agile and Lean \u2013 do not define a clear role for an architect.<\/p>\n\n\n\n By now, you would be getting the drift of what I am hinting at.<\/p>\n\n\n\n Even most critical applications today, may not be subject to the breadth and depth of testing needed to make them production quality and be reliable and available to meet business goals.<\/p>\n\n\n\n So, the first point to consider when computing the cost of testing should be against what is the desirable level of testing.<\/p>\n\n\n\n Next, the rigor of testing and the stage in which this testing is done. Which, usually is towards the release event.<\/p>\n\n\n\n By then, code freezes would have happened and the Dev teams busy with updating documentation or creating Easter eggs.<\/p>\n\n\n\n In a DevOps model, non functional requirements will include the considerations for successful deployment in production.<\/p>\n\n\n\n This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Teams following the V-model would have a focus on Unit, Integration, System and Acceptance [also known as business function] tests.<\/p>\n\n\n\n This is good.<\/p>\n\n\n\n But, has the limitation that a Dev influenced life cycle has.<\/p>\n\n\n\n The non functional testing is usually considered as a job for the specialists and is taken up in many cases as an after thought.<\/p>\n\n\n\n Even with all this, some aspects related to security ad vulnerability is rarely considered as part of the testing.<\/p>\n\n\n\n But then, as anyone who has developed software would know, the non-functional attributes need to be \u2018baked-in\u2019 and not bolted on.<\/p>\n\n\n\n This can happen only when the architecture takes these requirements also into account.<\/p>\n\n\n\n The most popular development approaches among DevOps teams \u2013 Agile and Lean \u2013 do not define a clear role for an architect.<\/p>\n\n\n\n By now, you would be getting the drift of what I am hinting at.<\/p>\n\n\n\n Even most critical applications today, may not be subject to the breadth and depth of testing needed to make them production quality and be reliable and available to meet business goals.<\/p>\n\n\n\n So, the first point to consider when computing the cost of testing should be against what is the desirable level of testing.<\/p>\n\n\n\n Next, the rigor of testing and the stage in which this testing is done. Which, usually is towards the release event.<\/p>\n\n\n\n By then, code freezes would have happened and the Dev teams busy with updating documentation or creating Easter eggs.<\/p>\n\n\n\n In a DevOps model, non functional requirements will include the considerations for successful deployment in production.<\/p>\n\n\n\n This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Before answering that question, I would like to spend a few minutes on the types of testing that is usually recommended and what is done.<\/p>\n\n\n\n Teams following the V-model would have a focus on Unit, Integration, System and Acceptance [also known as business function] tests.<\/p>\n\n\n\n This is good.<\/p>\n\n\n\n But, has the limitation that a Dev influenced life cycle has.<\/p>\n\n\n\n The non functional testing is usually considered as a job for the specialists and is taken up in many cases as an after thought.<\/p>\n\n\n\n Even with all this, some aspects related to security ad vulnerability is rarely considered as part of the testing.<\/p>\n\n\n\n But then, as anyone who has developed software would know, the non-functional attributes need to be \u2018baked-in\u2019 and not bolted on.<\/p>\n\n\n\n This can happen only when the architecture takes these requirements also into account.<\/p>\n\n\n\n The most popular development approaches among DevOps teams \u2013 Agile and Lean \u2013 do not define a clear role for an architect.<\/p>\n\n\n\n By now, you would be getting the drift of what I am hinting at.<\/p>\n\n\n\n Even most critical applications today, may not be subject to the breadth and depth of testing needed to make them production quality and be reliable and available to meet business goals.<\/p>\n\n\n\n So, the first point to consider when computing the cost of testing should be against what is the desirable level of testing.<\/p>\n\n\n\n Next, the rigor of testing and the stage in which this testing is done. Which, usually is towards the release event.<\/p>\n\n\n\n By then, code freezes would have happened and the Dev teams busy with updating documentation or creating Easter eggs.<\/p>\n\n\n\n In a DevOps model, non functional requirements will include the considerations for successful deployment in production.<\/p>\n\n\n\n This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
One question that I get asked frequently is whether DevOps implies significantly higher costs for testing.<\/p>\n\n\n\n Before answering that question, I would like to spend a few minutes on the types of testing that is usually recommended and what is done.<\/p>\n\n\n\n Teams following the V-model would have a focus on Unit, Integration, System and Acceptance [also known as business function] tests.<\/p>\n\n\n\n This is good.<\/p>\n\n\n\n But, has the limitation that a Dev influenced life cycle has.<\/p>\n\n\n\n The non functional testing is usually considered as a job for the specialists and is taken up in many cases as an after thought.<\/p>\n\n\n\n Even with all this, some aspects related to security ad vulnerability is rarely considered as part of the testing.<\/p>\n\n\n\n But then, as anyone who has developed software would know, the non-functional attributes need to be \u2018baked-in\u2019 and not bolted on.<\/p>\n\n\n\n This can happen only when the architecture takes these requirements also into account.<\/p>\n\n\n\n The most popular development approaches among DevOps teams \u2013 Agile and Lean \u2013 do not define a clear role for an architect.<\/p>\n\n\n\n By now, you would be getting the drift of what I am hinting at.<\/p>\n\n\n\n Even most critical applications today, may not be subject to the breadth and depth of testing needed to make them production quality and be reliable and available to meet business goals.<\/p>\n\n\n\n So, the first point to consider when computing the cost of testing should be against what is the desirable level of testing.<\/p>\n\n\n\n Next, the rigor of testing and the stage in which this testing is done. Which, usually is towards the release event.<\/p>\n\n\n\n By then, code freezes would have happened and the Dev teams busy with updating documentation or creating Easter eggs.<\/p>\n\n\n\n In a DevOps model, non functional requirements will include the considerations for successful deployment in production.<\/p>\n\n\n\n This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Image courtesy <\/span>https:\/\/unsplash.com\/patryksobczak<\/span><\/a><\/p>\n","post_title":"How does one create a DevOps Culture?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-does-one-create-a-devops-culture","to_ping":"","pinged":"","post_modified":"2024-01-29 12:21:32","post_modified_gmt":"2024-01-29 12:21:32","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3119","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":3101,"post_author":"30","post_date":"2015-03-23 16:20:38","post_date_gmt":"2015-03-23 10:50:38","post_content":"\n One question that I get asked frequently is whether DevOps implies significantly higher costs for testing.<\/p>\n\n\n\n Before answering that question, I would like to spend a few minutes on the types of testing that is usually recommended and what is done.<\/p>\n\n\n\n Teams following the V-model would have a focus on Unit, Integration, System and Acceptance [also known as business function] tests.<\/p>\n\n\n\n This is good.<\/p>\n\n\n\n But, has the limitation that a Dev influenced life cycle has.<\/p>\n\n\n\n The non functional testing is usually considered as a job for the specialists and is taken up in many cases as an after thought.<\/p>\n\n\n\n Even with all this, some aspects related to security ad vulnerability is rarely considered as part of the testing.<\/p>\n\n\n\n But then, as anyone who has developed software would know, the non-functional attributes need to be \u2018baked-in\u2019 and not bolted on.<\/p>\n\n\n\n This can happen only when the architecture takes these requirements also into account.<\/p>\n\n\n\n The most popular development approaches among DevOps teams \u2013 Agile and Lean \u2013 do not define a clear role for an architect.<\/p>\n\n\n\n By now, you would be getting the drift of what I am hinting at.<\/p>\n\n\n\n Even most critical applications today, may not be subject to the breadth and depth of testing needed to make them production quality and be reliable and available to meet business goals.<\/p>\n\n\n\n So, the first point to consider when computing the cost of testing should be against what is the desirable level of testing.<\/p>\n\n\n\n Next, the rigor of testing and the stage in which this testing is done. Which, usually is towards the release event.<\/p>\n\n\n\n By then, code freezes would have happened and the Dev teams busy with updating documentation or creating Easter eggs.<\/p>\n\n\n\n In a DevOps model, non functional requirements will include the considerations for successful deployment in production.<\/p>\n\n\n\n This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
have been able to derive significant benefits in terms of productivity and quality of their deliverables.<\/p>\n\n\n\n Image courtesy <\/span>https:\/\/unsplash.com\/patryksobczak<\/span><\/a><\/p>\n","post_title":"How does one create a DevOps Culture?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-does-one-create-a-devops-culture","to_ping":"","pinged":"","post_modified":"2024-01-29 12:21:32","post_modified_gmt":"2024-01-29 12:21:32","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3119","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":3101,"post_author":"30","post_date":"2015-03-23 16:20:38","post_date_gmt":"2015-03-23 10:50:38","post_content":"\n One question that I get asked frequently is whether DevOps implies significantly higher costs for testing.<\/p>\n\n\n\n Before answering that question, I would like to spend a few minutes on the types of testing that is usually recommended and what is done.<\/p>\n\n\n\n Teams following the V-model would have a focus on Unit, Integration, System and Acceptance [also known as business function] tests.<\/p>\n\n\n\n This is good.<\/p>\n\n\n\n But, has the limitation that a Dev influenced life cycle has.<\/p>\n\n\n\n The non functional testing is usually considered as a job for the specialists and is taken up in many cases as an after thought.<\/p>\n\n\n\n Even with all this, some aspects related to security ad vulnerability is rarely considered as part of the testing.<\/p>\n\n\n\n But then, as anyone who has developed software would know, the non-functional attributes need to be \u2018baked-in\u2019 and not bolted on.<\/p>\n\n\n\n This can happen only when the architecture takes these requirements also into account.<\/p>\n\n\n\n The most popular development approaches among DevOps teams \u2013 Agile and Lean \u2013 do not define a clear role for an architect.<\/p>\n\n\n\n By now, you would be getting the drift of what I am hinting at.<\/p>\n\n\n\n Even most critical applications today, may not be subject to the breadth and depth of testing needed to make them production quality and be reliable and available to meet business goals.<\/p>\n\n\n\n So, the first point to consider when computing the cost of testing should be against what is the desirable level of testing.<\/p>\n\n\n\n Next, the rigor of testing and the stage in which this testing is done. Which, usually is towards the release event.<\/p>\n\n\n\n By then, code freezes would have happened and the Dev teams busy with updating documentation or creating Easter eggs.<\/p>\n\n\n\n In a DevOps model, non functional requirements will include the considerations for successful deployment in production.<\/p>\n\n\n\n This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
- acquired multiple skills, to be able to not only review and enrich others\u2019 work products, but also to step into some other member\u2019s shoes, if a need arises<\/p>\n\n\n\n have been able to derive significant benefits in terms of productivity and quality of their deliverables.<\/p>\n\n\n\n Image courtesy <\/span>https:\/\/unsplash.com\/patryksobczak<\/span><\/a><\/p>\n","post_title":"How does one create a DevOps Culture?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-does-one-create-a-devops-culture","to_ping":"","pinged":"","post_modified":"2024-01-29 12:21:32","post_modified_gmt":"2024-01-29 12:21:32","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3119","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":3101,"post_author":"30","post_date":"2015-03-23 16:20:38","post_date_gmt":"2015-03-23 10:50:38","post_content":"\n One question that I get asked frequently is whether DevOps implies significantly higher costs for testing.<\/p>\n\n\n\n Before answering that question, I would like to spend a few minutes on the types of testing that is usually recommended and what is done.<\/p>\n\n\n\n Teams following the V-model would have a focus on Unit, Integration, System and Acceptance [also known as business function] tests.<\/p>\n\n\n\n This is good.<\/p>\n\n\n\n But, has the limitation that a Dev influenced life cycle has.<\/p>\n\n\n\n The non functional testing is usually considered as a job for the specialists and is taken up in many cases as an after thought.<\/p>\n\n\n\n Even with all this, some aspects related to security ad vulnerability is rarely considered as part of the testing.<\/p>\n\n\n\n But then, as anyone who has developed software would know, the non-functional attributes need to be \u2018baked-in\u2019 and not bolted on.<\/p>\n\n\n\n This can happen only when the architecture takes these requirements also into account.<\/p>\n\n\n\n The most popular development approaches among DevOps teams \u2013 Agile and Lean \u2013 do not define a clear role for an architect.<\/p>\n\n\n\n By now, you would be getting the drift of what I am hinting at.<\/p>\n\n\n\n Even most critical applications today, may not be subject to the breadth and depth of testing needed to make them production quality and be reliable and available to meet business goals.<\/p>\n\n\n\n So, the first point to consider when computing the cost of testing should be against what is the desirable level of testing.<\/p>\n\n\n\n Next, the rigor of testing and the stage in which this testing is done. Which, usually is towards the release event.<\/p>\n\n\n\n By then, code freezes would have happened and the Dev teams busy with updating documentation or creating Easter eggs.<\/p>\n\n\n\n In a DevOps model, non functional requirements will include the considerations for successful deployment in production.<\/p>\n\n\n\n This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
- organized themselves into feature crews<\/p>\n\n\n\n - acquired multiple skills, to be able to not only review and enrich others\u2019 work products, but also to step into some other member\u2019s shoes, if a need arises<\/p>\n\n\n\n have been able to derive significant benefits in terms of productivity and quality of their deliverables.<\/p>\n\n\n\n Image courtesy <\/span>https:\/\/unsplash.com\/patryksobczak<\/span><\/a><\/p>\n","post_title":"How does one create a DevOps Culture?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-does-one-create-a-devops-culture","to_ping":"","pinged":"","post_modified":"2024-01-29 12:21:32","post_modified_gmt":"2024-01-29 12:21:32","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3119","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":3101,"post_author":"30","post_date":"2015-03-23 16:20:38","post_date_gmt":"2015-03-23 10:50:38","post_content":"\n One question that I get asked frequently is whether DevOps implies significantly higher costs for testing.<\/p>\n\n\n\n Before answering that question, I would like to spend a few minutes on the types of testing that is usually recommended and what is done.<\/p>\n\n\n\n Teams following the V-model would have a focus on Unit, Integration, System and Acceptance [also known as business function] tests.<\/p>\n\n\n\n This is good.<\/p>\n\n\n\n But, has the limitation that a Dev influenced life cycle has.<\/p>\n\n\n\n The non functional testing is usually considered as a job for the specialists and is taken up in many cases as an after thought.<\/p>\n\n\n\n Even with all this, some aspects related to security ad vulnerability is rarely considered as part of the testing.<\/p>\n\n\n\n But then, as anyone who has developed software would know, the non-functional attributes need to be \u2018baked-in\u2019 and not bolted on.<\/p>\n\n\n\n This can happen only when the architecture takes these requirements also into account.<\/p>\n\n\n\n The most popular development approaches among DevOps teams \u2013 Agile and Lean \u2013 do not define a clear role for an architect.<\/p>\n\n\n\n By now, you would be getting the drift of what I am hinting at.<\/p>\n\n\n\n Even most critical applications today, may not be subject to the breadth and depth of testing needed to make them production quality and be reliable and available to meet business goals.<\/p>\n\n\n\n So, the first point to consider when computing the cost of testing should be against what is the desirable level of testing.<\/p>\n\n\n\n Next, the rigor of testing and the stage in which this testing is done. Which, usually is towards the release event.<\/p>\n\n\n\n By then, code freezes would have happened and the Dev teams busy with updating documentation or creating Easter eggs.<\/p>\n\n\n\n In a DevOps model, non functional requirements will include the considerations for successful deployment in production.<\/p>\n\n\n\n This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
- a high level of trust in each other and leadership<\/p>\n\n\n\n - organized themselves into feature crews<\/p>\n\n\n\n - acquired multiple skills, to be able to not only review and enrich others\u2019 work products, but also to step into some other member\u2019s shoes, if a need arises<\/p>\n\n\n\n have been able to derive significant benefits in terms of productivity and quality of their deliverables.<\/p>\n\n\n\n Image courtesy <\/span>https:\/\/unsplash.com\/patryksobczak<\/span><\/a><\/p>\n","post_title":"How does one create a DevOps Culture?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-does-one-create-a-devops-culture","to_ping":"","pinged":"","post_modified":"2024-01-29 12:21:32","post_modified_gmt":"2024-01-29 12:21:32","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3119","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":3101,"post_author":"30","post_date":"2015-03-23 16:20:38","post_date_gmt":"2015-03-23 10:50:38","post_content":"\n One question that I get asked frequently is whether DevOps implies significantly higher costs for testing.<\/p>\n\n\n\n Before answering that question, I would like to spend a few minutes on the types of testing that is usually recommended and what is done.<\/p>\n\n\n\n Teams following the V-model would have a focus on Unit, Integration, System and Acceptance [also known as business function] tests.<\/p>\n\n\n\n This is good.<\/p>\n\n\n\n But, has the limitation that a Dev influenced life cycle has.<\/p>\n\n\n\n The non functional testing is usually considered as a job for the specialists and is taken up in many cases as an after thought.<\/p>\n\n\n\n Even with all this, some aspects related to security ad vulnerability is rarely considered as part of the testing.<\/p>\n\n\n\n But then, as anyone who has developed software would know, the non-functional attributes need to be \u2018baked-in\u2019 and not bolted on.<\/p>\n\n\n\n This can happen only when the architecture takes these requirements also into account.<\/p>\n\n\n\n The most popular development approaches among DevOps teams \u2013 Agile and Lean \u2013 do not define a clear role for an architect.<\/p>\n\n\n\n By now, you would be getting the drift of what I am hinting at.<\/p>\n\n\n\n Even most critical applications today, may not be subject to the breadth and depth of testing needed to make them production quality and be reliable and available to meet business goals.<\/p>\n\n\n\n So, the first point to consider when computing the cost of testing should be against what is the desirable level of testing.<\/p>\n\n\n\n Next, the rigor of testing and the stage in which this testing is done. Which, usually is towards the release event.<\/p>\n\n\n\n By then, code freezes would have happened and the Dev teams busy with updating documentation or creating Easter eggs.<\/p>\n\n\n\n In a DevOps model, non functional requirements will include the considerations for successful deployment in production.<\/p>\n\n\n\n This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
- a shared goal<\/p>\n\n\n\n - a high level of trust in each other and leadership<\/p>\n\n\n\n - organized themselves into feature crews<\/p>\n\n\n\n - acquired multiple skills, to be able to not only review and enrich others\u2019 work products, but also to step into some other member\u2019s shoes, if a need arises<\/p>\n\n\n\n have been able to derive significant benefits in terms of productivity and quality of their deliverables.<\/p>\n\n\n\n Image courtesy <\/span>https:\/\/unsplash.com\/patryksobczak<\/span><\/a><\/p>\n","post_title":"How does one create a DevOps Culture?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-does-one-create-a-devops-culture","to_ping":"","pinged":"","post_modified":"2024-01-29 12:21:32","post_modified_gmt":"2024-01-29 12:21:32","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3119","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":3101,"post_author":"30","post_date":"2015-03-23 16:20:38","post_date_gmt":"2015-03-23 10:50:38","post_content":"\n One question that I get asked frequently is whether DevOps implies significantly higher costs for testing.<\/p>\n\n\n\n Before answering that question, I would like to spend a few minutes on the types of testing that is usually recommended and what is done.<\/p>\n\n\n\n Teams following the V-model would have a focus on Unit, Integration, System and Acceptance [also known as business function] tests.<\/p>\n\n\n\n This is good.<\/p>\n\n\n\n But, has the limitation that a Dev influenced life cycle has.<\/p>\n\n\n\n The non functional testing is usually considered as a job for the specialists and is taken up in many cases as an after thought.<\/p>\n\n\n\n Even with all this, some aspects related to security ad vulnerability is rarely considered as part of the testing.<\/p>\n\n\n\n But then, as anyone who has developed software would know, the non-functional attributes need to be \u2018baked-in\u2019 and not bolted on.<\/p>\n\n\n\n This can happen only when the architecture takes these requirements also into account.<\/p>\n\n\n\n The most popular development approaches among DevOps teams \u2013 Agile and Lean \u2013 do not define a clear role for an architect.<\/p>\n\n\n\n By now, you would be getting the drift of what I am hinting at.<\/p>\n\n\n\n Even most critical applications today, may not be subject to the breadth and depth of testing needed to make them production quality and be reliable and available to meet business goals.<\/p>\n\n\n\n So, the first point to consider when computing the cost of testing should be against what is the desirable level of testing.<\/p>\n\n\n\n Next, the rigor of testing and the stage in which this testing is done. Which, usually is towards the release event.<\/p>\n\n\n\n By then, code freezes would have happened and the Dev teams busy with updating documentation or creating Easter eggs.<\/p>\n\n\n\n In a DevOps model, non functional requirements will include the considerations for successful deployment in production.<\/p>\n\n\n\n This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
While the above model sounds very idealistic, we see teams where the members have<\/p>\n\n\n\n - a shared goal<\/p>\n\n\n\n - a high level of trust in each other and leadership<\/p>\n\n\n\n - organized themselves into feature crews<\/p>\n\n\n\n - acquired multiple skills, to be able to not only review and enrich others\u2019 work products, but also to step into some other member\u2019s shoes, if a need arises<\/p>\n\n\n\n have been able to derive significant benefits in terms of productivity and quality of their deliverables.<\/p>\n\n\n\n Image courtesy <\/span>https:\/\/unsplash.com\/patryksobczak<\/span><\/a><\/p>\n","post_title":"How does one create a DevOps Culture?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-does-one-create-a-devops-culture","to_ping":"","pinged":"","post_modified":"2024-01-29 12:21:32","post_modified_gmt":"2024-01-29 12:21:32","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3119","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":3101,"post_author":"30","post_date":"2015-03-23 16:20:38","post_date_gmt":"2015-03-23 10:50:38","post_content":"\n One question that I get asked frequently is whether DevOps implies significantly higher costs for testing.<\/p>\n\n\n\n Before answering that question, I would like to spend a few minutes on the types of testing that is usually recommended and what is done.<\/p>\n\n\n\n Teams following the V-model would have a focus on Unit, Integration, System and Acceptance [also known as business function] tests.<\/p>\n\n\n\n This is good.<\/p>\n\n\n\n But, has the limitation that a Dev influenced life cycle has.<\/p>\n\n\n\n The non functional testing is usually considered as a job for the specialists and is taken up in many cases as an after thought.<\/p>\n\n\n\n Even with all this, some aspects related to security ad vulnerability is rarely considered as part of the testing.<\/p>\n\n\n\n But then, as anyone who has developed software would know, the non-functional attributes need to be \u2018baked-in\u2019 and not bolted on.<\/p>\n\n\n\n This can happen only when the architecture takes these requirements also into account.<\/p>\n\n\n\n The most popular development approaches among DevOps teams \u2013 Agile and Lean \u2013 do not define a clear role for an architect.<\/p>\n\n\n\n By now, you would be getting the drift of what I am hinting at.<\/p>\n\n\n\n Even most critical applications today, may not be subject to the breadth and depth of testing needed to make them production quality and be reliable and available to meet business goals.<\/p>\n\n\n\n So, the first point to consider when computing the cost of testing should be against what is the desirable level of testing.<\/p>\n\n\n\n Next, the rigor of testing and the stage in which this testing is done. Which, usually is towards the release event.<\/p>\n\n\n\n By then, code freezes would have happened and the Dev teams busy with updating documentation or creating Easter eggs.<\/p>\n\n\n\n In a DevOps model, non functional requirements will include the considerations for successful deployment in production.<\/p>\n\n\n\n This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
And so on.<\/p>\n\n\n\n While the above model sounds very idealistic, we see teams where the members have<\/p>\n\n\n\n - a shared goal<\/p>\n\n\n\n - a high level of trust in each other and leadership<\/p>\n\n\n\n - organized themselves into feature crews<\/p>\n\n\n\n - acquired multiple skills, to be able to not only review and enrich others\u2019 work products, but also to step into some other member\u2019s shoes, if a need arises<\/p>\n\n\n\n have been able to derive significant benefits in terms of productivity and quality of their deliverables.<\/p>\n\n\n\n Image courtesy <\/span>https:\/\/unsplash.com\/patryksobczak<\/span><\/a><\/p>\n","post_title":"How does one create a DevOps Culture?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-does-one-create-a-devops-culture","to_ping":"","pinged":"","post_modified":"2024-01-29 12:21:32","post_modified_gmt":"2024-01-29 12:21:32","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3119","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":3101,"post_author":"30","post_date":"2015-03-23 16:20:38","post_date_gmt":"2015-03-23 10:50:38","post_content":"\n One question that I get asked frequently is whether DevOps implies significantly higher costs for testing.<\/p>\n\n\n\n Before answering that question, I would like to spend a few minutes on the types of testing that is usually recommended and what is done.<\/p>\n\n\n\n Teams following the V-model would have a focus on Unit, Integration, System and Acceptance [also known as business function] tests.<\/p>\n\n\n\n This is good.<\/p>\n\n\n\n But, has the limitation that a Dev influenced life cycle has.<\/p>\n\n\n\n The non functional testing is usually considered as a job for the specialists and is taken up in many cases as an after thought.<\/p>\n\n\n\n Even with all this, some aspects related to security ad vulnerability is rarely considered as part of the testing.<\/p>\n\n\n\n But then, as anyone who has developed software would know, the non-functional attributes need to be \u2018baked-in\u2019 and not bolted on.<\/p>\n\n\n\n This can happen only when the architecture takes these requirements also into account.<\/p>\n\n\n\n The most popular development approaches among DevOps teams \u2013 Agile and Lean \u2013 do not define a clear role for an architect.<\/p>\n\n\n\n By now, you would be getting the drift of what I am hinting at.<\/p>\n\n\n\n Even most critical applications today, may not be subject to the breadth and depth of testing needed to make them production quality and be reliable and available to meet business goals.<\/p>\n\n\n\n So, the first point to consider when computing the cost of testing should be against what is the desirable level of testing.<\/p>\n\n\n\n Next, the rigor of testing and the stage in which this testing is done. Which, usually is towards the release event.<\/p>\n\n\n\n By then, code freezes would have happened and the Dev teams busy with updating documentation or creating Easter eggs.<\/p>\n\n\n\n In a DevOps model, non functional requirements will include the considerations for successful deployment in production.<\/p>\n\n\n\n This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
From providing answers and directions to enabling teams to explore, analyze and support their solution deployment.<\/p>\n\n\n\n And so on.<\/p>\n\n\n\n While the above model sounds very idealistic, we see teams where the members have<\/p>\n\n\n\n - a shared goal<\/p>\n\n\n\n - a high level of trust in each other and leadership<\/p>\n\n\n\n - organized themselves into feature crews<\/p>\n\n\n\n - acquired multiple skills, to be able to not only review and enrich others\u2019 work products, but also to step into some other member\u2019s shoes, if a need arises<\/p>\n\n\n\n have been able to derive significant benefits in terms of productivity and quality of their deliverables.<\/p>\n\n\n\n Image courtesy <\/span>https:\/\/unsplash.com\/patryksobczak<\/span><\/a><\/p>\n","post_title":"How does one create a DevOps Culture?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-does-one-create-a-devops-culture","to_ping":"","pinged":"","post_modified":"2024-01-29 12:21:32","post_modified_gmt":"2024-01-29 12:21:32","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3119","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":3101,"post_author":"30","post_date":"2015-03-23 16:20:38","post_date_gmt":"2015-03-23 10:50:38","post_content":"\n One question that I get asked frequently is whether DevOps implies significantly higher costs for testing.<\/p>\n\n\n\n Before answering that question, I would like to spend a few minutes on the types of testing that is usually recommended and what is done.<\/p>\n\n\n\n Teams following the V-model would have a focus on Unit, Integration, System and Acceptance [also known as business function] tests.<\/p>\n\n\n\n This is good.<\/p>\n\n\n\n But, has the limitation that a Dev influenced life cycle has.<\/p>\n\n\n\n The non functional testing is usually considered as a job for the specialists and is taken up in many cases as an after thought.<\/p>\n\n\n\n Even with all this, some aspects related to security ad vulnerability is rarely considered as part of the testing.<\/p>\n\n\n\n But then, as anyone who has developed software would know, the non-functional attributes need to be \u2018baked-in\u2019 and not bolted on.<\/p>\n\n\n\n This can happen only when the architecture takes these requirements also into account.<\/p>\n\n\n\n The most popular development approaches among DevOps teams \u2013 Agile and Lean \u2013 do not define a clear role for an architect.<\/p>\n\n\n\n By now, you would be getting the drift of what I am hinting at.<\/p>\n\n\n\n Even most critical applications today, may not be subject to the breadth and depth of testing needed to make them production quality and be reliable and available to meet business goals.<\/p>\n\n\n\n So, the first point to consider when computing the cost of testing should be against what is the desirable level of testing.<\/p>\n\n\n\n Next, the rigor of testing and the stage in which this testing is done. Which, usually is towards the release event.<\/p>\n\n\n\n By then, code freezes would have happened and the Dev teams busy with updating documentation or creating Easter eggs.<\/p>\n\n\n\n In a DevOps model, non functional requirements will include the considerations for successful deployment in production.<\/p>\n\n\n\n This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
From being command-and-control managers to inspiring and guiding leaders.<\/p>\n\n\n\n From providing answers and directions to enabling teams to explore, analyze and support their solution deployment.<\/p>\n\n\n\n And so on.<\/p>\n\n\n\n While the above model sounds very idealistic, we see teams where the members have<\/p>\n\n\n\n - a shared goal<\/p>\n\n\n\n - a high level of trust in each other and leadership<\/p>\n\n\n\n - organized themselves into feature crews<\/p>\n\n\n\n - acquired multiple skills, to be able to not only review and enrich others\u2019 work products, but also to step into some other member\u2019s shoes, if a need arises<\/p>\n\n\n\n have been able to derive significant benefits in terms of productivity and quality of their deliverables.<\/p>\n\n\n\n Image courtesy <\/span>https:\/\/unsplash.com\/patryksobczak<\/span><\/a><\/p>\n","post_title":"How does one create a DevOps Culture?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-does-one-create-a-devops-culture","to_ping":"","pinged":"","post_modified":"2024-01-29 12:21:32","post_modified_gmt":"2024-01-29 12:21:32","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3119","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":3101,"post_author":"30","post_date":"2015-03-23 16:20:38","post_date_gmt":"2015-03-23 10:50:38","post_content":"\n One question that I get asked frequently is whether DevOps implies significantly higher costs for testing.<\/p>\n\n\n\n Before answering that question, I would like to spend a few minutes on the types of testing that is usually recommended and what is done.<\/p>\n\n\n\n Teams following the V-model would have a focus on Unit, Integration, System and Acceptance [also known as business function] tests.<\/p>\n\n\n\n This is good.<\/p>\n\n\n\n But, has the limitation that a Dev influenced life cycle has.<\/p>\n\n\n\n The non functional testing is usually considered as a job for the specialists and is taken up in many cases as an after thought.<\/p>\n\n\n\n Even with all this, some aspects related to security ad vulnerability is rarely considered as part of the testing.<\/p>\n\n\n\n But then, as anyone who has developed software would know, the non-functional attributes need to be \u2018baked-in\u2019 and not bolted on.<\/p>\n\n\n\n This can happen only when the architecture takes these requirements also into account.<\/p>\n\n\n\n The most popular development approaches among DevOps teams \u2013 Agile and Lean \u2013 do not define a clear role for an architect.<\/p>\n\n\n\n By now, you would be getting the drift of what I am hinting at.<\/p>\n\n\n\n Even most critical applications today, may not be subject to the breadth and depth of testing needed to make them production quality and be reliable and available to meet business goals.<\/p>\n\n\n\n So, the first point to consider when computing the cost of testing should be against what is the desirable level of testing.<\/p>\n\n\n\n Next, the rigor of testing and the stage in which this testing is done. Which, usually is towards the release event.<\/p>\n\n\n\n By then, code freezes would have happened and the Dev teams busy with updating documentation or creating Easter eggs.<\/p>\n\n\n\n In a DevOps model, non functional requirements will include the considerations for successful deployment in production.<\/p>\n\n\n\n This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
From being individual contributors to becoming members of teams that deliver full functions or features, fully tested and ready for deployment into production.<\/p>\n\n\n\n From being command-and-control managers to inspiring and guiding leaders.<\/p>\n\n\n\n From providing answers and directions to enabling teams to explore, analyze and support their solution deployment.<\/p>\n\n\n\n And so on.<\/p>\n\n\n\n While the above model sounds very idealistic, we see teams where the members have<\/p>\n\n\n\n - a shared goal<\/p>\n\n\n\n - a high level of trust in each other and leadership<\/p>\n\n\n\n - organized themselves into feature crews<\/p>\n\n\n\n - acquired multiple skills, to be able to not only review and enrich others\u2019 work products, but also to step into some other member\u2019s shoes, if a need arises<\/p>\n\n\n\n have been able to derive significant benefits in terms of productivity and quality of their deliverables.<\/p>\n\n\n\n Image courtesy <\/span>https:\/\/unsplash.com\/patryksobczak<\/span><\/a><\/p>\n","post_title":"How does one create a DevOps Culture?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-does-one-create-a-devops-culture","to_ping":"","pinged":"","post_modified":"2024-01-29 12:21:32","post_modified_gmt":"2024-01-29 12:21:32","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3119","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":3101,"post_author":"30","post_date":"2015-03-23 16:20:38","post_date_gmt":"2015-03-23 10:50:38","post_content":"\n One question that I get asked frequently is whether DevOps implies significantly higher costs for testing.<\/p>\n\n\n\n Before answering that question, I would like to spend a few minutes on the types of testing that is usually recommended and what is done.<\/p>\n\n\n\n Teams following the V-model would have a focus on Unit, Integration, System and Acceptance [also known as business function] tests.<\/p>\n\n\n\n This is good.<\/p>\n\n\n\n But, has the limitation that a Dev influenced life cycle has.<\/p>\n\n\n\n The non functional testing is usually considered as a job for the specialists and is taken up in many cases as an after thought.<\/p>\n\n\n\n Even with all this, some aspects related to security ad vulnerability is rarely considered as part of the testing.<\/p>\n\n\n\n But then, as anyone who has developed software would know, the non-functional attributes need to be \u2018baked-in\u2019 and not bolted on.<\/p>\n\n\n\n This can happen only when the architecture takes these requirements also into account.<\/p>\n\n\n\n The most popular development approaches among DevOps teams \u2013 Agile and Lean \u2013 do not define a clear role for an architect.<\/p>\n\n\n\n By now, you would be getting the drift of what I am hinting at.<\/p>\n\n\n\n Even most critical applications today, may not be subject to the breadth and depth of testing needed to make them production quality and be reliable and available to meet business goals.<\/p>\n\n\n\n So, the first point to consider when computing the cost of testing should be against what is the desirable level of testing.<\/p>\n\n\n\n Next, the rigor of testing and the stage in which this testing is done. Which, usually is towards the release event.<\/p>\n\n\n\n By then, code freezes would have happened and the Dev teams busy with updating documentation or creating Easter eggs.<\/p>\n\n\n\n In a DevOps model, non functional requirements will include the considerations for successful deployment in production.<\/p>\n\n\n\n This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n In extreme cases, it is continuous deployment.<\/p>\n\n\n\n In order to achieve this \u2013 or even progress towards this, the underlying application as well as the portfolio architecture should be aware of such evolution.<\/p>\n\n\n\n The discipline of Enterprise Architecture recommends structured approaches to layer the solutions and ensure that multiple perspectives are addressed adequately.<\/p>\n\n\n\n Building applications today is a lot more complex even for enterprise internal applications, as they need to cater to the expectations of the changing profiles of the workforce, changing patterns of technology adoption \u2013 including the trend to BYOD (Bring your own device) as well as the need to integrate information from multiple sources to infer patterns for better decision making.<\/p>\n\n\n\n Agile approaches have helped development teams become more productive and engage the customers throughout the life cycle.<\/p>\n\n\n\n One of the common misconceptions about Agile is that there is no need for spending time on architecting the solution.<\/p>\n\n\n\n That is not correct. While some portions of the detailed architecture [or design] could evolve over time, the core non-functional requirements need to be considered in making choices on technology, design patterns etc.<\/p>\n\n\n\n Additional aspects related to the application being fault-tolerant, or, in more advanced implementations, self-healing etc. will require run time tracking and logging of application behavior and analysis of causes that can be rectified.<\/p>\n\n\n\n In the Ops side, the concept of a KEDB [known error database] has delivered significant benefits in making the first level support more productive \u2013 leading directly to increased user satisfaction on quality closures of their requests.<\/p>\n\n\n\n For the software to also benefit from this, new technologies, including AI techniques need to be considered.<\/p>\n\n\n\n Agile approaches recommend that managers unlearn some of the techniques of command and control and learn approaches to let go and lead teams. Similarly, application architects need to unlearn some of their practices and transcend to enterprise views.<\/p>\n\n\n\n These views must necessarily include the run time or production perspectives also.<\/p>\n\n\n\n PM Power has mapped the elements of TOGAF to various aspects of a DevOps view of enterprise applications<\/a>.<\/p>\n\n\n\n To conclude, I would like to say that a DevOps journey should start with an analysis of the enterprise architecture and be based on a flexible foundation so that the benefits of rapid and frequent deployments can indeed bring in benefits to the business users.<\/p>\n","post_title":"Role of Architecture in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-architecture-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:26:20","post_modified_gmt":"2024-01-29 12:26:20","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2619","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":1662,"post_author":"30","post_date":"2014-11-16 21:30:44","post_date_gmt":"2014-11-16 16:00:44","post_content":"\n Image source : blogs.msdn.com\u00a0 \/\/ https:\/\/www.linkedin.com\/in\/adriancockcroft<\/p>\n\n\n\n One question that I get asked frequently, when talking about DevOps is: where do I begin?<\/p>\n\n\n\n A follow-up question is \u2013 Can you recommend any checklist or set of steps to get into DevOps?<\/p>\n\n\n\n My short answer to that question is: start where you can show some short term improvements.<\/p>\n\n\n\n How does one identify that? In most organizations, one neglected area is IT operations. Even though there are models and techniques \u2013 such as ITIL or Lean, Six Sigma etc, it is not very common for these to be integrated with the ways of working of the organization.<\/p>\n\n\n\n So, it is best if one can start with the operations area and look for some quick wins. The KEDB for those implementing ITIL or the log of tickets for others along with runbooks for applications can provide a lot of insight into identifying the top time and effort consuming activities that can either be reduced or eliminated. In doing this, automation of activities, self service capabilities for users, enhancement of applications could be considered for improvements. For activities that are repetitive or those that need to scale across the server farms, as well as the incoming quality gate activities for assessing the application quality and stability through testing in an integrated manner \u2013 consider automation.<\/p>\n\n\n\n Step 2 could be to look at the handoff interfaces within the IT ops groups \u2013 sometimes the verticals or micro verticals within Ops such as network, security, database etc and study the flow of typical transactions - ranked by either the priority \/ impact or the frequency of occurrence. This would help in reducing any wait times within the IT Ops flows.<\/p>\n\n\n\n Step 3 could be to extend this into the interfaces with external teams \u2013 particularly the development or engineering teams. While the ultimate goal of DevOps would be to eliminate the barriers between Dev and Ops and create a collaboration and mutually supporting team, the first baby step could be to create a mutual understanding and awareness of each other\u2019s activities and the constraints that they operate under. This will help in creating or improving the empathy across the two groups. This will be very useful to accelerate the collective ownership of the business impact created by the IT solutions.<\/p>\n\n\n\n A related initiative to step 3 would be to assess the readiness of the dev teams to adopt agile values and principles in their working models. For organizations and teams that are just starting out on an agile journey, it will be very good to take guidance from an experienced coach, either from within the organization or from outside.<\/p>\n\n\n\n A common thumb rule for all the above steps is to first review and simplify the current processes and practices before automating.<\/p>\n\n\n\n If you have read this far, it would mean that you have a serious intention to internalize the basics of DevOps. More on that in a later post.<\/p>\n\n\n\n Do share the improved practices that you have implemented successfully. They could be of relevance to many of your peers who have also embarked on their DevOps journey.<\/p>\n\n\n\n All the best!<\/p>\n\n\n\n Image source: blogs.msdn.com<\/p>\n","post_title":"How to begin a DevOps journey?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-to-begin-a-devops-journey","to_ping":"","pinged":"","post_modified":"2024-09-13 20:15:11","post_modified_gmt":"2024-09-13 14:45:11","post_content_filtered":"","post_parent":0,"guid":"http:\/\/blogs.pm-powerconsulting.com\/blogs\/?p=1662","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":2},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
The key enabler for such a transformation is a transformation of every individual.<\/p>\n\n\n\n From being individual contributors to becoming members of teams that deliver full functions or features, fully tested and ready for deployment into production.<\/p>\n\n\n\n From being command-and-control managers to inspiring and guiding leaders.<\/p>\n\n\n\n From providing answers and directions to enabling teams to explore, analyze and support their solution deployment.<\/p>\n\n\n\n And so on.<\/p>\n\n\n\n While the above model sounds very idealistic, we see teams where the members have<\/p>\n\n\n\n - a shared goal<\/p>\n\n\n\n - a high level of trust in each other and leadership<\/p>\n\n\n\n - organized themselves into feature crews<\/p>\n\n\n\n - acquired multiple skills, to be able to not only review and enrich others\u2019 work products, but also to step into some other member\u2019s shoes, if a need arises<\/p>\n\n\n\n have been able to derive significant benefits in terms of productivity and quality of their deliverables.<\/p>\n\n\n\n Image courtesy <\/span>https:\/\/unsplash.com\/patryksobczak<\/span><\/a><\/p>\n","post_title":"How does one create a DevOps Culture?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"how-does-one-create-a-devops-culture","to_ping":"","pinged":"","post_modified":"2024-01-29 12:21:32","post_modified_gmt":"2024-01-29 12:21:32","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3119","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":3101,"post_author":"30","post_date":"2015-03-23 16:20:38","post_date_gmt":"2015-03-23 10:50:38","post_content":"\n One question that I get asked frequently is whether DevOps implies significantly higher costs for testing.<\/p>\n\n\n\n Before answering that question, I would like to spend a few minutes on the types of testing that is usually recommended and what is done.<\/p>\n\n\n\n Teams following the V-model would have a focus on Unit, Integration, System and Acceptance [also known as business function] tests.<\/p>\n\n\n\n This is good.<\/p>\n\n\n\n But, has the limitation that a Dev influenced life cycle has.<\/p>\n\n\n\n The non functional testing is usually considered as a job for the specialists and is taken up in many cases as an after thought.<\/p>\n\n\n\n Even with all this, some aspects related to security ad vulnerability is rarely considered as part of the testing.<\/p>\n\n\n\n But then, as anyone who has developed software would know, the non-functional attributes need to be \u2018baked-in\u2019 and not bolted on.<\/p>\n\n\n\n This can happen only when the architecture takes these requirements also into account.<\/p>\n\n\n\n The most popular development approaches among DevOps teams \u2013 Agile and Lean \u2013 do not define a clear role for an architect.<\/p>\n\n\n\n By now, you would be getting the drift of what I am hinting at.<\/p>\n\n\n\n Even most critical applications today, may not be subject to the breadth and depth of testing needed to make them production quality and be reliable and available to meet business goals.<\/p>\n\n\n\n So, the first point to consider when computing the cost of testing should be against what is the desirable level of testing.<\/p>\n\n\n\n Next, the rigor of testing and the stage in which this testing is done. Which, usually is towards the release event.<\/p>\n\n\n\n By then, code freezes would have happened and the Dev teams busy with updating documentation or creating Easter eggs.<\/p>\n\n\n\n In a DevOps model, non functional requirements will include the considerations for successful deployment in production.<\/p>\n\n\n\n This will mean that the application \u2013 or enterprise \u2013 architecture should take this into account as well, right from the beginning.<\/p>\n\n\n\n and on a continued basis..<\/p>\n\n\n\n What continuous delivery [or deployment] will necessitate is that every increment that goes to production is fully tested.<\/p>\n\n\n\n Obviously this will mean that testing also has to be continuous.<\/p>\n\n\n\n Thankfully, approaches, techniques and enabling technologies and solutions make this a little bit easier, particularly when tests need to be repeated.<\/p>\n\n\n\n Another significant approach that has proven to be beneficial is the left-shift model.<\/p>\n\n\n\n Moving testing to as early in the life cycle as possible \u2013 either by including these criteria as part of the definition of DONE in earlier stages of development, or by running automated tests on every build.. \u2013 not only reduced the cost of testing, but also ensures that critical components are tested multiple times, thereby reducing the risk of failure.<\/p>\n\n\n\n Another requirement of a successful DevOps implementation is to be able to rollback gracefully.<\/p>\n\n\n\n Even with a lot of care in testing, sometimes, incompatibilities in the environment of apps sometimes leads to instability. Rollbacks help minimize the damage to production stability.<\/p>\n\n\n\n Now, to the question that triggered this post.<\/p>\n\n\n\n Yea, there are costs one needs to consider \u2013 for automating testing, to include testable architecture as a way of development etc.<\/p>\n\n\n\n But a fairer comparison would be to look at the cost \/ benefit.<\/p>\n\n\n\n As teams aim to deliver continuous business value, delivering it right every time becomes an extremely important requirement.<\/p>\n\n\n\n Based on the case studies that are documented and freely available on the web, paying attention to testing from the beginning, taking the Ops requirements also into the architecture have paid satisfying dividends.<\/p>\n\n\n\n When one considers the diversity in the devices used to access the applications, the complexity in testing becomes even higher.<\/p>\n\n\n\n The session on testing and mobility in the Decoding DevOps conference would touch upon many of these aspects and also be a platform for some of the practitioners to share their experiences.<\/p>\n","post_title":"Role of testing in DevOps","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-of-testing-in-devops","to_ping":"","pinged":"","post_modified":"2024-01-29 12:22:54","post_modified_gmt":"2024-01-29 12:22:54","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=3101","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2619,"post_author":"30","post_date":"2015-02-02 12:30:45","post_date_gmt":"2015-02-02 07:00:45","post_content":"\n<\/p>\n\n\n\n<\/p>\n\n\n\n<\/p>\n\n\n\n<\/p>\n\n\n\n<\/p>\n\n\n\n<\/p>\n\n\n\n<\/p>\n\n\n\n<\/p>\n\n\n\n<\/p>\n\n\n\n<\/p>\n\n\n\n<\/p>\n\n\n\n<\/p>\n\n\n\n<\/p>\n\n\n\n![\"architecture](\"https:\/\/pm-powerconsulting.com\/wp-content\/uploads\/2015\/02\/architecture-blog-image_thumb.jpg\" "\\"architecture")
<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n<\/a> DevOps approaches highlight the value of early and frequent releases into production.<\/p>\n\n\n\n<\/p>\n\n\n\n
