{"id":711,"date":"2020-06-07T19:06:34","date_gmt":"2020-06-07T17:06:34","guid":{"rendered":"https:\/\/metaworks.eu\/wordpress\/?p=711"},"modified":"2020-06-07T19:06:34","modified_gmt":"2020-06-07T17:06:34","slug":"the-physics-of-agile-methodologies-and-how-our-vocabulary-creates-unnecessary-entry-barriers","status":"publish","type":"post","link":"https:\/\/metaworks.eu\/wordpress\/the-physics-of-agile-methodologies-and-how-our-vocabulary-creates-unnecessary-entry-barriers\/","title":{"rendered":"The Physics of Agile Methodologies…and how our vocabulary creates unnecessary entry barriers"},"content":{"rendered":"\n
\"\"<\/figure><\/div>\n\n\n\n

In the course of many consultancy gigs and trainings, I had the opportunity to work with people from many different cultural and professional backgrounds. While there are quite a few opportunities for little culture clashes (e.g. the perceived duration of 5 minutes), most of the people I work with share a common perception:<\/p>\n\n\n\n

The terminology we use in Agile Methods is nerdy, and far from the language \u201cnormal people\u201d would use.<\/strong> This might be a first clue that we might be using terminology to separate those in the know from laymen. <\/p>\n\n\n\n

Agile is for the people who work with it, not for the consultants.<\/p><\/blockquote>\n\n\n\n

This is not what Agile methods are about, and there is no need to use awkward terms to come across scientific. Agile is for the people who work with it, not for the consultants…so, no need for it to come across as an actual science. Let\u2019s de-science our vocabulary. Simpler words will help making Agile Methods more accessible, which in turn will allow for a more widespread adoption, even with non-techy teams.<\/p>\n\n\n\n

Imagine a purely non-technical team. Not software engineering, no DevOps, just a normal crew trying to get things done, say…Office Management. Let\u2019s call it the A-Team<\/em>, and they are looking for some way to improve their daily work. The A-Team is also looking for ways to add transparency for their team and their internal customers.<\/p>\n\n\n\n

Assuming a lucky coincidence, they arranged to meet with their friendly neighborhood Agile Coach. <\/p>\n\n\n\n

(brief pause for tension)<\/p>\n\n\n\n

After the meeting, all team members and the coach have confused looks on their faces. The team is numbed by funny words like iteration<\/em> and information radiator<\/em>. They also wonder what their velocity<\/em> might be, as they usually just sit at their desks? In this meeting, there was no actual communication going on, since the vocabulary was new.<\/p>\n\n\n\n

Having said that, I\u2019d like to give some example of Agile terms which could be expressed in non-techy ways.<\/p>\n\n\n\n

Sprints, Iterations and Inspect&Adapt<\/h3>\n\n\n\n

I\u2019ll start with that one, as the basic principle of \u201citerating\u201d towards our ever-changing goals is the cornerstone of anything we might call Agile. However, the bus near my house is neither sprinting nor iterating, and kids don\u2019t inspect&adapt their way towards being able to draw awesome pics of airplanes.<\/p>\n\n\n\n

So how about using simpler terms like \u201cRepetition<\/em>\u201d or \u201cSchedule<\/em>\u201d?
Therefore, in the course of several repetitions, we use \u201cTrial and Error<\/em>\u201d to achieve a result.<\/p>\n\n\n\n

Increment<\/h3>\n\n\n\n

At the end of an iteration, we\u2019re supposed to come up with a product increment<\/em>. The underlying idea is that we do not just write code, but a healthy team will come up with a usable product increment. Tested. Documented. Integrated. Shipped. <\/p>\n\n\n\n

But then, have you ever heard your neighbors bragging about their latest increment<\/em> to the house?<\/p>\n\n\n\n

Here, a more accessible term would be \u201cextension<\/em>\u201d or \u201caddition<\/em>\u201d.
\u201cAt the end of each repetition, we are able to present an addition to our product.\u201d<\/em><\/p>\n\n\n\n

Velocity and Cadence<\/h3>\n\n\n\n

These terms are physics at its best (yes I am aware that cadence<\/em> is also used in music). While the terms themselves are uber-precise, they immediately lead to an anaphylactic shock with everybody who is more Penny than Sheldon.<\/p>\n\n\n\n

Therefore, we could just as well use the term \u201cspeed<\/em>\u201d and achieve the same semantics:
\u201cAt the current speed, we need 6 repetitions to be ready.\u201d<\/em><\/p>\n\n\n\n

Information Radiation<\/h3>\n\n\n\n

An Information Radiator<\/em> is any kind of analogue or digital display, which is constantly showing project status information. You\u2019ll find these in the team room or near the coffee maker, and they serve to keep the team focused and relieve them of unnecessary status meetings.<\/p>\n\n\n\n

I suggest to stick with the analogy of \u201cheating\u201d, but use a simpler term: \u201cThe team room is hot with information\u201d.<\/em><\/p>\n\n\n\n

Value Streams, Information Flow and Theory of Constraints<\/h3>\n\n\n\n

These terms arent\u2019t really from any Agile methodology. However, with higher maturity levels, I invite teams to address their information flow, its visualization and maybe all the jams<\/em> or congestions<\/em>.<\/p>\n\n\n\n

Newton\u2019s 3rd Law of Motion<\/h3>\n\n\n\n

You got me, I sneaked this one in – it\u2019s not a term used anywhere in the Agile software development literature, so consequently it won\u2019t appear in the overview table below.<\/p>\n\n\n\n

However, I observed this in multiple change management projects…a behaviour which can be phrased as Newton\u2019s Third Law of Motion: For every action, there is an equal and opposite reaction. In simpler terms, we are \u201cpushing against a wall<\/em>\u201d.<\/p>\n\n\n\n

These are just a few examples of technical terms being used in a field that is particularly about individuals working together.<\/p>\n\n\n\n

This brief article serves as a conversation starter<\/em> towards a better vocabulary. Once we un-nerded our vocabulary, there will be less friction<\/em> (wink, wink) in the adoption of Agile methods by non-technical teams.<\/p>\n\n\n\n

Term<\/strong><\/td>Alternative Term Suggestion<\/strong><\/td><\/tr>
Sprint\/Iteration<\/td>Repetition\/Schedule<\/td><\/tr>
Inspect&Adapt<\/td>Trial&Error<\/td><\/tr>
Increment<\/td>Extension\/Addition<\/td><\/tr>
Velocity\/Cadence<\/td>Speed<\/td><\/tr>
Information Radiation<\/td>Hot\/Cold Environment<\/td><\/tr>
Constraint<\/td>Jam\/Congestion<\/td><\/tr><\/tbody><\/table><\/figure>\n","protected":false},"excerpt":{"rendered":"

The terminology we use in Agile Methods is nerdy, and far from the language \u201cnormal people\u201d would use. Agile is for the people who work with it, not for the consultants, so let\u2019s de-science our vocabulary. Simpler words will help making Agile Methods more accessible, which in turn will allow for a more widespread adoption, even with non-techy teams.<\/p>\n","protected":false},"author":1,"featured_media":712,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[45],"tags":[73,25,26,28],"class_list":["post-711","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-change-management","tag-agile-adoption","tag-agile-methods","tag-change-management","tag-learning","entry","has-media"],"_links":{"self":[{"href":"https:\/\/metaworks.eu\/wordpress\/wp-json\/wp\/v2\/posts\/711","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/metaworks.eu\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/metaworks.eu\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/metaworks.eu\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/metaworks.eu\/wordpress\/wp-json\/wp\/v2\/comments?post=711"}],"version-history":[{"count":1,"href":"https:\/\/metaworks.eu\/wordpress\/wp-json\/wp\/v2\/posts\/711\/revisions"}],"predecessor-version":[{"id":713,"href":"https:\/\/metaworks.eu\/wordpress\/wp-json\/wp\/v2\/posts\/711\/revisions\/713"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/metaworks.eu\/wordpress\/wp-json\/wp\/v2\/media\/712"}],"wp:attachment":[{"href":"https:\/\/metaworks.eu\/wordpress\/wp-json\/wp\/v2\/media?parent=711"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/metaworks.eu\/wordpress\/wp-json\/wp\/v2\/categories?post=711"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/metaworks.eu\/wordpress\/wp-json\/wp\/v2\/tags?post=711"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}