Posted on 1 Comment

Product Owner. Not the Agile name for project manager or other outdated functions.

The Product Owner in Scrum is accountable for the value delivered. Besides the fact that value is a very different driver than volume is (think outcome versus output), that accountability can hardly be demonstrated without a clearly identified ‘product’. Product is the vehicle to deliver value. Neither can a Product Owner be accountable and effective without a mandate to make decisions. Product Owner accountability cannot be mapped on existing roles or functions, nor can it be effectively enacted through deliverables and meetings dating from the industrial paradigm.

Although ‘product’ determines the scope, span and depth of Scrum, it is one of the most ignored considerations when Scrum is introduced. Organizations often introduce Scrum by constructing teams within existing departments and silo structures. The ‘Product Backlogs’ that they work off may be fascinating collections of work, but they are rarely for a…product. But how can you then know what the Product Owner actually owns? What purpose serves Product Backlog if not the single source of work to optimize for the value that a product delivers? What is it that releasable Increments are being created of when not of a well-defined product?

Without a clearly identified ‘product’ optimizing for value is hardly possible and Scrum is hardly used effectively.

When teams work within the confines of a traditional line organization, the highest achievable definition of product is often a part of a system, a component, a module or ‘something’ to be shipped tosomeone’. Teams deliver work to other teams that in turn combine it with their work or the parts of the system, components or modules they produce. And other teams again depend on the work to be received from them. As the different teams often operate under different line management, it ends up with nobody minding the synergies across them, with nobody minding the actual product and the value delivered to end-users, with nobody minding how poorly Scrum is organized and employed. One might wonder where the courageous Scrum Masters have gone but in the end the effective use of Scrum is impeded by mapping it to the old delivery structures to keep producing the same parts and modules for the same sub-products in a series of open-loop systems rather than thriving on closed-loop feedback control.

The challenge is to know your product or service so you can start organizing your Scrum to best serve the people consuming it and the organization funding its development, while increasing the sense of accomplishment for the people performing the work!

After knowing the product, the mandate and autonomy of the Product Owner is the next tactical challenge to tackle. Is your Product Owner the best placed person to make business decisions or is your Product Owner a proxy, a distant representative, a temp like a project manager or some other intermediary? Are the decisions by your Product Owner fully supported or does your Product Owner have to check in with managers, directors or the steering committee before making a decision? Any decision?

Regardless, the minimal purpose of the Product Owner role in the Scrum framework is to inject and uphold the business perspective in the product development work. The Product Owner connects the worlds of (1) product management and the business side of the organization (think market research, sales, finance, legal, marketing), (2) the user and consumer base and (3) the delivery or development parts of the organization.

Connecting those worlds includes engaging with them to assure that all product management aspects and the wider business perspective are integrated into the actual development. In the other direction it allows the Product Owner to keep stakeholders and product management people up to date on the actual progress, so they can organize or re-organize their work accordingly. Being a connector is not the same as being a bottleneck. Product Owner, not information barrier.

Regardless, the Product Owner is the one person making the final call on the order of the work in the Product Backlog. Product Backlog shows all the work currently envisioned for the product, all work that potentially increases the value that the product delivers. Smart Product Owners show openness for great ideas whatever their source or origin and they gracefully employ skills of development people to convert product ideas and business solutions into requirements. Product Owner, not product dictator.

The Product Owner manages Product Backlog based on the product vision as a longer-term view of the road ahead. A product vision captures why the product is being built and why the product is worthwhile investing in. A product vision helps the Product Owner set or reset specific goals, hopes and dreams, express the expectations and ideas captured in the Product Backlog better and better order the items in the Product Backlog for value.

If anybody wants to know what work is identified and planned for the product, it suffices to look at the Product Backlog, at one artifact only. To understand what is planned for or what is in the product, and why, it suffices to ask the Product Owner, one person only.

Sprint Review is a great opportunity for a Product Owner to learn about the assumed or actual value that the product delivers. At the Sprint Review, (key) stakeholders, the team and (potentially) consumers or (key) users collaborate over what got done and what didn’t get done, what influenced the work and what was the purpose of that work. But value as the overall purpose is a very different driver than volume is. The purpose of Sprint Review is not reporting or justification of the amount of tasks executed and features implemented but sharing relevant information on usage and impact, competition and market trends; feedback that will help optimizing for value in the next Sprint(s). The goal is to collaboratively identify what is the most valuable work to do next for the product. This is evidently captured in the living artifact that Product Backlog is.

