agile communication

The world is getting “more agile” — or let’s say carefully … it wants to become more agile. That’s challenge enough. But why agile commu­ni­ca­tion at the same time? I have got used to the aston­ished eyes of some customers when I explain that agility is above all a matter of attitude. Agility is not something I can simply “work through”, I have to live agility.

Agile mindset means closer to the customer —
Agile communication means closer to the communication partner

The founders of the concept clearly defined the basic idea of agile work in their “Agile Manifesto”. Even though its origins lie in software devel­op­ment, it is also the basis for work in other fields of devel­op­ment and service.
At least 2 of the 4 princi­ples of the agile manifesto focus on cooper­a­tion and the human being — and thus on commu­ni­ca­tion.

  • Individ­uals and inter­ac­tions - stand above processes and tools
  • Functioning software [/ functioning products / satis­fac­tory service] — stands above compre­hen­sive documen­ta­tion
  • Cooper­a­tion with the customerstands above contract negoti­a­tion
  • Reaction to change - stands above following a plan

A prior­i­ti­za­tion that requires a rethink for many estab­lished and familiar processes — just a different attitude.
It is this combi­na­tion of attitude (mindset) and the appro­priate agile methods through which the agile concept unfolds its benefits.

Impor­tant pillars of agility are customer proximity and teamwork. All partic­i­pants are in constant exchange with each other — that means commu­ni­ca­tion is omnipresent: commu­ni­cate when there is something to specify; commu­ni­cate when there are questions; commu­ni­cate when there are problems; commu­ni­cate when you need support; …

The seconds sprint of agile communication

Agile commu­ni­ca­tion is similar to agile methods like Scrum. As with Scrum, agile commu­ni­ca­tion works in incre­ments:

WHAT (which messages) do I want to convey [Scrum: Product Backlog]

HOW do I reach my inter­locu­tors (WHEN) so that they listen to me openly [Scrum: Sprint Planning and Backlog]?

agile communicationCOMMUNICATE [Scrum: Sprint Backlog, Create Incre­ment]

CHECK, has my message arrived? Findings from the reaction to my commu­ni­ca­tion? [Scrum: Daily Scrum, Sprint Review]

SELF STREFLEKTION, what can I person­ally improve in my commu­ni­ca­tion? [Scrum: Sprint Retro­spec­tive]

FURTHER, if the commu­ni­ca­tion was successful: Super, next step! [Scrum: next entry from the product backlog]
- if the commu­ni­ca­tion was not successful: no problem, with the findings from “CHECK” again in the “HOW” [Scrum: with the same product backlog and new knowl­edge again in the Sprint]

The differ­ence to Scrum lies in the speed. A sprint with Scrum lasts up to 30 days — an agile commu­ni­ca­tion sprint rarely takes more than a few seconds.

Agile commu­ni­ca­tion means: to design the commu­ni­ca­tion from second to second in order to create a positive and effec­tive environ­ment with the commu­ni­ca­tion partner. This requires mindful­ness: has my message been received? Do I experi­ence positive or negative conflict behav­iour? Is my commu­ni­ca­tion partner in an OK-OK attitude? Am I in an OK-OK attitude? Do I see drivers or distress behavior? How can I shape the commu­ni­ca­tion process?
And all this in a few seconds? Sounds challenging? — You can train! Who knows which signals are relevant in commu­ni­ca­tion, can optimize his own commu­ni­ca­tion in agile steps and is efficient according to the situa­tion.

#Process­Com­mu­ni­ca­tion­Model®  #Leadin­gOut­Of­Drama®

Process Communication Model LogoRecog­nize signals, under­stand use
- Reach person­al­i­ties

Leading Out of Drama LogoFrom polyphony to the next step —
from positive conflicts to innova­tions

Pin It on Pinterest

Share This