Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n
To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n
Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n
To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nWhen all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n
The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n
Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n
To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nA successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n
When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n
The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n
Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n
To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nTechniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n
A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n
When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n
The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n
Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n
To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nIn one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n
Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n
A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n
When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n
The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n
Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n
To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nDevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n
In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n
Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n
A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n
When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n
The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n
Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n
To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nDevOps is more of an organizational agility approach.<\/p>\n\n\n\n
DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n
In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n
Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n
A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n
When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n
The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n
Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n
To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nNow, for the No part:<\/p>\n\n\n\n
DevOps is more of an organizational agility approach.<\/p>\n\n\n\n
DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n
In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n
Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n
A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n
When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n
The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n
Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n
To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nHere, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n
Now, for the No part:<\/p>\n\n\n\n
DevOps is more of an organizational agility approach.<\/p>\n\n\n\n
DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n
In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n
Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n
A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n
When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n
The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n
Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n
To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nBoth approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n
Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n
Now, for the No part:<\/p>\n\n\n\n
DevOps is more of an organizational agility approach.<\/p>\n\n\n\n
DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n
In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n
Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n
A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n
When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n
The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n
Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n
To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nBoth Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n
Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n
Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n
Now, for the No part:<\/p>\n\n\n\n
DevOps is more of an organizational agility approach.<\/p>\n\n\n\n
DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n
In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n
Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n
A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n
When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n
The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n
Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n
To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nFirst the Yes part \u2013 similarities:<\/p>\n\n\n\n
Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n
Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n
Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n
Now, for the No part:<\/p>\n\n\n\n
DevOps is more of an organizational agility approach.<\/p>\n\n\n\n
DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n
In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n
Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n
A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n
When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n
The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n
Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n
To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nThe simple answer is Yes and No.<\/p>\n\n\n\n
First the Yes part \u2013 similarities:<\/p>\n\n\n\n
Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n
Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n
Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n
Now, for the No part:<\/p>\n\n\n\n
DevOps is more of an organizational agility approach.<\/p>\n\n\n\n
DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n
In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n
Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n
A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n
When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n
The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n
Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n
To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\n- We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n
The simple answer is Yes and No.<\/p>\n\n\n\n
First the Yes part \u2013 similarities:<\/p>\n\n\n\n
Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n
Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n
Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n
Now, for the No part:<\/p>\n\n\n\n
DevOps is more of an organizational agility approach.<\/p>\n\n\n\n
DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n
In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n
Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n
A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n
When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n
The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n
Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n
To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nIn many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n
- We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n
The simple answer is Yes and No.<\/p>\n\n\n\n
First the Yes part \u2013 similarities:<\/p>\n\n\n\n
Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n
Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n
Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n
Now, for the No part:<\/p>\n\n\n\n
DevOps is more of an organizational agility approach.<\/p>\n\n\n\n
DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n
In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n
Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n
A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n
When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n
The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n
Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n
To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nThis is probably the most frequently asked question that I have received.<\/p>\n\n\n\n
In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n
- We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n
The simple answer is Yes and No.<\/p>\n\n\n\n
First the Yes part \u2013 similarities:<\/p>\n\n\n\n
Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n
Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n
Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n
Now, for the No part:<\/p>\n\n\n\n
DevOps is more of an organizational agility approach.<\/p>\n\n\n\n
DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n
In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n
Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n
A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n
When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n
The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n
Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n
To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nIf you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n
This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n
In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n
- We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n
The simple answer is Yes and No.<\/p>\n\n\n\n
First the Yes part \u2013 similarities:<\/p>\n\n\n\n
Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n
Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n
Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n
Now, for the No part:<\/p>\n\n\n\n
DevOps is more of an organizational agility approach.<\/p>\n\n\n\n
DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n
In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n
Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n
A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n
When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n
The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n
Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n
To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nyou can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
With an immutable approach, the shift is from a \u2018maintained\u2019 infrastructure \u2013 as it would be the case for dedicated data centers, to a \u2018replaceable\u2019 data center, as in the case of a cloud platform.<\/p>\n\n\n\n Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Usually, when we upgrade applications as patches, new features etc, there is a downtime needed to complete the setup and migration \u2013 as depicted in the top portion of the diagram.<\/p>\n\n\n\n With an immutable approach, the shift is from a \u2018maintained\u2019 infrastructure \u2013 as it would be the case for dedicated data centers, to a \u2018replaceable\u2019 data center, as in the case of a cloud platform.<\/p>\n\n\n\n Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
The concept itself is not new. We have heard this in different forms \u2013 most popular is the plug and play model. Just replace a component or add a new component and everything will work well and, in effect, replace the old configuration.<\/p>\n\n\n\n Usually, when we upgrade applications as patches, new features etc, there is a downtime needed to complete the setup and migration \u2013 as depicted in the top portion of the diagram.<\/p>\n\n\n\n With an immutable approach, the shift is from a \u2018maintained\u2019 infrastructure \u2013 as it would be the case for dedicated data centers, to a \u2018replaceable\u2019 data center, as in the case of a cloud platform.<\/p>\n\n\n\n Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
One of the concepts that is not talked about much, is related to immutable infrastructure.<\/p>\n\n\n\n The concept itself is not new. We have heard this in different forms \u2013 most popular is the plug and play model. Just replace a component or add a new component and everything will work well and, in effect, replace the old configuration.<\/p>\n\n\n\n Usually, when we upgrade applications as patches, new features etc, there is a downtime needed to complete the setup and migration \u2013 as depicted in the top portion of the diagram.<\/p>\n\n\n\n With an immutable approach, the shift is from a \u2018maintained\u2019 infrastructure \u2013 as it would be the case for dedicated data centers, to a \u2018replaceable\u2019 data center, as in the case of a cloud platform.<\/p>\n\n\n\n Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
While DevOps is also considered as a significant cultural approach, there are many aspects that contribute to deriving the benefits of a cross-functional team working together with the user experience in mind \u2013 which is the spirit of DevOps or the Software Delivery Lifecycle. [See also a related post on this topic<\/a>]<\/p>\n\n\n\n One of the concepts that is not talked about much, is related to immutable infrastructure.<\/p>\n\n\n\n The concept itself is not new. We have heard this in different forms \u2013 most popular is the plug and play model. Just replace a component or add a new component and everything will work well and, in effect, replace the old configuration.<\/p>\n\n\n\n Usually, when we upgrade applications as patches, new features etc, there is a downtime needed to complete the setup and migration \u2013 as depicted in the top portion of the diagram.<\/p>\n\n\n\n With an immutable approach, the shift is from a \u2018maintained\u2019 infrastructure \u2013 as it would be the case for dedicated data centers, to a \u2018replaceable\u2019 data center, as in the case of a cloud platform.<\/p>\n\n\n\n Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\u2013 We deploy to the cloud etc.<\/p>\n\n\n\n While DevOps is also considered as a significant cultural approach, there are many aspects that contribute to deriving the benefits of a cross-functional team working together with the user experience in mind \u2013 which is the spirit of DevOps or the Software Delivery Lifecycle. [See also a related post on this topic<\/a>]<\/p>\n\n\n\n One of the concepts that is not talked about much, is related to immutable infrastructure.<\/p>\n\n\n\n The concept itself is not new. We have heard this in different forms \u2013 most popular is the plug and play model. Just replace a component or add a new component and everything will work well and, in effect, replace the old configuration.<\/p>\n\n\n\n Usually, when we upgrade applications as patches, new features etc, there is a downtime needed to complete the setup and migration \u2013 as depicted in the top portion of the diagram.<\/p>\n\n\n\n With an immutable approach, the shift is from a \u2018maintained\u2019 infrastructure \u2013 as it would be the case for dedicated data centers, to a \u2018replaceable\u2019 data center, as in the case of a cloud platform.<\/p>\n\n\n\n Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\u2013 We have a CI\/CD pipeline [use Jenkins]<\/p>\n\n\n\n \u2013 We deploy to the cloud etc.<\/p>\n\n\n\n While DevOps is also considered as a significant cultural approach, there are many aspects that contribute to deriving the benefits of a cross-functional team working together with the user experience in mind \u2013 which is the spirit of DevOps or the Software Delivery Lifecycle. [See also a related post on this topic<\/a>]<\/p>\n\n\n\n One of the concepts that is not talked about much, is related to immutable infrastructure.<\/p>\n\n\n\n The concept itself is not new. We have heard this in different forms \u2013 most popular is the plug and play model. Just replace a component or add a new component and everything will work well and, in effect, replace the old configuration.<\/p>\n\n\n\n Usually, when we upgrade applications as patches, new features etc, there is a downtime needed to complete the setup and migration \u2013 as depicted in the top portion of the diagram.<\/p>\n\n\n\n With an immutable approach, the shift is from a \u2018maintained\u2019 infrastructure \u2013 as it would be the case for dedicated data centers, to a \u2018replaceable\u2019 data center, as in the case of a cloud platform.<\/p>\n\n\n\n Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\u2013 We use Chef\/Puppet<\/p>\n\n\n\n \u2013 We have a CI\/CD pipeline [use Jenkins]<\/p>\n\n\n\n \u2013 We deploy to the cloud etc.<\/p>\n\n\n\n While DevOps is also considered as a significant cultural approach, there are many aspects that contribute to deriving the benefits of a cross-functional team working together with the user experience in mind \u2013 which is the spirit of DevOps or the Software Delivery Lifecycle. [See also a related post on this topic<\/a>]<\/p>\n\n\n\n One of the concepts that is not talked about much, is related to immutable infrastructure.<\/p>\n\n\n\n The concept itself is not new. We have heard this in different forms \u2013 most popular is the plug and play model. Just replace a component or add a new component and everything will work well and, in effect, replace the old configuration.<\/p>\n\n\n\n Usually, when we upgrade applications as patches, new features etc, there is a downtime needed to complete the setup and migration \u2013 as depicted in the top portion of the diagram.<\/p>\n\n\n\n With an immutable approach, the shift is from a \u2018maintained\u2019 infrastructure \u2013 as it would be the case for dedicated data centers, to a \u2018replaceable\u2019 data center, as in the case of a cloud platform.<\/p>\n\n\n\n Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Similarly, there are many misconceptions about DevOps. When asked what is your DevOps approach.<\/p>\n\n\n\n \u2013 We use Chef\/Puppet<\/p>\n\n\n\n \u2013 We have a CI\/CD pipeline [use Jenkins]<\/p>\n\n\n\n \u2013 We deploy to the cloud etc.<\/p>\n\n\n\n While DevOps is also considered as a significant cultural approach, there are many aspects that contribute to deriving the benefits of a cross-functional team working together with the user experience in mind \u2013 which is the spirit of DevOps or the Software Delivery Lifecycle. [See also a related post on this topic<\/a>]<\/p>\n\n\n\n One of the concepts that is not talked about much, is related to immutable infrastructure.<\/p>\n\n\n\n The concept itself is not new. We have heard this in different forms \u2013 most popular is the plug and play model. Just replace a component or add a new component and everything will work well and, in effect, replace the old configuration.<\/p>\n\n\n\n Usually, when we upgrade applications as patches, new features etc, there is a downtime needed to complete the setup and migration \u2013 as depicted in the top portion of the diagram.<\/p>\n\n\n\n With an immutable approach, the shift is from a \u2018maintained\u2019 infrastructure \u2013 as it would be the case for dedicated data centers, to a \u2018replaceable\u2019 data center, as in the case of a cloud platform.<\/p>\n\n\n\n Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\u201cWe are already agile, we do daily standups \u2013 so, we do not need any training. Just tell us how to improve productivity.\u201d<\/p>\n\n\n\n Similarly, there are many misconceptions about DevOps. When asked what is your DevOps approach.<\/p>\n\n\n\n \u2013 We use Chef\/Puppet<\/p>\n\n\n\n \u2013 We have a CI\/CD pipeline [use Jenkins]<\/p>\n\n\n\n \u2013 We deploy to the cloud etc.<\/p>\n\n\n\n While DevOps is also considered as a significant cultural approach, there are many aspects that contribute to deriving the benefits of a cross-functional team working together with the user experience in mind \u2013 which is the spirit of DevOps or the Software Delivery Lifecycle. [See also a related post on this topic<\/a>]<\/p>\n\n\n\n One of the concepts that is not talked about much, is related to immutable infrastructure.<\/p>\n\n\n\n The concept itself is not new. We have heard this in different forms \u2013 most popular is the plug and play model. Just replace a component or add a new component and everything will work well and, in effect, replace the old configuration.<\/p>\n\n\n\n Usually, when we upgrade applications as patches, new features etc, there is a downtime needed to complete the setup and migration \u2013 as depicted in the top portion of the diagram.<\/p>\n\n\n\n With an immutable approach, the shift is from a \u2018maintained\u2019 infrastructure \u2013 as it would be the case for dedicated data centers, to a \u2018replaceable\u2019 data center, as in the case of a cloud platform.<\/p>\n\n\n\n Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
In such situations, the conversations invariably start something like this:<\/p>\n\n\n\n \u201cWe are already agile, we do daily standups \u2013 so, we do not need any training. Just tell us how to improve productivity.\u201d<\/p>\n\n\n\n Similarly, there are many misconceptions about DevOps. When asked what is your DevOps approach.<\/p>\n\n\n\n \u2013 We use Chef\/Puppet<\/p>\n\n\n\n \u2013 We have a CI\/CD pipeline [use Jenkins]<\/p>\n\n\n\n \u2013 We deploy to the cloud etc.<\/p>\n\n\n\n While DevOps is also considered as a significant cultural approach, there are many aspects that contribute to deriving the benefits of a cross-functional team working together with the user experience in mind \u2013 which is the spirit of DevOps or the Software Delivery Lifecycle. [See also a related post on this topic<\/a>]<\/p>\n\n\n\n One of the concepts that is not talked about much, is related to immutable infrastructure.<\/p>\n\n\n\n The concept itself is not new. We have heard this in different forms \u2013 most popular is the plug and play model. Just replace a component or add a new component and everything will work well and, in effect, replace the old configuration.<\/p>\n\n\n\n Usually, when we upgrade applications as patches, new features etc, there is a downtime needed to complete the setup and migration \u2013 as depicted in the top portion of the diagram.<\/p>\n\n\n\n With an immutable approach, the shift is from a \u2018maintained\u2019 infrastructure \u2013 as it would be the case for dedicated data centers, to a \u2018replaceable\u2019 data center, as in the case of a cloud platform.<\/p>\n\n\n\n Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Over the many years of my interactions with various projects, the most common misconception that I come across is equating a daily standup to scrum and agile.<\/p>\n\n\n\n In such situations, the conversations invariably start something like this:<\/p>\n\n\n\n \u201cWe are already agile, we do daily standups \u2013 so, we do not need any training. Just tell us how to improve productivity.\u201d<\/p>\n\n\n\n Similarly, there are many misconceptions about DevOps. When asked what is your DevOps approach.<\/p>\n\n\n\n \u2013 We use Chef\/Puppet<\/p>\n\n\n\n \u2013 We have a CI\/CD pipeline [use Jenkins]<\/p>\n\n\n\n \u2013 We deploy to the cloud etc.<\/p>\n\n\n\n While DevOps is also considered as a significant cultural approach, there are many aspects that contribute to deriving the benefits of a cross-functional team working together with the user experience in mind \u2013 which is the spirit of DevOps or the Software Delivery Lifecycle. [See also a related post on this topic<\/a>]<\/p>\n\n\n\n One of the concepts that is not talked about much, is related to immutable infrastructure.<\/p>\n\n\n\n The concept itself is not new. We have heard this in different forms \u2013 most popular is the plug and play model. Just replace a component or add a new component and everything will work well and, in effect, replace the old configuration.<\/p>\n\n\n\n Usually, when we upgrade applications as patches, new features etc, there is a downtime needed to complete the setup and migration \u2013 as depicted in the top portion of the diagram.<\/p>\n\n\n\n With an immutable approach, the shift is from a \u2018maintained\u2019 infrastructure \u2013 as it would be the case for dedicated data centers, to a \u2018replaceable\u2019 data center, as in the case of a cloud platform.<\/p>\n\n\n\n Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Even if you have not started your DevOps journey yet, this will be a very useful read!<\/p>\n","post_title":"Some inferences from the State of DevOps 2017 report","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"inferences-state-devops-2017-report","to_ping":"","pinged":"","post_modified":"2024-01-29 12:00:04","post_modified_gmt":"2024-01-29 12:00:04","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7334","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7337,"post_author":"30","post_date":"2017-01-28 14:31:15","post_date_gmt":"2017-01-28 09:01:15","post_content":"\n Over the many years of my interactions with various projects, the most common misconception that I come across is equating a daily standup to scrum and agile.<\/p>\n\n\n\n In such situations, the conversations invariably start something like this:<\/p>\n\n\n\n \u201cWe are already agile, we do daily standups \u2013 so, we do not need any training. Just tell us how to improve productivity.\u201d<\/p>\n\n\n\n Similarly, there are many misconceptions about DevOps. When asked what is your DevOps approach.<\/p>\n\n\n\n \u2013 We use Chef\/Puppet<\/p>\n\n\n\n \u2013 We have a CI\/CD pipeline [use Jenkins]<\/p>\n\n\n\n \u2013 We deploy to the cloud etc.<\/p>\n\n\n\n While DevOps is also considered as a significant cultural approach, there are many aspects that contribute to deriving the benefits of a cross-functional team working together with the user experience in mind \u2013 which is the spirit of DevOps or the Software Delivery Lifecycle. [See also a related post on this topic<\/a>]<\/p>\n\n\n\n One of the concepts that is not talked about much, is related to immutable infrastructure.<\/p>\n\n\n\n The concept itself is not new. We have heard this in different forms \u2013 most popular is the plug and play model. Just replace a component or add a new component and everything will work well and, in effect, replace the old configuration.<\/p>\n\n\n\n Usually, when we upgrade applications as patches, new features etc, there is a downtime needed to complete the setup and migration \u2013 as depicted in the top portion of the diagram.<\/p>\n\n\n\n With an immutable approach, the shift is from a \u2018maintained\u2019 infrastructure \u2013 as it would be the case for dedicated data centers, to a \u2018replaceable\u2019 data center, as in the case of a cloud platform.<\/p>\n\n\n\n Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
In summary, this is a well made report that is easy to read and understand.<\/p>\n\n\n\n Even if you have not started your DevOps journey yet, this will be a very useful read!<\/p>\n","post_title":"Some inferences from the State of DevOps 2017 report","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"inferences-state-devops-2017-report","to_ping":"","pinged":"","post_modified":"2024-01-29 12:00:04","post_modified_gmt":"2024-01-29 12:00:04","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7334","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7337,"post_author":"30","post_date":"2017-01-28 14:31:15","post_date_gmt":"2017-01-28 09:01:15","post_content":"\n Over the many years of my interactions with various projects, the most common misconception that I come across is equating a daily standup to scrum and agile.<\/p>\n\n\n\n In such situations, the conversations invariably start something like this:<\/p>\n\n\n\n \u201cWe are already agile, we do daily standups \u2013 so, we do not need any training. Just tell us how to improve productivity.\u201d<\/p>\n\n\n\n Similarly, there are many misconceptions about DevOps. When asked what is your DevOps approach.<\/p>\n\n\n\n \u2013 We use Chef\/Puppet<\/p>\n\n\n\n \u2013 We have a CI\/CD pipeline [use Jenkins]<\/p>\n\n\n\n \u2013 We deploy to the cloud etc.<\/p>\n\n\n\n While DevOps is also considered as a significant cultural approach, there are many aspects that contribute to deriving the benefits of a cross-functional team working together with the user experience in mind \u2013 which is the spirit of DevOps or the Software Delivery Lifecycle. [See also a related post on this topic<\/a>]<\/p>\n\n\n\n One of the concepts that is not talked about much, is related to immutable infrastructure.<\/p>\n\n\n\n The concept itself is not new. We have heard this in different forms \u2013 most popular is the plug and play model. Just replace a component or add a new component and everything will work well and, in effect, replace the old configuration.<\/p>\n\n\n\n Usually, when we upgrade applications as patches, new features etc, there is a downtime needed to complete the setup and migration \u2013 as depicted in the top portion of the diagram.<\/p>\n\n\n\n With an immutable approach, the shift is from a \u2018maintained\u2019 infrastructure \u2013 as it would be the case for dedicated data centers, to a \u2018replaceable\u2019 data center, as in the case of a cloud platform.<\/p>\n\n\n\n Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
This reinforces the approach that I had talked about in an earlier post.<\/a><\/p>\n\n\n\n In summary, this is a well made report that is easy to read and understand.<\/p>\n\n\n\n Even if you have not started your DevOps journey yet, this will be a very useful read!<\/p>\n","post_title":"Some inferences from the State of DevOps 2017 report","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"inferences-state-devops-2017-report","to_ping":"","pinged":"","post_modified":"2024-01-29 12:00:04","post_modified_gmt":"2024-01-29 12:00:04","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7334","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7337,"post_author":"30","post_date":"2017-01-28 14:31:15","post_date_gmt":"2017-01-28 09:01:15","post_content":"\n Over the many years of my interactions with various projects, the most common misconception that I come across is equating a daily standup to scrum and agile.<\/p>\n\n\n\n In such situations, the conversations invariably start something like this:<\/p>\n\n\n\n \u201cWe are already agile, we do daily standups \u2013 so, we do not need any training. Just tell us how to improve productivity.\u201d<\/p>\n\n\n\n Similarly, there are many misconceptions about DevOps. When asked what is your DevOps approach.<\/p>\n\n\n\n \u2013 We use Chef\/Puppet<\/p>\n\n\n\n \u2013 We have a CI\/CD pipeline [use Jenkins]<\/p>\n\n\n\n \u2013 We deploy to the cloud etc.<\/p>\n\n\n\n While DevOps is also considered as a significant cultural approach, there are many aspects that contribute to deriving the benefits of a cross-functional team working together with the user experience in mind \u2013 which is the spirit of DevOps or the Software Delivery Lifecycle. [See also a related post on this topic<\/a>]<\/p>\n\n\n\n One of the concepts that is not talked about much, is related to immutable infrastructure.<\/p>\n\n\n\n The concept itself is not new. We have heard this in different forms \u2013 most popular is the plug and play model. Just replace a component or add a new component and everything will work well and, in effect, replace the old configuration.<\/p>\n\n\n\n Usually, when we upgrade applications as patches, new features etc, there is a downtime needed to complete the setup and migration \u2013 as depicted in the top portion of the diagram.<\/p>\n\n\n\n With an immutable approach, the shift is from a \u2018maintained\u2019 infrastructure \u2013 as it would be the case for dedicated data centers, to a \u2018replaceable\u2019 data center, as in the case of a cloud platform.<\/p>\n\n\n\n Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
I want to also highlight the importance of architecture to really derive the benefits of a DevOps transformation. It is no longer sufficient to adopt some tools for automating specific tasks of the software delivery lifecycle, but also the core of the enterprise and application architectures.<\/p>\n\n\n\n This reinforces the approach that I had talked about in an earlier post.<\/a><\/p>\n\n\n\n In summary, this is a well made report that is easy to read and understand.<\/p>\n\n\n\n Even if you have not started your DevOps journey yet, this will be a very useful read!<\/p>\n","post_title":"Some inferences from the State of DevOps 2017 report","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"inferences-state-devops-2017-report","to_ping":"","pinged":"","post_modified":"2024-01-29 12:00:04","post_modified_gmt":"2024-01-29 12:00:04","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7334","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7337,"post_author":"30","post_date":"2017-01-28 14:31:15","post_date_gmt":"2017-01-28 09:01:15","post_content":"\n Over the many years of my interactions with various projects, the most common misconception that I come across is equating a daily standup to scrum and agile.<\/p>\n\n\n\n In such situations, the conversations invariably start something like this:<\/p>\n\n\n\n \u201cWe are already agile, we do daily standups \u2013 so, we do not need any training. Just tell us how to improve productivity.\u201d<\/p>\n\n\n\n Similarly, there are many misconceptions about DevOps. When asked what is your DevOps approach.<\/p>\n\n\n\n \u2013 We use Chef\/Puppet<\/p>\n\n\n\n \u2013 We have a CI\/CD pipeline [use Jenkins]<\/p>\n\n\n\n \u2013 We deploy to the cloud etc.<\/p>\n\n\n\n While DevOps is also considered as a significant cultural approach, there are many aspects that contribute to deriving the benefits of a cross-functional team working together with the user experience in mind \u2013 which is the spirit of DevOps or the Software Delivery Lifecycle. [See also a related post on this topic<\/a>]<\/p>\n\n\n\n One of the concepts that is not talked about much, is related to immutable infrastructure.<\/p>\n\n\n\n The concept itself is not new. We have heard this in different forms \u2013 most popular is the plug and play model. Just replace a component or add a new component and everything will work well and, in effect, replace the old configuration.<\/p>\n\n\n\n Usually, when we upgrade applications as patches, new features etc, there is a downtime needed to complete the setup and migration \u2013 as depicted in the top portion of the diagram.<\/p>\n\n\n\n With an immutable approach, the shift is from a \u2018maintained\u2019 infrastructure \u2013 as it would be the case for dedicated data centers, to a \u2018replaceable\u2019 data center, as in the case of a cloud platform.<\/p>\n\n\n\n Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
The power of autonomy and ownership at a team level are also indicated in the report where one can see a correlation of loosely coupled, autonomous teams that work together with stable, continuous delivery practices.<\/p>\n\n\n\n I want to also highlight the importance of architecture to really derive the benefits of a DevOps transformation. It is no longer sufficient to adopt some tools for automating specific tasks of the software delivery lifecycle, but also the core of the enterprise and application architectures.<\/p>\n\n\n\n This reinforces the approach that I had talked about in an earlier post.<\/a><\/p>\n\n\n\n In summary, this is a well made report that is easy to read and understand.<\/p>\n\n\n\n Even if you have not started your DevOps journey yet, this will be a very useful read!<\/p>\n","post_title":"Some inferences from the State of DevOps 2017 report","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"inferences-state-devops-2017-report","to_ping":"","pinged":"","post_modified":"2024-01-29 12:00:04","post_modified_gmt":"2024-01-29 12:00:04","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7334","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7337,"post_author":"30","post_date":"2017-01-28 14:31:15","post_date_gmt":"2017-01-28 09:01:15","post_content":"\n Over the many years of my interactions with various projects, the most common misconception that I come across is equating a daily standup to scrum and agile.<\/p>\n\n\n\n In such situations, the conversations invariably start something like this:<\/p>\n\n\n\n \u201cWe are already agile, we do daily standups \u2013 so, we do not need any training. Just tell us how to improve productivity.\u201d<\/p>\n\n\n\n Similarly, there are many misconceptions about DevOps. When asked what is your DevOps approach.<\/p>\n\n\n\n \u2013 We use Chef\/Puppet<\/p>\n\n\n\n \u2013 We have a CI\/CD pipeline [use Jenkins]<\/p>\n\n\n\n \u2013 We deploy to the cloud etc.<\/p>\n\n\n\n While DevOps is also considered as a significant cultural approach, there are many aspects that contribute to deriving the benefits of a cross-functional team working together with the user experience in mind \u2013 which is the spirit of DevOps or the Software Delivery Lifecycle. [See also a related post on this topic<\/a>]<\/p>\n\n\n\n One of the concepts that is not talked about much, is related to immutable infrastructure.<\/p>\n\n\n\n The concept itself is not new. We have heard this in different forms \u2013 most popular is the plug and play model. Just replace a component or add a new component and everything will work well and, in effect, replace the old configuration.<\/p>\n\n\n\n Usually, when we upgrade applications as patches, new features etc, there is a downtime needed to complete the setup and migration \u2013 as depicted in the top portion of the diagram.<\/p>\n\n\n\n With an immutable approach, the shift is from a \u2018maintained\u2019 infrastructure \u2013 as it would be the case for dedicated data centers, to a \u2018replaceable\u2019 data center, as in the case of a cloud platform.<\/p>\n\n\n\n Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Since Lean approaches have been proven in manufacturing companies there are enough examples and patterns that we can adopt in the IT industry context.<\/p>\n\n\n\n The power of autonomy and ownership at a team level are also indicated in the report where one can see a correlation of loosely coupled, autonomous teams that work together with stable, continuous delivery practices.<\/p>\n\n\n\n I want to also highlight the importance of architecture to really derive the benefits of a DevOps transformation. It is no longer sufficient to adopt some tools for automating specific tasks of the software delivery lifecycle, but also the core of the enterprise and application architectures.<\/p>\n\n\n\n This reinforces the approach that I had talked about in an earlier post.<\/a><\/p>\n\n\n\n In summary, this is a well made report that is easy to read and understand.<\/p>\n\n\n\n Even if you have not started your DevOps journey yet, this will be a very useful read!<\/p>\n","post_title":"Some inferences from the State of DevOps 2017 report","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"inferences-state-devops-2017-report","to_ping":"","pinged":"","post_modified":"2024-01-29 12:00:04","post_modified_gmt":"2024-01-29 12:00:04","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7334","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7337,"post_author":"30","post_date":"2017-01-28 14:31:15","post_date_gmt":"2017-01-28 09:01:15","post_content":"\n Over the many years of my interactions with various projects, the most common misconception that I come across is equating a daily standup to scrum and agile.<\/p>\n\n\n\n In such situations, the conversations invariably start something like this:<\/p>\n\n\n\n \u201cWe are already agile, we do daily standups \u2013 so, we do not need any training. Just tell us how to improve productivity.\u201d<\/p>\n\n\n\n Similarly, there are many misconceptions about DevOps. When asked what is your DevOps approach.<\/p>\n\n\n\n \u2013 We use Chef\/Puppet<\/p>\n\n\n\n \u2013 We have a CI\/CD pipeline [use Jenkins]<\/p>\n\n\n\n \u2013 We deploy to the cloud etc.<\/p>\n\n\n\n While DevOps is also considered as a significant cultural approach, there are many aspects that contribute to deriving the benefits of a cross-functional team working together with the user experience in mind \u2013 which is the spirit of DevOps or the Software Delivery Lifecycle. [See also a related post on this topic<\/a>]<\/p>\n\n\n\n One of the concepts that is not talked about much, is related to immutable infrastructure.<\/p>\n\n\n\n The concept itself is not new. We have heard this in different forms \u2013 most popular is the plug and play model. Just replace a component or add a new component and everything will work well and, in effect, replace the old configuration.<\/p>\n\n\n\n Usually, when we upgrade applications as patches, new features etc, there is a downtime needed to complete the setup and migration \u2013 as depicted in the top portion of the diagram.<\/p>\n\n\n\n With an immutable approach, the shift is from a \u2018maintained\u2019 infrastructure \u2013 as it would be the case for dedicated data centers, to a \u2018replaceable\u2019 data center, as in the case of a cloud platform.<\/p>\n\n\n\n Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
The report also talks of the applicability of DevOps approaches \u2013 which can trace their origins to principles of Lean and Theory of Constraints models \u2013 is not only for the Unicorns, but for all organizations, including ones that have not-so-modern technologies deployed.<\/p>\n\n\n\n Since Lean approaches have been proven in manufacturing companies there are enough examples and patterns that we can adopt in the IT industry context.<\/p>\n\n\n\n The power of autonomy and ownership at a team level are also indicated in the report where one can see a correlation of loosely coupled, autonomous teams that work together with stable, continuous delivery practices.<\/p>\n\n\n\n I want to also highlight the importance of architecture to really derive the benefits of a DevOps transformation. It is no longer sufficient to adopt some tools for automating specific tasks of the software delivery lifecycle, but also the core of the enterprise and application architectures.<\/p>\n\n\n\n This reinforces the approach that I had talked about in an earlier post.<\/a><\/p>\n\n\n\n In summary, this is a well made report that is easy to read and understand.<\/p>\n\n\n\n Even if you have not started your DevOps journey yet, this will be a very useful read!<\/p>\n","post_title":"Some inferences from the State of DevOps 2017 report","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"inferences-state-devops-2017-report","to_ping":"","pinged":"","post_modified":"2024-01-29 12:00:04","post_modified_gmt":"2024-01-29 12:00:04","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7334","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7337,"post_author":"30","post_date":"2017-01-28 14:31:15","post_date_gmt":"2017-01-28 09:01:15","post_content":"\n Over the many years of my interactions with various projects, the most common misconception that I come across is equating a daily standup to scrum and agile.<\/p>\n\n\n\n In such situations, the conversations invariably start something like this:<\/p>\n\n\n\n \u201cWe are already agile, we do daily standups \u2013 so, we do not need any training. Just tell us how to improve productivity.\u201d<\/p>\n\n\n\n Similarly, there are many misconceptions about DevOps. When asked what is your DevOps approach.<\/p>\n\n\n\n \u2013 We use Chef\/Puppet<\/p>\n\n\n\n \u2013 We have a CI\/CD pipeline [use Jenkins]<\/p>\n\n\n\n \u2013 We deploy to the cloud etc.<\/p>\n\n\n\n While DevOps is also considered as a significant cultural approach, there are many aspects that contribute to deriving the benefits of a cross-functional team working together with the user experience in mind \u2013 which is the spirit of DevOps or the Software Delivery Lifecycle. [See also a related post on this topic<\/a>]<\/p>\n\n\n\n One of the concepts that is not talked about much, is related to immutable infrastructure.<\/p>\n\n\n\n The concept itself is not new. We have heard this in different forms \u2013 most popular is the plug and play model. Just replace a component or add a new component and everything will work well and, in effect, replace the old configuration.<\/p>\n\n\n\n Usually, when we upgrade applications as patches, new features etc, there is a downtime needed to complete the setup and migration \u2013 as depicted in the top portion of the diagram.<\/p>\n\n\n\n With an immutable approach, the shift is from a \u2018maintained\u2019 infrastructure \u2013 as it would be the case for dedicated data centers, to a \u2018replaceable\u2019 data center, as in the case of a cloud platform.<\/p>\n\n\n\n Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
From my experience with various transformational and organizational excellence initiatives across multiple industries, this is a common success factor. Setting a clear vision and mission and letting the teams take up ownership detail out execution strategies creates a sustainable transformation.<\/p>\n\n\n\n The report also talks of the applicability of DevOps approaches \u2013 which can trace their origins to principles of Lean and Theory of Constraints models \u2013 is not only for the Unicorns, but for all organizations, including ones that have not-so-modern technologies deployed.<\/p>\n\n\n\n Since Lean approaches have been proven in manufacturing companies there are enough examples and patterns that we can adopt in the IT industry context.<\/p>\n\n\n\n The power of autonomy and ownership at a team level are also indicated in the report where one can see a correlation of loosely coupled, autonomous teams that work together with stable, continuous delivery practices.<\/p>\n\n\n\n I want to also highlight the importance of architecture to really derive the benefits of a DevOps transformation. It is no longer sufficient to adopt some tools for automating specific tasks of the software delivery lifecycle, but also the core of the enterprise and application architectures.<\/p>\n\n\n\n This reinforces the approach that I had talked about in an earlier post.<\/a><\/p>\n\n\n\n In summary, this is a well made report that is easy to read and understand.<\/p>\n\n\n\n Even if you have not started your DevOps journey yet, this will be a very useful read!<\/p>\n","post_title":"Some inferences from the State of DevOps 2017 report","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"inferences-state-devops-2017-report","to_ping":"","pinged":"","post_modified":"2024-01-29 12:00:04","post_modified_gmt":"2024-01-29 12:00:04","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7334","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7337,"post_author":"30","post_date":"2017-01-28 14:31:15","post_date_gmt":"2017-01-28 09:01:15","post_content":"\n Over the many years of my interactions with various projects, the most common misconception that I come across is equating a daily standup to scrum and agile.<\/p>\n\n\n\n In such situations, the conversations invariably start something like this:<\/p>\n\n\n\n \u201cWe are already agile, we do daily standups \u2013 so, we do not need any training. Just tell us how to improve productivity.\u201d<\/p>\n\n\n\n Similarly, there are many misconceptions about DevOps. When asked what is your DevOps approach.<\/p>\n\n\n\n \u2013 We use Chef\/Puppet<\/p>\n\n\n\n \u2013 We have a CI\/CD pipeline [use Jenkins]<\/p>\n\n\n\n \u2013 We deploy to the cloud etc.<\/p>\n\n\n\n While DevOps is also considered as a significant cultural approach, there are many aspects that contribute to deriving the benefits of a cross-functional team working together with the user experience in mind \u2013 which is the spirit of DevOps or the Software Delivery Lifecycle. [See also a related post on this topic<\/a>]<\/p>\n\n\n\n One of the concepts that is not talked about much, is related to immutable infrastructure.<\/p>\n\n\n\n The concept itself is not new. We have heard this in different forms \u2013 most popular is the plug and play model. Just replace a component or add a new component and everything will work well and, in effect, replace the old configuration.<\/p>\n\n\n\n Usually, when we upgrade applications as patches, new features etc, there is a downtime needed to complete the setup and migration \u2013 as depicted in the top portion of the diagram.<\/p>\n\n\n\n With an immutable approach, the shift is from a \u2018maintained\u2019 infrastructure \u2013 as it would be the case for dedicated data centers, to a \u2018replaceable\u2019 data center, as in the case of a cloud platform.<\/p>\n\n\n\n Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
* Personal Recognition<\/p>\n\n\n\n From my experience with various transformational and organizational excellence initiatives across multiple industries, this is a common success factor. Setting a clear vision and mission and letting the teams take up ownership detail out execution strategies creates a sustainable transformation.<\/p>\n\n\n\n The report also talks of the applicability of DevOps approaches \u2013 which can trace their origins to principles of Lean and Theory of Constraints models \u2013 is not only for the Unicorns, but for all organizations, including ones that have not-so-modern technologies deployed.<\/p>\n\n\n\n Since Lean approaches have been proven in manufacturing companies there are enough examples and patterns that we can adopt in the IT industry context.<\/p>\n\n\n\n The power of autonomy and ownership at a team level are also indicated in the report where one can see a correlation of loosely coupled, autonomous teams that work together with stable, continuous delivery practices.<\/p>\n\n\n\n I want to also highlight the importance of architecture to really derive the benefits of a DevOps transformation. It is no longer sufficient to adopt some tools for automating specific tasks of the software delivery lifecycle, but also the core of the enterprise and application architectures.<\/p>\n\n\n\n This reinforces the approach that I had talked about in an earlier post.<\/a><\/p>\n\n\n\n In summary, this is a well made report that is easy to read and understand.<\/p>\n\n\n\n Even if you have not started your DevOps journey yet, this will be a very useful read!<\/p>\n","post_title":"Some inferences from the State of DevOps 2017 report","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"inferences-state-devops-2017-report","to_ping":"","pinged":"","post_modified":"2024-01-29 12:00:04","post_modified_gmt":"2024-01-29 12:00:04","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7334","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7337,"post_author":"30","post_date":"2017-01-28 14:31:15","post_date_gmt":"2017-01-28 09:01:15","post_content":"\n Over the many years of my interactions with various projects, the most common misconception that I come across is equating a daily standup to scrum and agile.<\/p>\n\n\n\n In such situations, the conversations invariably start something like this:<\/p>\n\n\n\n \u201cWe are already agile, we do daily standups \u2013 so, we do not need any training. Just tell us how to improve productivity.\u201d<\/p>\n\n\n\n Similarly, there are many misconceptions about DevOps. When asked what is your DevOps approach.<\/p>\n\n\n\n \u2013 We use Chef\/Puppet<\/p>\n\n\n\n \u2013 We have a CI\/CD pipeline [use Jenkins]<\/p>\n\n\n\n \u2013 We deploy to the cloud etc.<\/p>\n\n\n\n While DevOps is also considered as a significant cultural approach, there are many aspects that contribute to deriving the benefits of a cross-functional team working together with the user experience in mind \u2013 which is the spirit of DevOps or the Software Delivery Lifecycle. [See also a related post on this topic<\/a>]<\/p>\n\n\n\n One of the concepts that is not talked about much, is related to immutable infrastructure.<\/p>\n\n\n\n The concept itself is not new. We have heard this in different forms \u2013 most popular is the plug and play model. Just replace a component or add a new component and everything will work well and, in effect, replace the old configuration.<\/p>\n\n\n\n Usually, when we upgrade applications as patches, new features etc, there is a downtime needed to complete the setup and migration \u2013 as depicted in the top portion of the diagram.<\/p>\n\n\n\n With an immutable approach, the shift is from a \u2018maintained\u2019 infrastructure \u2013 as it would be the case for dedicated data centers, to a \u2018replaceable\u2019 data center, as in the case of a cloud platform.<\/p>\n\n\n\n Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
* Supportive Leadership and<\/p>\n\n\n\n * Personal Recognition<\/p>\n\n\n\n From my experience with various transformational and organizational excellence initiatives across multiple industries, this is a common success factor. Setting a clear vision and mission and letting the teams take up ownership detail out execution strategies creates a sustainable transformation.<\/p>\n\n\n\n The report also talks of the applicability of DevOps approaches \u2013 which can trace their origins to principles of Lean and Theory of Constraints models \u2013 is not only for the Unicorns, but for all organizations, including ones that have not-so-modern technologies deployed.<\/p>\n\n\n\n Since Lean approaches have been proven in manufacturing companies there are enough examples and patterns that we can adopt in the IT industry context.<\/p>\n\n\n\n The power of autonomy and ownership at a team level are also indicated in the report where one can see a correlation of loosely coupled, autonomous teams that work together with stable, continuous delivery practices.<\/p>\n\n\n\n I want to also highlight the importance of architecture to really derive the benefits of a DevOps transformation. It is no longer sufficient to adopt some tools for automating specific tasks of the software delivery lifecycle, but also the core of the enterprise and application architectures.<\/p>\n\n\n\n This reinforces the approach that I had talked about in an earlier post.<\/a><\/p>\n\n\n\n In summary, this is a well made report that is easy to read and understand.<\/p>\n\n\n\n Even if you have not started your DevOps journey yet, this will be a very useful read!<\/p>\n","post_title":"Some inferences from the State of DevOps 2017 report","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"inferences-state-devops-2017-report","to_ping":"","pinged":"","post_modified":"2024-01-29 12:00:04","post_modified_gmt":"2024-01-29 12:00:04","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7334","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7337,"post_author":"30","post_date":"2017-01-28 14:31:15","post_date_gmt":"2017-01-28 09:01:15","post_content":"\n Over the many years of my interactions with various projects, the most common misconception that I come across is equating a daily standup to scrum and agile.<\/p>\n\n\n\n In such situations, the conversations invariably start something like this:<\/p>\n\n\n\n \u201cWe are already agile, we do daily standups \u2013 so, we do not need any training. Just tell us how to improve productivity.\u201d<\/p>\n\n\n\n Similarly, there are many misconceptions about DevOps. When asked what is your DevOps approach.<\/p>\n\n\n\n \u2013 We use Chef\/Puppet<\/p>\n\n\n\n \u2013 We have a CI\/CD pipeline [use Jenkins]<\/p>\n\n\n\n \u2013 We deploy to the cloud etc.<\/p>\n\n\n\n While DevOps is also considered as a significant cultural approach, there are many aspects that contribute to deriving the benefits of a cross-functional team working together with the user experience in mind \u2013 which is the spirit of DevOps or the Software Delivery Lifecycle. [See also a related post on this topic<\/a>]<\/p>\n\n\n\n One of the concepts that is not talked about much, is related to immutable infrastructure.<\/p>\n\n\n\n The concept itself is not new. We have heard this in different forms \u2013 most popular is the plug and play model. Just replace a component or add a new component and everything will work well and, in effect, replace the old configuration.<\/p>\n\n\n\n Usually, when we upgrade applications as patches, new features etc, there is a downtime needed to complete the setup and migration \u2013 as depicted in the top portion of the diagram.<\/p>\n\n\n\n With an immutable approach, the shift is from a \u2018maintained\u2019 infrastructure \u2013 as it would be the case for dedicated data centers, to a \u2018replaceable\u2019 data center, as in the case of a cloud platform.<\/p>\n\n\n\n Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
* Intellectual Stimulation<\/p>\n\n\n\n * Supportive Leadership and<\/p>\n\n\n\n * Personal Recognition<\/p>\n\n\n\n From my experience with various transformational and organizational excellence initiatives across multiple industries, this is a common success factor. Setting a clear vision and mission and letting the teams take up ownership detail out execution strategies creates a sustainable transformation.<\/p>\n\n\n\n The report also talks of the applicability of DevOps approaches \u2013 which can trace their origins to principles of Lean and Theory of Constraints models \u2013 is not only for the Unicorns, but for all organizations, including ones that have not-so-modern technologies deployed.<\/p>\n\n\n\n Since Lean approaches have been proven in manufacturing companies there are enough examples and patterns that we can adopt in the IT industry context.<\/p>\n\n\n\n The power of autonomy and ownership at a team level are also indicated in the report where one can see a correlation of loosely coupled, autonomous teams that work together with stable, continuous delivery practices.<\/p>\n\n\n\n I want to also highlight the importance of architecture to really derive the benefits of a DevOps transformation. It is no longer sufficient to adopt some tools for automating specific tasks of the software delivery lifecycle, but also the core of the enterprise and application architectures.<\/p>\n\n\n\n This reinforces the approach that I had talked about in an earlier post.<\/a><\/p>\n\n\n\n In summary, this is a well made report that is easy to read and understand.<\/p>\n\n\n\n Even if you have not started your DevOps journey yet, this will be a very useful read!<\/p>\n","post_title":"Some inferences from the State of DevOps 2017 report","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"inferences-state-devops-2017-report","to_ping":"","pinged":"","post_modified":"2024-01-29 12:00:04","post_modified_gmt":"2024-01-29 12:00:04","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7334","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7337,"post_author":"30","post_date":"2017-01-28 14:31:15","post_date_gmt":"2017-01-28 09:01:15","post_content":"\n Over the many years of my interactions with various projects, the most common misconception that I come across is equating a daily standup to scrum and agile.<\/p>\n\n\n\n In such situations, the conversations invariably start something like this:<\/p>\n\n\n\n \u201cWe are already agile, we do daily standups \u2013 so, we do not need any training. Just tell us how to improve productivity.\u201d<\/p>\n\n\n\n Similarly, there are many misconceptions about DevOps. When asked what is your DevOps approach.<\/p>\n\n\n\n \u2013 We use Chef\/Puppet<\/p>\n\n\n\n \u2013 We have a CI\/CD pipeline [use Jenkins]<\/p>\n\n\n\n \u2013 We deploy to the cloud etc.<\/p>\n\n\n\n While DevOps is also considered as a significant cultural approach, there are many aspects that contribute to deriving the benefits of a cross-functional team working together with the user experience in mind \u2013 which is the spirit of DevOps or the Software Delivery Lifecycle. [See also a related post on this topic<\/a>]<\/p>\n\n\n\n One of the concepts that is not talked about much, is related to immutable infrastructure.<\/p>\n\n\n\n The concept itself is not new. We have heard this in different forms \u2013 most popular is the plug and play model. Just replace a component or add a new component and everything will work well and, in effect, replace the old configuration.<\/p>\n\n\n\n Usually, when we upgrade applications as patches, new features etc, there is a downtime needed to complete the setup and migration \u2013 as depicted in the top portion of the diagram.<\/p>\n\n\n\n With an immutable approach, the shift is from a \u2018maintained\u2019 infrastructure \u2013 as it would be the case for dedicated data centers, to a \u2018replaceable\u2019 data center, as in the case of a cloud platform.<\/p>\n\n\n\n Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
* Inspirational Communication<\/p>\n\n\n\n * Intellectual Stimulation<\/p>\n\n\n\n * Supportive Leadership and<\/p>\n\n\n\n * Personal Recognition<\/p>\n\n\n\n From my experience with various transformational and organizational excellence initiatives across multiple industries, this is a common success factor. Setting a clear vision and mission and letting the teams take up ownership detail out execution strategies creates a sustainable transformation.<\/p>\n\n\n\n The report also talks of the applicability of DevOps approaches \u2013 which can trace their origins to principles of Lean and Theory of Constraints models \u2013 is not only for the Unicorns, but for all organizations, including ones that have not-so-modern technologies deployed.<\/p>\n\n\n\n Since Lean approaches have been proven in manufacturing companies there are enough examples and patterns that we can adopt in the IT industry context.<\/p>\n\n\n\n The power of autonomy and ownership at a team level are also indicated in the report where one can see a correlation of loosely coupled, autonomous teams that work together with stable, continuous delivery practices.<\/p>\n\n\n\n I want to also highlight the importance of architecture to really derive the benefits of a DevOps transformation. It is no longer sufficient to adopt some tools for automating specific tasks of the software delivery lifecycle, but also the core of the enterprise and application architectures.<\/p>\n\n\n\n This reinforces the approach that I had talked about in an earlier post.<\/a><\/p>\n\n\n\n In summary, this is a well made report that is easy to read and understand.<\/p>\n\n\n\n Even if you have not started your DevOps journey yet, this will be a very useful read!<\/p>\n","post_title":"Some inferences from the State of DevOps 2017 report","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"inferences-state-devops-2017-report","to_ping":"","pinged":"","post_modified":"2024-01-29 12:00:04","post_modified_gmt":"2024-01-29 12:00:04","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7334","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7337,"post_author":"30","post_date":"2017-01-28 14:31:15","post_date_gmt":"2017-01-28 09:01:15","post_content":"\n Over the many years of my interactions with various projects, the most common misconception that I come across is equating a daily standup to scrum and agile.<\/p>\n\n\n\n In such situations, the conversations invariably start something like this:<\/p>\n\n\n\n \u201cWe are already agile, we do daily standups \u2013 so, we do not need any training. Just tell us how to improve productivity.\u201d<\/p>\n\n\n\n Similarly, there are many misconceptions about DevOps. When asked what is your DevOps approach.<\/p>\n\n\n\n \u2013 We use Chef\/Puppet<\/p>\n\n\n\n \u2013 We have a CI\/CD pipeline [use Jenkins]<\/p>\n\n\n\n \u2013 We deploy to the cloud etc.<\/p>\n\n\n\n While DevOps is also considered as a significant cultural approach, there are many aspects that contribute to deriving the benefits of a cross-functional team working together with the user experience in mind \u2013 which is the spirit of DevOps or the Software Delivery Lifecycle. [See also a related post on this topic<\/a>]<\/p>\n\n\n\n One of the concepts that is not talked about much, is related to immutable infrastructure.<\/p>\n\n\n\n The concept itself is not new. We have heard this in different forms \u2013 most popular is the plug and play model. Just replace a component or add a new component and everything will work well and, in effect, replace the old configuration.<\/p>\n\n\n\n Usually, when we upgrade applications as patches, new features etc, there is a downtime needed to complete the setup and migration \u2013 as depicted in the top portion of the diagram.<\/p>\n\n\n\n With an immutable approach, the shift is from a \u2018maintained\u2019 infrastructure \u2013 as it would be the case for dedicated data centers, to a \u2018replaceable\u2019 data center, as in the case of a cloud platform.<\/p>\n\n\n\n Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
* Vision<\/p>\n\n\n\n * Inspirational Communication<\/p>\n\n\n\n * Intellectual Stimulation<\/p>\n\n\n\n * Supportive Leadership and<\/p>\n\n\n\n * Personal Recognition<\/p>\n\n\n\n From my experience with various transformational and organizational excellence initiatives across multiple industries, this is a common success factor. Setting a clear vision and mission and letting the teams take up ownership detail out execution strategies creates a sustainable transformation.<\/p>\n\n\n\n The report also talks of the applicability of DevOps approaches \u2013 which can trace their origins to principles of Lean and Theory of Constraints models \u2013 is not only for the Unicorns, but for all organizations, including ones that have not-so-modern technologies deployed.<\/p>\n\n\n\n Since Lean approaches have been proven in manufacturing companies there are enough examples and patterns that we can adopt in the IT industry context.<\/p>\n\n\n\n The power of autonomy and ownership at a team level are also indicated in the report where one can see a correlation of loosely coupled, autonomous teams that work together with stable, continuous delivery practices.<\/p>\n\n\n\n I want to also highlight the importance of architecture to really derive the benefits of a DevOps transformation. It is no longer sufficient to adopt some tools for automating specific tasks of the software delivery lifecycle, but also the core of the enterprise and application architectures.<\/p>\n\n\n\n This reinforces the approach that I had talked about in an earlier post.<\/a><\/p>\n\n\n\n In summary, this is a well made report that is easy to read and understand.<\/p>\n\n\n\n Even if you have not started your DevOps journey yet, this will be a very useful read!<\/p>\n","post_title":"Some inferences from the State of DevOps 2017 report","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"inferences-state-devops-2017-report","to_ping":"","pinged":"","post_modified":"2024-01-29 12:00:04","post_modified_gmt":"2024-01-29 12:00:04","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7334","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7337,"post_author":"30","post_date":"2017-01-28 14:31:15","post_date_gmt":"2017-01-28 09:01:15","post_content":"\n Over the many years of my interactions with various projects, the most common misconception that I come across is equating a daily standup to scrum and agile.<\/p>\n\n\n\n In such situations, the conversations invariably start something like this:<\/p>\n\n\n\n \u201cWe are already agile, we do daily standups \u2013 so, we do not need any training. Just tell us how to improve productivity.\u201d<\/p>\n\n\n\n Similarly, there are many misconceptions about DevOps. When asked what is your DevOps approach.<\/p>\n\n\n\n \u2013 We use Chef\/Puppet<\/p>\n\n\n\n \u2013 We have a CI\/CD pipeline [use Jenkins]<\/p>\n\n\n\n \u2013 We deploy to the cloud etc.<\/p>\n\n\n\n While DevOps is also considered as a significant cultural approach, there are many aspects that contribute to deriving the benefits of a cross-functional team working together with the user experience in mind \u2013 which is the spirit of DevOps or the Software Delivery Lifecycle. [See also a related post on this topic<\/a>]<\/p>\n\n\n\n One of the concepts that is not talked about much, is related to immutable infrastructure.<\/p>\n\n\n\n The concept itself is not new. We have heard this in different forms \u2013 most popular is the plug and play model. Just replace a component or add a new component and everything will work well and, in effect, replace the old configuration.<\/p>\n\n\n\n Usually, when we upgrade applications as patches, new features etc, there is a downtime needed to complete the setup and migration \u2013 as depicted in the top portion of the diagram.<\/p>\n\n\n\n With an immutable approach, the shift is from a \u2018maintained\u2019 infrastructure \u2013 as it would be the case for dedicated data centers, to a \u2018replaceable\u2019 data center, as in the case of a cloud platform.<\/p>\n\n\n\n Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
The report talks of five common characteristics shared by transformational leaders that have been correlated to high performing teams and organizations. These include<\/p>\n\n\n\n * Vision<\/p>\n\n\n\n * Inspirational Communication<\/p>\n\n\n\n * Intellectual Stimulation<\/p>\n\n\n\n * Supportive Leadership and<\/p>\n\n\n\n * Personal Recognition<\/p>\n\n\n\n From my experience with various transformational and organizational excellence initiatives across multiple industries, this is a common success factor. Setting a clear vision and mission and letting the teams take up ownership detail out execution strategies creates a sustainable transformation.<\/p>\n\n\n\n The report also talks of the applicability of DevOps approaches \u2013 which can trace their origins to principles of Lean and Theory of Constraints models \u2013 is not only for the Unicorns, but for all organizations, including ones that have not-so-modern technologies deployed.<\/p>\n\n\n\n Since Lean approaches have been proven in manufacturing companies there are enough examples and patterns that we can adopt in the IT industry context.<\/p>\n\n\n\n The power of autonomy and ownership at a team level are also indicated in the report where one can see a correlation of loosely coupled, autonomous teams that work together with stable, continuous delivery practices.<\/p>\n\n\n\n I want to also highlight the importance of architecture to really derive the benefits of a DevOps transformation. It is no longer sufficient to adopt some tools for automating specific tasks of the software delivery lifecycle, but also the core of the enterprise and application architectures.<\/p>\n\n\n\n This reinforces the approach that I had talked about in an earlier post.<\/a><\/p>\n\n\n\n In summary, this is a well made report that is easy to read and understand.<\/p>\n\n\n\n Even if you have not started your DevOps journey yet, this will be a very useful read!<\/p>\n","post_title":"Some inferences from the State of DevOps 2017 report","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"inferences-state-devops-2017-report","to_ping":"","pinged":"","post_modified":"2024-01-29 12:00:04","post_modified_gmt":"2024-01-29 12:00:04","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7334","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7337,"post_author":"30","post_date":"2017-01-28 14:31:15","post_date_gmt":"2017-01-28 09:01:15","post_content":"\n Over the many years of my interactions with various projects, the most common misconception that I come across is equating a daily standup to scrum and agile.<\/p>\n\n\n\n In such situations, the conversations invariably start something like this:<\/p>\n\n\n\n \u201cWe are already agile, we do daily standups \u2013 so, we do not need any training. Just tell us how to improve productivity.\u201d<\/p>\n\n\n\n Similarly, there are many misconceptions about DevOps. When asked what is your DevOps approach.<\/p>\n\n\n\n \u2013 We use Chef\/Puppet<\/p>\n\n\n\n \u2013 We have a CI\/CD pipeline [use Jenkins]<\/p>\n\n\n\n \u2013 We deploy to the cloud etc.<\/p>\n\n\n\n While DevOps is also considered as a significant cultural approach, there are many aspects that contribute to deriving the benefits of a cross-functional team working together with the user experience in mind \u2013 which is the spirit of DevOps or the Software Delivery Lifecycle. [See also a related post on this topic<\/a>]<\/p>\n\n\n\n One of the concepts that is not talked about much, is related to immutable infrastructure.<\/p>\n\n\n\n The concept itself is not new. We have heard this in different forms \u2013 most popular is the plug and play model. Just replace a component or add a new component and everything will work well and, in effect, replace the old configuration.<\/p>\n\n\n\n Usually, when we upgrade applications as patches, new features etc, there is a downtime needed to complete the setup and migration \u2013 as depicted in the top portion of the diagram.<\/p>\n\n\n\n With an immutable approach, the shift is from a \u2018maintained\u2019 infrastructure \u2013 as it would be the case for dedicated data centers, to a \u2018replaceable\u2019 data center, as in the case of a cloud platform.<\/p>\n\n\n\n Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Some highlights from the report this year are significant from an organizational maturity and transformation perspective.<\/p>\n\n\n\n The report talks of five common characteristics shared by transformational leaders that have been correlated to high performing teams and organizations. These include<\/p>\n\n\n\n * Vision<\/p>\n\n\n\n * Inspirational Communication<\/p>\n\n\n\n * Intellectual Stimulation<\/p>\n\n\n\n * Supportive Leadership and<\/p>\n\n\n\n * Personal Recognition<\/p>\n\n\n\n From my experience with various transformational and organizational excellence initiatives across multiple industries, this is a common success factor. Setting a clear vision and mission and letting the teams take up ownership detail out execution strategies creates a sustainable transformation.<\/p>\n\n\n\n The report also talks of the applicability of DevOps approaches \u2013 which can trace their origins to principles of Lean and Theory of Constraints models \u2013 is not only for the Unicorns, but for all organizations, including ones that have not-so-modern technologies deployed.<\/p>\n\n\n\n Since Lean approaches have been proven in manufacturing companies there are enough examples and patterns that we can adopt in the IT industry context.<\/p>\n\n\n\n The power of autonomy and ownership at a team level are also indicated in the report where one can see a correlation of loosely coupled, autonomous teams that work together with stable, continuous delivery practices.<\/p>\n\n\n\n I want to also highlight the importance of architecture to really derive the benefits of a DevOps transformation. It is no longer sufficient to adopt some tools for automating specific tasks of the software delivery lifecycle, but also the core of the enterprise and application architectures.<\/p>\n\n\n\n This reinforces the approach that I had talked about in an earlier post.<\/a><\/p>\n\n\n\n In summary, this is a well made report that is easy to read and understand.<\/p>\n\n\n\n Even if you have not started your DevOps journey yet, this will be a very useful read!<\/p>\n","post_title":"Some inferences from the State of DevOps 2017 report","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"inferences-state-devops-2017-report","to_ping":"","pinged":"","post_modified":"2024-01-29 12:00:04","post_modified_gmt":"2024-01-29 12:00:04","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7334","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7337,"post_author":"30","post_date":"2017-01-28 14:31:15","post_date_gmt":"2017-01-28 09:01:15","post_content":"\n Over the many years of my interactions with various projects, the most common misconception that I come across is equating a daily standup to scrum and agile.<\/p>\n\n\n\n In such situations, the conversations invariably start something like this:<\/p>\n\n\n\n \u201cWe are already agile, we do daily standups \u2013 so, we do not need any training. Just tell us how to improve productivity.\u201d<\/p>\n\n\n\n Similarly, there are many misconceptions about DevOps. When asked what is your DevOps approach.<\/p>\n\n\n\n \u2013 We use Chef\/Puppet<\/p>\n\n\n\n \u2013 We have a CI\/CD pipeline [use Jenkins]<\/p>\n\n\n\n \u2013 We deploy to the cloud etc.<\/p>\n\n\n\n While DevOps is also considered as a significant cultural approach, there are many aspects that contribute to deriving the benefits of a cross-functional team working together with the user experience in mind \u2013 which is the spirit of DevOps or the Software Delivery Lifecycle. [See also a related post on this topic<\/a>]<\/p>\n\n\n\n One of the concepts that is not talked about much, is related to immutable infrastructure.<\/p>\n\n\n\n The concept itself is not new. We have heard this in different forms \u2013 most popular is the plug and play model. Just replace a component or add a new component and everything will work well and, in effect, replace the old configuration.<\/p>\n\n\n\n Usually, when we upgrade applications as patches, new features etc, there is a downtime needed to complete the setup and migration \u2013 as depicted in the top portion of the diagram.<\/p>\n\n\n\n With an immutable approach, the shift is from a \u2018maintained\u2019 infrastructure \u2013 as it would be the case for dedicated data centers, to a \u2018replaceable\u2019 data center, as in the case of a cloud platform.<\/p>\n\n\n\n Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure you can read it online at the author\u2019s company site<\/a>.<\/p>\n\n\n\n If you have created any tools for doing this, or have some experience \u2013 good or not so good \u2013 please share for the benefit of the others.<\/p>\n","post_title":"Immutable infrastructure","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"immutable-infrastructure","to_ping":"","pinged":"","post_modified":"2024-01-29 12:01:36","post_modified_gmt":"2024-01-29 12:01:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7337","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":4083,"post_author":"30","post_date":"2016-01-12 11:33:44","post_date_gmt":"2016-01-12 06:03:44","post_content":"\n This is probably the most frequently asked question that I have received.<\/p>\n\n\n\n In many sessions when I introduce the concept of DevOps and some characteristics, after the first 30 minutes or so, the question is a variation of:<\/p>\n\n\n\n - We are already agile. all this sounds just like agile. how is it different and why do we need DevOps<\/p>\n\n\n\n The simple answer is Yes and No.<\/p>\n\n\n\n First the Yes part \u2013 similarities:<\/p>\n\n\n\n Both Agle and DevOps have their origins from Lean thinking, that has been well embraced in manufacturing activities.<\/p>\n\n\n\n Both approaches encourage a minimalistic view to design and deliver, but in an incremental manner.<\/p>\n\n\n\n Here, when I say Agile, I include both the governance framework [Scrum] as well as the good engineering practices [XP], though the popular label of agile is applied to teams that follow [portions] of Scrum!<\/p>\n\n\n\n Now, for the No part:<\/p>\n\n\n\n DevOps is more of an organizational agility approach.<\/p>\n\n\n\n DevOps is a cross functional movement, aimed at maximizing the value delivered to customers. It builds on other techniques and frameworks available, without imposing any prescriptive ways to implement them. However, organizations are free to look at a mix and match of practices and tools and put them together so that all activitie across the full applcation lfecycle can be connected and work smoothly.<\/p>\n\n\n\n In one sense it may also be considered as DevOps extending the scope of the lifecycle from Requirements [backlog] that can be considered one step before the product planning, to the deployment activitiy that has typically been much after the dev team has completed their development activities.<\/p>\n\n\n\n Techniques and standards such as Scrum, Kanban [or a combination \u2013 Scrumban], Lean, ITIL etc all continue to have significant roles in the DevOps view of the value flow.<\/p>\n\n\n\n A successful DevOps adoption requires aspects of people, process and technology all the be addressed in a balanced manner.<\/p>\n\n\n\n When all contributing teams and individuals are all aligned to the requirements from the customer, many internal iefficiencies in organizations get addressed.<\/p>\n\n\n\n The softer aspects as well as enterprise architecture requirements become more prominent in a DevOps team.<\/p>\n\n\n\n Taking a DevOps approach will influence many current systems and practices \u2013 including: target setting, planning and tracking, rewards and recognition [based on shared goals and achievements], architecture, automation of SDLC activities.<\/p>\n\n\n\n To summarize, while there may be common origins and intent, similarity in some of the adoption approches, DevOps addresses some of the basic organizational aspects of structure, flows etc while Agile typically has looked at improving the software development activities.<\/p>\n","post_title":"Is DevOps = Agile++?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"is-devops-agile","to_ping":"","pinged":"","post_modified":"2024-01-29 12:12:36","post_modified_gmt":"2024-01-29 12:12:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=4083","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Over the years this report has been getting better in terms of the depth and also the analysis.<\/p>\n\n\n\n Some highlights from the report this year are significant from an organizational maturity and transformation perspective.<\/p>\n\n\n\n The report talks of five common characteristics shared by transformational leaders that have been correlated to high performing teams and organizations. These include<\/p>\n\n\n\n * Vision<\/p>\n\n\n\n * Inspirational Communication<\/p>\n\n\n\n * Intellectual Stimulation<\/p>\n\n\n\n * Supportive Leadership and<\/p>\n\n\n\n * Personal Recognition<\/p>\n\n\n\n From my experience with various transformational and organizational excellence initiatives across multiple industries, this is a common success factor. Setting a clear vision and mission and letting the teams take up ownership detail out execution strategies creates a sustainable transformation.<\/p>\n\n\n\n The report also talks of the applicability of DevOps approaches \u2013 which can trace their origins to principles of Lean and Theory of Constraints models \u2013 is not only for the Unicorns, but for all organizations, including ones that have not-so-modern technologies deployed.<\/p>\n\n\n\n Since Lean approaches have been proven in manufacturing companies there are enough examples and patterns that we can adopt in the IT industry context.<\/p>\n\n\n\n The power of autonomy and ownership at a team level are also indicated in the report where one can see a correlation of loosely coupled, autonomous teams that work together with stable, continuous delivery practices.<\/p>\n\n\n\n I want to also highlight the importance of architecture to really derive the benefits of a DevOps transformation. It is no longer sufficient to adopt some tools for automating specific tasks of the software delivery lifecycle, but also the core of the enterprise and application architectures.<\/p>\n\n\n\n This reinforces the approach that I had talked about in an earlier post.<\/a><\/p>\n\n\n\n In summary, this is a well made report that is easy to read and understand.<\/p>\n\n\n\n Even if you have not started your DevOps journey yet, this will be a very useful read!<\/p>\n","post_title":"Some inferences from the State of DevOps 2017 report","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"inferences-state-devops-2017-report","to_ping":"","pinged":"","post_modified":"2024-01-29 12:00:04","post_modified_gmt":"2024-01-29 12:00:04","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7334","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":7337,"post_author":"30","post_date":"2017-01-28 14:31:15","post_date_gmt":"2017-01-28 09:01:15","post_content":"\n Over the many years of my interactions with various projects, the most common misconception that I come across is equating a daily standup to scrum and agile.<\/p>\n\n\n\n In such situations, the conversations invariably start something like this:<\/p>\n\n\n\n \u201cWe are already agile, we do daily standups \u2013 so, we do not need any training. Just tell us how to improve productivity.\u201d<\/p>\n\n\n\n Similarly, there are many misconceptions about DevOps. When asked what is your DevOps approach.<\/p>\n\n\n\n \u2013 We use Chef\/Puppet<\/p>\n\n\n\n \u2013 We have a CI\/CD pipeline [use Jenkins]<\/p>\n\n\n\n \u2013 We deploy to the cloud etc.<\/p>\n\n\n\n While DevOps is also considered as a significant cultural approach, there are many aspects that contribute to deriving the benefits of a cross-functional team working together with the user experience in mind \u2013 which is the spirit of DevOps or the Software Delivery Lifecycle. [See also a related post on this topic<\/a>]<\/p>\n\n\n\n One of the concepts that is not talked about much, is related to immutable infrastructure.<\/p>\n\n\n\n The concept itself is not new. We have heard this in different forms \u2013 most popular is the plug and play model. Just replace a component or add a new component and everything will work well and, in effect, replace the old configuration.<\/p>\n\n\n\n Usually, when we upgrade applications as patches, new features etc, there is a downtime needed to complete the setup and migration \u2013 as depicted in the top portion of the diagram.<\/p>\n\n\n\n With an immutable approach, the shift is from a \u2018maintained\u2019 infrastructure \u2013 as it would be the case for dedicated data centers, to a \u2018replaceable\u2019 data center, as in the case of a cloud platform.<\/p>\n\n\n\n Traditionally, provisioning infrastructure from the scratch is a more time consuming activity compared to patching or mutating an existing infrastructure. That has made the latter approach more popular.<\/p>\n\n\n\n However this has a potential side effect of unpredictable application behavior, since there could be differences between the production environment and the development or test\/staging set ups.<\/p>\n\n\n\n Immutable infrastructure is a collection of components where the infrastructure is closed for modifications, but open for recreation and expansion.<\/p>\n\n\n\n The significant benefits are predictability and the ability to fail fast, if you have to!<\/p>\n\n\n\n On cloud platforms, changes to the resources are pretty much a simple command or API call.<\/p>\n\n\n\n Immutable does not mean that nothing changes. It is just that the evolution can be better managed with reduced disruptions.<\/p>\n\n\n\n Martin Fowler wrote in a July 2012 blog post titled \u201cPhoenixServer\u201d: It is almost like in-situ renovation.<\/p>\n\n\n\n In order to do this, the application[s] should inherently be able to handle this. Stateful applications [for special applications] and multi-data center deployments could add additional challenges, but none of them unmanageable.<\/p>\n\n\n\n More careful planning and automation can help make the upgrades smooth. If the underlying architecture is more API based or service oriented \u2013 in other words, based on high cohesion and loose coupling, managing some of these changes will become simpler.<\/p>\n\n\n\n This approach could be an overkill, if you manage a fairly simple application running on a few dedicated servers. If you are already on the cloud, you may already be leveraging the facilities of the service provider.<\/p>\n\n\n\n But, if you anticipate the application to evolve into a large one, building an immutable infrastructure in parallel, even during the time of development may benefit in the long-run, to scale out and also detect failure more easily.<\/p>\n\n\n\n Virtualization [and microservices] will help you replace old images, as suggested by an immutable approach.<\/p>\n\n\n\n If you want to take baby steps towards this, you can start with the blue\/green model<\/a>.<\/p>\n\n\n\n Have 2 infrastructures, one that is live and the other that could be just standing by. Again, build the heartbeat or replication features in the architecture, particularly to handle any degradation in production, gracefully.<\/p>\n\n\n\n If you are ready to experiment, inspect and adapt, a good reference to read is:<\/p>\n\n\n\n Immutable Infrastructure
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n
[ \u2026 ], it is a good idea to virtually burn down your servers at regular intervals. A server should be like a phoenix, regularly rising from the ashes.<\/p>\n\n\n\n
by Josha Stella,
Copyright \u00a9 2016 O\u2019Reilly Media, Inc.<\/p>\n\n\n\n