There cannot be any doubt that being a Product Owner implies expectations, skills and traits that go beyond those of a traditional requirements engineer, a requirements provider throwing work over the wall to developers or a similar proxy. Product Owner, actually, owns the product and is the owner of the product. Such ownership of a product implies strong organizational adoption of the role. It allows a Product Owner to act like a product-CEO (again, not a product dictator). That accountability cannot be mapped on existing roles or functions, deliverables and meetings. The role simply did not exist in the industrial paradigm.


Note. This article is based on texts that are taken from my current book-in-progress “The House of Scrum” (to be released in 2021).

Posted on 1 Comment

My life of Scrum (did not start with Scrum)

October 1995. After a few years of searching and experimenting, “Scrum” was documented and presented to the general public.

October 2020. Scrum turns 25. Hip hip hooray! I record a few highlights of “My life of Scrum”, a few aspects from the past 17 years of the life of an independent Scrum Caretaker.

September 2003. The founding managers of the company that employs me, ask me to have a look at the challenge of delivering the core server platform for a digital television implementation (one of the first in Europe at a bigger scale). Due to delayed negotiations, the project is already late and the real work hasn’t even started. Two software architects give me a 15-minutes introduction of eXtreme Programming. I fall for it. Completely. The urgency and feeling of crisis is also such that we are allowed to start applying it. We throw away all existing plans, create an ordered pile of User Stories, get together a great gang of developers, and go to work in iterations of 3 weeks. Later, we add Scrum to our approach. Scrum cannot be applied effectively without clear and agreed development practices and standards in place.

May 2004. I attend a CSM class (“Certified ScrumMaster”) by Ken Schwaber. It turns out the first CSM class in the region (Belgium, Netherlands). We join with 5 people from our organization. There are 25 people in total. We need to pay in cash. In my memory it was a 3-days class. Although that is said to be impossible, in my memory it still is. I am not to be trusted in such things. I don’t care about titles, positions, certifications, career. I don’t keep up with all the certifications being created, but just practice Scrum with different teams, in different domains, for the next 7 years.

December 2011. I attend a PSM class (“Professional Scrum Master”) by Ken Schwaber as part of my journey towards obtaining a license as a Professional Scrum Trainer. I also start working full-time in the Netherlands: helping, assisting, coaching, guiding, and advising large organizations on their journey of adopting Scrum. I could not have done so without the 7 years of practice that preceded this phase of my professional life. I would have not had the firm foundation to stand my ground. Some things take time. More dots get connected as I engage in a partnership with Ken and Scrum.org from 2013-2016, and as I continue my journey afterwards as an independent Scrum Caretaker.

Posted on 6 Comments

Surprise. I am no wizard. Agile nor Scrum.

I regularly get inquiries from people reaching out for instructions, assistance, or other forms of guidance to learn about Scrum, pass exams, become a trainer, or advance their career towards “Agile coach”.
Surprise. I am no wizard. I do not have the magical powers that would be required.

I really don’t want to go into people’s motivation to approach me with those desires (‘free’ seems to be a recurring theme), but I can share my personal and professional stance and considerations.

(1) Honestly, I don’t know what an “Agile Coach” is or does. Not even attending a “Coaching Stance” class by the Agile Coaching Institute in 2012 has helped me in that regard. The same goes for having worked with many people holding the title. I have never called myself that and I have never used the label in my profile, CV, or service offerings, let alone that I would have the powers to turn somebody into it.

Looking back on the 16+ years that have passed since I started applying the powerful combination of Scrum and eXtreme Programming in 2003, I realize I only ‘had’ to start thinking about and explaining what ‘Agile’ might mean, or what an “Agile Coach” is, since 2010-2011 (7 years later). I don’t think it is a coincidence that this is when I started engaging with large companies and the wave of ‘scale’ sweeping my world, the time when ‘Agile’ became a corporate thing. I still can’t clearly explain what an “Agile Coach” is or does.

(2) I have always been and am still all about Scrum. It makes transparent what I stand for, it makes tangible and actionable the services I offer and bring, and it includes plenty of room and openness for contextual customizations. As Scrum is an open framework, an organization can standardize on Scrum and substantially increase their agility without industrializing their Scrum to death.

The continuous balancing act of a Scrum Master, including the coaching aspect

