{"id":12298,"date":"2020-04-23T07:45:42","date_gmt":"2020-04-23T12:45:42","guid":{"rendered":"https:\/\/gsb.lat\/continuous-improvement-a-key-success-factor-in-agility\/"},"modified":"2020-04-23T07:45:42","modified_gmt":"2020-04-23T12:45:42","slug":"continuous-improvement-a-key-success-factor-in-agility","status":"publish","type":"post","link":"https:\/\/gsb.lat\/en\/continuous-improvement-a-key-success-factor-in-agility\/","title":{"rendered":"Continuous Improvement: A Key Success Factor in Agility"},"content":{"rendered":"

Continuous Improvement can be defined as a philosophy to improve the processes, services and products of an organization, through techniques and tools, together with the development of a general attitude, which forms the basis for constant inspection, adaptation and continuous improvement.<\/p>\n

Regarding continuous improvement, the Agile Manifesto<\/a> reads, “At regular intervals, the team reflects on how to be more effective and then adjusts and refines its behavior accordingly (…) Continuous attention to technical excellence and good design improves Agility.”<\/p>\n

For this reason, agile frameworks such as Scrum, include at the end of each Sprint the Retrospective<\/a> ceremony, being the outstanding result of this event, the continuous improvement actions agreed by the team to solve their problems or impediments.<\/p>\n

Furthermore, the implementation of continuous improvement follows a cycle (Deming’s continuous improvement cycle<\/a>), where once the improvement action has been identified, it is plan<\/strong> (Plan), will run<\/strong> (Do), it is verified or check<\/strong> its impact on the situation that generated it (Check) and is acts<\/strong> implementing corrective or change actions (Act) whose inspection enters the next cycle.<\/p>\n

Note how Deming’s improvement cycle (1950s), which some call the spiral of continuous improvement<\/a>, involves iterating on hypothetical solutions(experiments<\/strong>) that, according to the results of verification(inspection<\/strong>), are acted upon to adapt<\/strong> processes to new improvements. This enters into a continuous cycle of improvement in the search for technical excellence<\/strong>, which, as you know, is not a point of arrival or goal, but a path.<\/p>\n

Now, some of you may be wondering how, being always so busy, with busy schedules, blocks, problems and daily pressures, can we find room for continuous improvement?<\/p>\n

I am going to open a parenthesis in this thread before proposing an answer to the question, it is about the phases that learning goes through<\/a>.<\/p>\n

There is a lot of information that we don’t even know exists, therefore, we are Unconsciously Incompetent<\/strong>. Then we hear or read about it and we become Incompetent Conscious<\/strong>, and by studying, we understand what certain theories and practices are proposing, and we achieve a Conscious Competence<\/strong>, which means that we understand it but that frequent and constant practice is needed for such knowledge to become Unconscious Knowledge<\/strong>, which is the place where we find our Habits.<\/strong><\/p>\n

\"There<\/div>\n

Habits are activities that we do every day naturally and that do not generate a great effort, and when it comes to changing or creating new habits, this is accompanied by emotions that explain the resistance to change, but that will be a topic for another day.<\/p>\n

Returning to the previous question, the answer could be to make continuous improvement a habit. <\/span><\/em>
\n continuous improvement becomes a habit, a daily practice of the work team, implementing a discipline<\/em>
\n<\/strong>This is a daily practice of the work team, implementing a discipline where little by little they incorporate improvements in their processes.<\/em><\/p>\n

Mar\u00eda Esther Remedios<\/p>\n

@soy.agile.coach<\/p>\n","protected":false},"excerpt":{"rendered":"

Continuous Improvement can be defined as a philosophy to improve the processes, services and products of an organization, through techniques and tools, together with the development of a general attitude, which forms the basis for constant inspection, adaptation and continuous improvement. Regarding continuous improvement, the Agile Manifesto reads, “At regular intervals, the team reflects on…<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[536,539,543],"tags":[],"class_list":["post-12298","post","type-post","status-publish","format-standard","hentry","category-articles","category-gsb-team","category-trends","category-536","category-539","category-543","description-off"],"_links":{"self":[{"href":"https:\/\/gsb.lat\/en\/wp-json\/wp\/v2\/posts\/12298","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/gsb.lat\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/gsb.lat\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/gsb.lat\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/gsb.lat\/en\/wp-json\/wp\/v2\/comments?post=12298"}],"version-history":[{"count":0,"href":"https:\/\/gsb.lat\/en\/wp-json\/wp\/v2\/posts\/12298\/revisions"}],"wp:attachment":[{"href":"https:\/\/gsb.lat\/en\/wp-json\/wp\/v2\/media?parent=12298"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/gsb.lat\/en\/wp-json\/wp\/v2\/categories?post=12298"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/gsb.lat\/en\/wp-json\/wp\/v2\/tags?post=12298"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}