top of page

NM:MN LEARNING AGILE – from BEING agile to DOING agile (1/2)

Part 1) BEING agile


My learning journey with regard to #agility started around 2018. I had just started my studies at the Hernstein Institute in Vienna – eager to deepen my knowledge in the fields of #leadership and #transformation – when I was introduced to the inspiring module of “Leadership 4.0”.

The ingenious Hans-Christian Hiessböck built the topic from scratch:

With him, learning agile - from being agile to doing agile started with the foundation of BEING agile (#agilemindset) and only then continued with insights on DOING agile (#agilepractices and #agilemethods).

✨ I was fascinated by the possibilities that opened up in terms of confronting #complexity with #agility. Thus, I took a deep dive into Frederic Laloux’s “Reinventing Organizations” and dedicated my Master Thesis to “The influence of corporate culture on the introduction of agiles ways of working”.

Details on this adventure are to be told another time…


… for now, join me on my continuous learning journey with regard to #agility.

Next “bus stop”: The pandemic.

Working in the field of MedTech and leading solely in a virtual setting, allowed me to successfully practice “Leadership 4.0” with my team. And I have to say: BEING agile really took #empowerment and #selforganization to the next level.

I was and still am so very proud of my team, back then at the MedTech-Cluster…

In 07/2023 I had the chance to benefit from a boost in theory – attending the “IC Agile Certified Professional” training in 07/2023.

Talking about LEARNING AGILE, these are some of the learnings I took with me:

Derived from the #agilemanifesto, there are 4 #agilevalues which are representing the 1 #agilemindset and which are demonstrated by 12 #agileprinciples… all of this belongs to the foundation of BEING agile.


from BEING agile to DOING agile | #agilevalues

1.      Individuals and interactions over processes and tools

2.      Working software over comprehensive documentation

3.      Customer collaboration over contract negotiation

4.      Responding to change over following a plan


What I love about the phrasing of these values is the term “over” (as opposed to “instead”) – expressing that both are important and it is just a question of prioritization (not of “neglection” such as 0 or 1).


from BEING agile to DOING agile | #agileprinciples

  1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

  2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

  3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

  4. Business people and developers must work together daily throughout the project.

  5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

  6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

  7. Working software is the primary measure of progress.

  8. Continuous attention to technical excellence and good design enhances agility.

  9. Simplicity--the art of maximizing the amount of work not done--is essential.

  10. The best architectures, requirements, and designs emerge from self-organizing teams.

  11. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly.

  12. Whereas all of the above is closely intertwined with each other in the sense that the 12 principles are for example a demonstration of the 4 values.  

Speaking about a #learningcurve.

Care to share your take-aways regarding LEARNING AGILE – from BEING to DOING agile?

I’d love to hear from you.

2 Ansichten0 Kommentare

Aktuelle Beiträge

Alle ansehen


bottom of page