(3) I don’t create them for that reason, but I am humbled when people say my writings (books, articles, papers) or my classes were useful in achieving a certification, in becoming a trainer, or in passing some other milestone. I am comforted knowing that those individuals did the actual work. They might have gotten some insights and language from me, but that’s about it. I did not hold their pen or control their brain. It is likely that they struggled, fell, got back up, failed, tried again. Maybe along the road they took a break, read more, gained more experience with Scrum, and demonstrated other forms of patience, persistence, and belief.

The many requests from people that seem to believe that I can ‘make’ them a trainer or ‘make’ them achieve a certification leave me flabbergasted. Surprise. I CANNOT. And even if I could, I wouldn’t. It would not be helpful for the requestor’s autonomy and development.
I don’t know whether it has anything to do with the current covid-crisis sweeping the planet, but I worry seriously how this seems an obsession for quite some people.

On a personal note, I want to share that my journey of Scrum started in 2003. And I spent 7 years (seven!) of just applying Scrum, and enjoying how it helped deliver great results, make users and consumers happy, and observe highly engaged teams enjoying their work. During that time, I had no idea about certifications, grades, or career moves, and I can honestly say that I couldn’t care less. It was only by accident in 2010-2011 that I became what I didn’t know I wanted to be. Looking back it still feels odd. Although it may look as if there was a plan, there wasn’t.

Even after more than 16 years of this stuff, I am no expert. Nor am I tired of Scrum. Not even close. I am an eternal novice. There is so much to learn. There are so many ways to consider and explain Scrum, even having published two books and considering two more books as we speak.

I welcome everybody to join my classes or workshops to find out how I express Scrum, or attend the many events and webinars I participate in, check out my YouTube channel, hire me for some consulting and coaching. I will do my best to help you understand Scrum, its purpose and design, how to get the most out of it, and learn to think for yourself in terms of Scrum. Regardless of how much I care however, I cannot ‘make’ anyone a trainer, a Scrum Master, Product Owner, or “Agile Coach”. I cannot ‘make’ anyone pass some certification assessment or exam. That is not in my powers (if even that would be helpful). I am no wizard. I have no magic, some empathy at most.

And, like it or not, the primary source of learning about Scrum is from practice, from doing Scrum. It is the way to learn Scrum, beyond learning about Scrum. There is a huge difference.

Yours truly
Gunther
independent Scrum Caretaker

Posted on

“Scrum – Una Guida Tascabile” is now widely available

As I was working on the second edition of my pocket guide to Scrum in 2018, Michael F Forni proposed to create an Italian translation of my book. It was the start of a collaborative endeavour, in which he got help from Fabio Panzavolta and Aniello Di Florio, towards self-publishing the translation.

I am humbled and honoured for announcing that the result is now available as Scrum – Una Guida Tascabile (Un compagno di viaggio smart)“, in Kindle and in paperback format via Amazon.

I wish all Italian speaking friends of Scrum much joy reading my translated thoughts, beliefs and considerations of Scrum, that simple framework to address complex challenges. I feel forever indebted to Michael, Fabio and Aniello for making my book available for all Italian readers, and to Barbara Knijff of Jellylab for creating the cover.

Loving regards
Gunther
independent Scrum Caretaker

Here is how Michael, Fabio and Aniello introduced their work in the book:

Nel ringraziare Gunther per questa fantastica opportunità – consapevoli della grande responsabilità che porta il compito di tradurre un così importante testo divulgativo come la sua Guida a Scrum – chiediamo al lettore di essere comprensivo e di focalizzarsi il più possibile sulla sostanza del pensiero dell’autore, piuttosto che sulla forma di volta in volta scelta dal traduttore: il reale valore di manuali come questo non sta infatti nel successo – o meno – di riuscire a cogliere esattamente il senso della singola parola o frase, bensì quello di trasmetterne efficacemente i concetti, gli esempi e le pratiche da applicare al proprio contesto individuale.

Per la traduzione della terminologia Scrum, ferma restando l’assoluta inopportunità, pienamente condivisa con l’autore, di modificare o storpiare i consolidati sostantivi caratterizzanti del framework (oramai divenuti d’uso comune nella Comunità Internazionale degli Agile practitioners) – sono state tenute in debita considerazione: 1) le traduzioni passate ed attuale delle versioni in Italiano de “La Guida a Scrum” 2) il lessico oramai d’uso comune tra i praticanti di Scrum 3) la nostra sensibilità di bilingue, che naturalmente risente delle esperienze personali.

