{"id":561,"date":"2016-02-01T16:20:07","date_gmt":"2016-02-01T16:20:07","guid":{"rendered":"http:\/\/johnkendrick.com\/blog\/?p=561"},"modified":"2016-02-01T16:20:07","modified_gmt":"2016-02-01T16:20:07","slug":"agile-isnt-a-process-or-even-a-methodology-its-a-type-of-person-kanban-scrum-retrospective","status":"publish","type":"post","link":"http:\/\/johnkendrick.com\/blog\/2016\/02\/agile-isnt-a-process-or-even-a-methodology-its-a-type-of-person-kanban-scrum-retrospective\/","title":{"rendered":"#Agile isn&rsquo;t a process, or even a methodology, its a type of person #Kanban #SCRUM #Retrospective"},"content":{"rendered":"<p>Over the last few years I have worked on implementing Agile.&nbsp; This is quite different to using an pre-existing Agile process or template.&nbsp; Its also very different to getting involved in an Agile team that already up and running.&nbsp; Building Agile from the ground up is not something people do very often \u2013 and worse than that, if they do, they don\u2019t do it very well.<\/p>\n<p>In part, there is a responsibility of success on the person leading the team \u2013 they need to be able to absorb new ways of status reporting, change control, etc (see my article on the <a href=\"http:\/\/johnkendrick.com\/blog\/2015\/09\/can-you-handle-the-brutality-of-the-glass-office-agile-scrum-kanban-tfs-jira-ripplerock\/\" target=\"_blank\">Glass Office<\/a>).&nbsp; But, crucially, a vast majority of success is actually down to the people who are in the team.&nbsp; One of the Agile secrets that isn\u2019t very well known or widely published (<em>someone called it a dirty secret to me recently<\/em>) is that its actually down to the type of person in the team.<\/p>\n<p>Agile is based on a premise of understand what the outcome is, then work out what is the most acceptable way of achieving that outcome, note down how you will measure if you have made the outcome and then go do it.&nbsp; As you work on the method of the outcome, then you continuously care about improvement on the way you do it.&nbsp; You care about the outcome, you care about quality, you care about learning and wanting to understand new methods and ways of improving yourself.<\/p>\n<p>Agile will not work if you don\u2019t have a team or group of people who are willing to adapt and try new things and ways of working.&nbsp; Without a \u201clets see if it works\u201d mentality the team will never be successful.&nbsp; Retrospectives and CI (Continuous Improvement) are threaded through all of the Agile work \u2013 you have to be able to try new things and see if they add value or not.&nbsp; You have to be able to look at your current way of working and see if you can improve it&#8230;<\/p>\n<p>For Agile to be successful you need a group of people are willing to adapt and learn and try new things.&nbsp; They mustn\u2019t be afraid of failure and they must <strong><u>never<\/u><\/strong> be afraid of change.<\/p>\n<p>Getting the right kind of team, and this extends out to the user community as well as the delivery team, is key to success.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Over the last few years I have worked on implementing Agile.&nbsp; This is quite different to using an pre-existing Agile process or template.&nbsp; Its also very different to getting involved in an Agile team that already up and running.&nbsp; Building Agile from the ground up is not something people do very often \u2013 and worse [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[81,95,82,86],"tags":[],"class_list":["post-561","post","type-post","status-publish","format-standard","hentry","category-agile","category-featured_posts","category-kanban","category-scrum"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p3mjsZ-93","jetpack_sharing_enabled":true,"jetpack_likes_enabled":true,"_links":{"self":[{"href":"http:\/\/johnkendrick.com\/blog\/wp-json\/wp\/v2\/posts\/561","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/johnkendrick.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/johnkendrick.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/johnkendrick.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/johnkendrick.com\/blog\/wp-json\/wp\/v2\/comments?post=561"}],"version-history":[{"count":1,"href":"http:\/\/johnkendrick.com\/blog\/wp-json\/wp\/v2\/posts\/561\/revisions"}],"predecessor-version":[{"id":562,"href":"http:\/\/johnkendrick.com\/blog\/wp-json\/wp\/v2\/posts\/561\/revisions\/562"}],"wp:attachment":[{"href":"http:\/\/johnkendrick.com\/blog\/wp-json\/wp\/v2\/media?parent=561"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/johnkendrick.com\/blog\/wp-json\/wp\/v2\/categories?post=561"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/johnkendrick.com\/blog\/wp-json\/wp\/v2\/tags?post=561"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}