Contiamo che il lettore sia indulgente e non ce ne voglia; qualora rilevasse errori, imprecisioni o volesse dare il proprio contributo migliorativo, saremo felici di essere contattati per apportare ulteriore valore a quest’opera.

Buona lettura!

Michael Fabrizio Forni – Co-traduttore e curatore dell’opera
Fabio Panzavolta – Co-traduttore
Aniello Di Florio – Correttore bozze

 

Posted on Leave a comment

“Framework”

At some point in time the term “Framework” became really fashionable. I don’t remember when it was exactly, but it was when smart businessmen assumed it was better for sales, as commonly used terms like methodology or process got burned. At least, that can be seen as an achievement too. Most likely they guessed it explained the wide adoption of Scrum, and aspired the same ’success’.

Today, the word is omnipresent and can surely be added to the list of most misunderstood words in the world of “Agile”. That does not change the fact that we did not start using the word lightly in the past. It was not about marketing or selling. It was about sincerely describing the lightweight nature of Scrum, as a simple set of rules, principles and values that define a framework for inspection and adaptation, a way for people to address complex challenges.

Regardless of fashion of the day and obfuscation, this is not a term to leave to the sharks. Language matters. Scrum is a framework, not a methodology, as I described in 2013 and in my book “Scrum – A Pocket Guide”.

Posted on 2 Comments

The international versions of the Scrum Values (September 2018)

In May 2013 I described how there is value in the Scrum Values. I included that text in my book “Scrum – A Pocket Guide” that was published in November 2013. Early in 2018 I updated my description slightly to be included in a revision of my book that I anticipate. A group of Scrum enthusiasts subsequently translated that updated version to different languages.

The last incremental update of the September 2018 release of the international versions of the Scrum Values is now available, as a free download (PDF): The Scrum Values (international versions) -September 2018 (R3).

Early in September following new languages were released as a new baseline version: Filipino-Tagalog, Indian-Hindi, Polish, and Spanish. Throughout September we went into a continuous delivery mode and released additional languages as they became available: Persian, Arabic, and Danish.

A poster of the international versions of the Scrum Values is available as a free download (PNG): The Scrum Values (International Versions poster).

Share my gratitude that following people spent quite some of their valuable time on this initiative to make these translations available for you:

  • Arabic: Rasheed Raya.
  • Chinese (simp/trad): Lana Sun, Wei Lun Teh, Chee-Hong Hsia.
  • Danish: Mikkel Toudal Kristiansen.
  • Filipino: Shirley Santiago, Warren Yu.
  • French: Fabio Panzavolta, Mohamed Gargouri.
  • German: Uwe Schirmer, Peter Götz, Dominik Maximini.
  • Hindi: Punit Doshi, Hiren Doshi, Nagesh Sharma.
  • Italian: Michael F. Forni.
  • Persian: Mehdi Hoseini.
  • Polish: Krystian Kaczor.
  • Portuguese: Leonardo Bittencourt.
  • Russian: Konstantin Razumovsky.
  • Spanish: Pablo Bernardo.
  • Turkish: ilkay Polat, Lemi Orhan Ergin.

In the document you will also find my Dutch translation. I maintain the base English version on the Scrum Values section of my website.

All feedback is welcome. Sharing of the PDF is equally encouraged.

Warm regards
Gunther

Posted on Leave a comment

Scrum Glossary (International Versions, April 2018)

By the end of 2017 I updated the Scrum Glossary of my book “Scrum – A Pocket Guide” (2013). A group of Scrum enthusiasts subsequently translated that updated version to different languages. A first release of those international versions was done in March 2018.

The new, April 2018, release of the international versions is now available, as a free download (PDF): Scrum Glossary (International versions) -April 2018

  • Four new languages were added: Filipino-Tagalog, French, Indian-Hindi, Turkish.
  • The definition for “Definition of Done” was rephrased.
  • A definition for “Product” was added.

Share my gratitude that following people spent quite some of their valuable time on this initiative to make these translations available for you:

  • Chinese (simp/trad): Lana Sun, Wei Lun Teh, Chee-Hong Hsia
  • Danish: Rasmus Kaae
  • Filipino: Shirley Santiago, Warren Yu
  • French: Fabio Panzavolta, Mohamed Gargouri
  • German: Uwe Schirmer, Peter Götz, Dominik Maximini
  • Hindi: Punit Doshi, Hiren Doshi
  • Italian: Michael F. Forni
  • Polish: Paweł Feliński
  • Portuguese: Leonardo Bittencourt
  • Russian: Konstantin Razumovsky
  • Spanish: Alex Ballarin
  • Turkish: Ilkay Polat, Lemi Orhan Ergin

In the document you will also find my Dutch translation. I maintain the base English version on the Scrum Glossary section of my website.

All feedback is welcome. Sharing of the PDF is equally encouraged.

Warm regards
Gunther

Posted on Leave a comment

Blog Statistics (country views)

On Valentine’s Day of 2008 I started my blog “Ullizee.wordpress.com” with a first blog post. The URL still exists but is now redirected to “guntherverheyen.com”.

Since that day I have created 457 posts. The past years I blogged primarily about Scrum, and rather occasionally still about my love for books, music and my family.

I am mostly amazed by the global reach of my musings. The statistics show that my blog was visited by people from 182 countries. The top 10 countries (5,5%) account for 75% of all traffic.

Another 20% of all traffic is by visitors from an additional 30 countries (16,5%). So, 95% of all traffic on my site is generated by visitors from 40 countries, i.e. 22% of all countries. That leaves 142 countries, 78% of all countries, accounting for the remaining 5% of traffic.

Hereby a huge thanks and a big hug to my international readers, followers, likers, sharers. You mean the world to me.

Love
Gunther.

Posted on 2 Comments

Have an amazing 2017

2016 was a most fascinating year. From my perspective it was either high or low, with little room for middleground.

Our family and my professional life skyrocketed. I gained creative and intellectual freedom and ownership when deciding to further my journey as an independent Scrum Caretaker. And collaborations of beauty are emerging. But all around, in my city Antwerp, my country Belgium, my home continent Europe and on our planet we saw fear and anxiety often dominating.

Remember, fire causes passion as well as death and destruction. Try not to feed your internal wolf called ‘fear’ too much.

Make 2017 an amazing year!

As announced, I foresee spending much energy on introducing re-vers-ify to the world, an act of rhythm, simplicity and focus, a way to help people re-imagine their Scrum and their organisation.

With love
Gunther
22 December 2016

Posted on 1 Comment

Aan het einde van de kim, (de) WIL. Onbereikbaar?

olyslaegers-jeroen-wilWIL brengt ons het levensverhaal van de genaamde Wils, Wilfried, Antwerpenaar. Zijn levensverhaal wordt volledig overschaduwd door WO II, toen Wils en zijn kameraad Lode hulpagent waren in Antwerpen. Zeker wat Wils betrof, was dit een opportunistische arbeidskeuze. Zo kon hij ontsnappen aan de verplichte arbeid in Duitsland. Het ambiguë gevolg was dan wel dat hij geacht werd andere arbeidsonwilligen in de kraag te vatten. En erger.

Alhoewel Wils heimelijk eigenlijk het serieuze dichterschap ambieert, lijkt zijn voornaamste talent te zijn: overleven. Ambitieloos schippert hij tussen oorlog en vrede, tussen bezetter en verzet, tussen participatie en onthouding, tussen Duitsers en Joden, tussen werkplicht en razzia’s, tussen smeerlap en behager.

De genaamde Jeroen Olyslaegers, getalenteerd schrijver, laat Wilfried Wils, overgrootvader intussen, vandaag zijn verhaal brengen in een indrukwekkende terugblik van zo’n slordige 300 pagina’s. Wils blikt terug op zijn leven, zijn huwelijk, de oorlogsperiode en het leven erna, alhoewel de schaduw van de oorlog veel, zoniet alles, bepaalt. Alsof de klok haar tikken stopte rond ’45. De lezer leert Wilfried Wils kennen als een man die zijn wil wil doen gelden, daar glorieus in faalt, herhaaldelijk, overleeft en voortkrabbelt, herhaaldelijk.

Jeroen Olyslaegers brengt ons met WIL een indringend onderzoek naar de zucht naar normaliteit, het stilzwijgende verlangen om steeds weer zo snel mogelijk, wat er ook gebeurt, over te gaan tot de orde van de dag. Jeroen schetst ons de veranderende gezichten van een stad tijdens de bezetting, het dagelijks leven in een bezette stad, in straten en verdonkerde huizen vergeven van de normaalzucht, ver weg van prozaïsche helden vs. verachtelijke misdadigers. De stad zelf krijgt daarin een eigen stem, terwijl er door haar bevolking meer wordt gezwegen dan gepraat, in de illusie dat dan alles snel weer normaal zal worden. Zwijgen en normaalzucht gaan er hand in hand, in het bezette leven in deze bezette stad.

Genadeloos toont de schrijver ons het laffe zwijgen, en het verdoken verraad dat erin verscholen ligt. Maar de auteur vergoelijkt, oordeelt noch veroordeelt, alsof ook hij over en weer geslingerd wordt tussen de liefde voor de mens, geportretteerd in zijn personages, en de afschuw voor hun daden, alsof ook hij weet dat de grens tussen lafheid en slechtheid moeilijk te trekken is, alhoewel ze wel bestaat. We worden mede-verstekelingen op de schepen genaamd “Leven”, de oceaanstomer genaamd “Maatschappij”. Verstoken van overtuigingen die kunnen uitgesproken worden. We worden allen stilzwijgende neutralen. Toch neemt WIL ons mee tot voorbij het punt waar zwijgen nog een optie is.

Stilte is in zekere zin, en in meerdere lagen, ook de grote kracht van WIL. Zoals we van hem gewend zijn, hanteert Jeroen een overweldigende en rijke taal in WIL, en daarenboven een prachtig Vlaams dat netjes laveert tussen gesproken klank en geschreven inkt, tussen stedelijk volks en verheven poëticaal. Jeroen staat, bij mij alvast, bekend vanwege een stevige overdrive en overdaad, in beelden, in drukte, in woorden. Wel, in WIL is zijn taal nog steeds mooi en rijk, maar blijft hij weg van zijn over-taal. Hij laat de gebeurtenissen, vaak in alle gruwelijkheid, voor zich spreken. Er komt geen onnodig gemoraliseer aan te pas, geen gedramatiseer. Net daarom is het zo’n kopstoot. Wils brengt het verhaal, Olyslaegers is onthecht. Net daarom komen de beschreven gebeurtenissen zo hard binnen. De horror en de gruwel komen onversneden tot de lezer. Maar de schrijvende schepper stelt zich oordeelloos op. Hij zoekt geen excuses, maar gedraagt zich ook niet als rechter.

Het is niet moeilijk de link te zien met hedendaagse thema’s en burgemeesters, maatschappelijk engagement, migratie en vreemden, politieke en andere retoriek, het neo-populisme. Dat is een sterk (s)taaltje, teksten schrijven gebaseerd op een mid-vorige eeuwse periode zodat lezing ervan ook vandaag relevant is. Misschien ook wel beangstigend. Sommige passages kunnen letterlijk, zonder één letter te wijzigen, hergebruikt worden in het Antwerpen en Vlaanderen anno 2016. Voorwaar. WIL is echter geen simplistisch pamflet, het bevat geen lineaire zwart-wit meningen of oordelen, maar toont ons de complexe inter-menselijkheid achter -soms bijzonder gruwelijke- feiten. WIL toont de vele facetten van de diamant, het steentje, de illusie genaamd “waarheid”.

Er is de WIL tot Macht. Er is de onWIL tot spreken. De WIL van de angst en de wrok, voor de Ander, de WIL tot het Grote Zwijgen. En er is WIL van Jeroen Olyslaegers. Verder heb ik zelf geen mening, doe ik er liever het zwijgen toe. Per slot van rekening heb ik hier niet voor gestudeerd, en zijn het mijn zaken niet, de literatuur. En laat me dan ook maar voorbij gaan aan de gigantische hoeveelheden research die dit boek duidelijk gekost hebben.

Evidenter is het om te genieten van de prachtige cover. Gestileerd, dreigend. De sfeer van een bezette stad, de herinnering aan de cover van Bezette Stad van die andere Antwerpenaar, de dichter Van Ostaijen. En cinema uit het interbellum, signatuur Fritz Lang en co.

van-ostaijen-paul-bezette-stadmetropolis-movie-posterm-movie-poster

Ik begrijp dat de ware literatici veelvuldig verwijzen naar Claus, Boon en andere grootheden. Dat is helemaal terecht, omdat WIL in een grootse literaire traditie thuishoort, maar niet omdat het een afkooksel of kopie is van. Een loutere vergelijking doet allen tekort. WIL is vintage Olyslaegers, een gigant op zich, die zijn stem verder heeft ontwikkeld, in beheersing. Vintage de nieuwe Olyslaegers, die net is opgestaan.

Ik kijk en zie. Aan het einde van de kim, de incarnatie van Angelo. De diamanten gevonden. Achterin de kast, inderdaad.

Dank je, Jeroen.

img_3247Vanwege
de Man op de Foto