Gunther Verheyen is an independent Scrum Caretaker and Workplace Humanitarian on a journey of humanizing the workplace.
Saturday September 27 1997. The morning of a nice day. The morning that my wife and I got married. It was not the start, but a continuation of a shared life that started 4 1/2 years earlier. Nevertheless, a day to remember. A milestone still. A celebration of unity. That lasts and keeps lasting.
There’s sugar on your soul
You’re like no one I know
You’re the life of another world
You swallow me whole(Editors, Sugar, 2013)
Scrum is not a goal in itself, Scrum is a mean. Scrum is a path that a person, a team, an organization takes toward increased competitiveness, higher responsiveness, more learning, more creativity, optimistic opportunism, a sustainable way of working, restored respect for people. Scrum is a journey toward increased… agility.
I have written a book about Scrum, published on 4 November 2013.
As Scrum is designed to help people, organizations and teams embark on a journey, my book is a smart travel companion for that journey. My book is a pocket guide that can help you prepare, take off, and get going. And while on the road you can always have a quick peek again to find your way or re-orient.
My book is completely focused on Scrum. It was an explicit choice to stick to the topic, Scrum. And to be essential about that. As David Starr, Agile craftsman at Microsoft, said upon reviewing an early version, it is “without a drop of hyperbole“. Ken Schwaber, my fellow-traveller at Scrum.org and co-creator of Scrum, says it is plainly the best description of Scrum currently available. Ken has also written the foreword, summarized as “An outstanding accomplishment that simmers with intelligence.”
The book has 4 chapters:
Other appreciated reviewers were Ralph Jocham, Agile professional and Professional Scrum trainer, and Patricia Kong, director of partners at Scrum.org. Ralph says this is the book he will advise his students, coachees and organizations to read in order to learn the essential Scrum. Patricia says she would have loved to have this book when she entered the world of Scrum. Because she didn’t find one at the time.
The book, “Scrum – A Pocket Guide (A Smart Travel Companion)” will be published by Van Haren. My gratitude goes out to their team that has made this possible!
Pre-order your copy at Amazon (UK) or at the publisher’s webshop.
De eerste schooldag van het nieuwe schooljaar hebben we weeral achter de rug, gisteren, maandag 2 september 2013.
Zoals gebruikelijk nemen we foto’s van onze kroost. En dan voegen we weeral een jaartje toe aan onze compilatie:
En dit jaar hebben we voor de eerste maal 3 kindjes die allemaal het nieuwe schooljaar aanvangen:
Nu ja, wij zouden ‘wij’ niet zijn als alles vlekkeloos verloopt. Nienke heeft verleden jaar de instapklas gedaan, en gaat dus nu naar de eerste ‘echte’ kleuterklas. We hadden echter verleden week vastgesteld dat ze uit haar vriendengroepje was getrokken en in een andere klas dan hen was gesplitst. Navraag bij de juffen leerde ons dat ze daar niet echt bij stil gestaan hadden. Gewoon, lijstje afgelopen tot het gewenste aantal was bereikt en streep getrokken. Afgehandeld. Zoals de conversatie.
Zo niet bij ons. Een mailtje naar de directeur leidde wel tot een gesprek, niet tot dialoog. De misnoegde, want beledigde, knorpot maakte duidelijk dat dit een genomen beslissing was. Afgehandeld.
Zo niet bij ons. Nienke gaat naar een andere school, en wel vlak bij huis. Lekker wortelen in Ekeren. En dat dat de enige goede beslissing is, kunnen we afmeten aan het gebrek aan hechting dat ze heeft op haar huidige school, waardoor ze nu al naar de andere school wilde (we hebben het haar wel verteld, natuurlijk).
Hmm, 3 kinderen, 3 scholen. Best wel fun, eigenlijk. De drive om goede keuzes te maken, niet zomaar zo-zo keuzes. It’s a way of life, als je er goed over zou nadenken. Intussen heb ik geleerd er trots op te zijn. Free spirits.
No excuses, I was a teenager in the ’80s. And I gave my girlfriend/wife their best of album ’81-’90. Yet I never showed much interest in the Waterboys, despite my wide interest in music. Maybe I was too fed up with ‘The Whole of the Moon’ as it was really, really played a lot in the places I went out in the weekends around ’86-’87? Maybe it didn’t fit my cool punk-wave ways (not preventing me to deeply love The Smiths and The Triffids, to name a few)? Maybe my mind just wasn’t ready for it, not free enough a spirit by then?
It wasn’t until 2000 that I bought my first Waterboys record, the by then just released A Rock in the Weary Land. No idea where the sudden attraction came from. Was it because it was described as a comeback? Was it because of the fooling around with vocoders and other distorters, the heavy electricity on the record? 
It was a strange attraction. That led to me immediately falling in love with this rock called love; its passion, drive, pleasure. It turned out the start of a rollercoaster of musical brainfloods that started by subsequently also purchasing the EP Is She Conscious from the 2000 album. That EP included an incredible 15 minutes live version of Savage Earth Heart. To my surprise this song originated from their early years. And that got me interested to dive further.
When the early Waterboys albums one by one got re-released with substantial remastering and editing by mr. Mike Scott I bought them as they were put out. And consistently fell in love with each of them, while greedily and gratefully feeding my mind on the fascinating background added in Mike’s sleeve notes. I grew along with each re-release to finally reach the big music of This Is The Sea via The Waterboys and A Pagan Place. And so, some silly 20 years after locking it out of my musical world, I discovered the amazing beauty, melodies, layers and power of The Whole of the Moon. Although it is ‘Red Army Blues’ that gets me in tears every time again.
Impatient and near-unbearable waiting followed, but then finally also Fisherman’s Blues was re-released. And 20 years after the boys themselves ‘slightly’ changed direction (understatement), I was able to savour the outcome of their Irish adventures. The sleeve notes only partially shed light over this impressive turn they took, and the years of wandering and exploring it took to create it. That didn’t prevent me from feeling the free spirit that breaths throughout the Fisherman’s work.
Later on I was impressed by the bluesy Too Close To Heaven too, and its refurbished and boosted edits of FB sessions. Unfortunately Universal Hall and Book of Lightning didn’t overload me with enthusiasm therefore skipping the Karma Burning album, not even realizing it’s a live album. Hmm, Waterboys and live playing, that always works, do I know now. I did feel Mike’s fond love for music on one of his solo albums that I bought in the mean time, Bring ’em All In.
More and more, in interviews mr. Mike alluded to his lack of real inspiration, although reviews of their live performances were full of praise, one by one. But then, 2011, the message of the release of An Appointment with Mr. Yeats reached me (see my Top Music 2011 summary), convincing me to buy it. It turned out to be wildly inspirational, bewildering, enthusiast, broad, folk danceable while rocking as in the big music era. Artistically, the album melts the many faces of the Waterboys into one highly cohesive, unique musical picture.
And next, 2013, a tweet by a rock journalist pointed me to Mike Scott’s autobiography, Adventures of a Waterboy. I took it on our family holiday early August 2013, intrigued but also eager to be ‘prepared’ for the live gig of The Waterboys we were about to attend by the end of August in Antwerp (yes, first time we get to see them on stage). Through it I hoped to better understand who the man is that will be on that stage. A wild man, somewhat shamanist and an all-music madman, as he is in my imagination?
So my wife and I unilaterally made an appointment with Mr. Scott to go discover these Waterboys live; live on stage, the only platform mr. Mike considers the right one for a musician to grow an audience; much more than music business tricks like videos, music clips, alternate releases of the same song, etc. Some things I learned from his fantastic book. I will come back to his adventurous book, but note that the gig was fantastic, guiding us through all the worlds of the Waterboys; folk, rock, big music, tiny music, acoustic, improvised, extended, unexpected, driven by the spirits. The chemistry between Mick and Steve is obvious and shiny. And Steve Wickham brilliantly took over the brass and trumpets from the first albums with his terrific fiddling.
Scrum seems to puzzle some people. Oddly enough most of them are puzzled by the simplicity of Scrum, yet find it difficult to implement all elements of Scrum. There is some weird logic in play saying that it can’t be that simple, so elements of Scrum are replaced with much more and preferably highly complicated structures, procedures and processes.
Scrum has 3 roles, 3 artefacts and 5 events. It is enough to empirically solve the complex puzzle of software development, but all are required to cover all accountabilities in software development. Complete simplicity is the key. It doesn’t make it easier to play the game, but it does help to focus on the problem, and not on the difficulties that the structures themselves cause.
Following jigsaw representation of the Scrum framework (1) shows all elements that formally make out Scrum, and (2) it helps seeing that Scrum isn’t complete when you don’t have all the pieces in place:
The last couple of years we headed south for our yearly summer holidays, to Croatia, Italy, Spain; looking for the sun and making sure a swimming pool is around. For 2013 we decided to head north, to Sweden.
Before presenting my little summary of every day and a mosaic with one picture a day, let me share some take-aways first that popped up in my head during our 2 weeks in Sweden, Småland:
Nice bread. Big trucks. Quiet Saturdays. Much green. No elks.
Day 1, Friday August.2: Antwerp-Bremen. A bit stressed (as always at the start). Some hotel swimming and an outside German dinner at Prüser’s Gasthof in Hellwege (near Bremen).
Day 2, Saturday August.3: Bremen-Malmö. Relaxed (totally, finally). Taking the boat from Germany to Denmark (just in time), and crossing the famous bridge from Copenhague to Malmö. What a fine hotel (after turning a couch into a bed for the boys). Enjoying the evening at a square with a lovely fountain and modern eating of famous chefs.
Day 3, Sunday August.4: Malmö-Öreryd. Even more relaxed. Morning market and first vintage purchase in Malmö before headinf further north. Lunch in Halmstad. Arriving following the GPS. Depressed by the house. Found a supermarket though (in Gislaved) and the lake in Öreryd.
Day 4, Monday August.5: Jönköping shopping. Most relaxed (BIG!) lunch ever including caffé frappé; the children lovelier than ever during a relaxed lunch. Noa noa sales shopping for the women!!!
Day 5, Tuesday August.6: Öreryd beach day. Morning reading (see Books chapter below), Gislaved supermarket and… Öreryd beach by the lake. Sun after rain. Hurting my knee in an overcourageous jump into the water an and overheated barbecue in the evening.
Day 6, Wednesday August.7: Country day. Pleasant surprise: quilt shopping in Tyger o Ting, and a vintage lunch in Smålandsstenar and more money well spent.
Day 7, Thursday August.8: Regensprookjesdag (rainy legend day). Going to Ljundby mainly for the ‘Sagomuseet’ (fairytale museum). Finding more country stuff. Passing via mount Isaberg and its handcraft exposition on the way home. Tired. Rain.
Day 8, Friday August.9: Götebörg. A long, terrific day of shopping, eating and relaxing in a neat and soothing city. A tapas ending near the river. Little rabbit’s asleep.
Day 9, Saturday August.10: Lazy day Saturday. Morning reading, supermarket and… Öreryd beach by the lake. Swimming in the rain. Followed by a refreshing evening walk.
Day 10, Sunday August.11: Short day out to Gislaved. Eating in Smålandia, an ancient looking truck restaurant.
Day 11, Monday August.12: Astrid Lindgren day. Early up to be immersed all day, a long day, in the world of Astrid Lindgren. Little houses, big houses, little stories and big stories told, played and depicted. Presents for all! A fantastic highlight.
Day 12, Tuesday August.13: Rain. Escaped to tiny sun beams and a vintage lunch in Gränna, city of candy.
Day 13, Wednesday August.14: Rain. Escape to the swimming pool. Evening dinner in Jönköping.
Day 14, Thursday August.15: Garden day. Visiting the Gunilla gardens in Swedish Småland by Danish artist Tage Andersen. We celebrate mother’s day. The Swedish don’t. And we end with an expected sunny stay at an unexpected beach near lake Vättern Evening dinner at a Jönköping pier.
Day 15, Friday August.16: Lazy day of awakening slowly, starting to clean the house and going for another vintage afternoon lunch in Smålandsstenar, and vintage sales hunting in the connected shop. Nienke entering the Lega värld, with her first Lego Friends set.
Day 16, Saturday August.17: Last day. In search of the second hand super market of Gnosjö. Found. It’s still there. We closed the vacation with a tapas dinner by the water in Jönköping.
Day 17, Sunday August.18: Öreryd-Bremen. Back on the boat. Germany is definitely a terrible driving country. Same hotel, same swimming pool in Hellwege. Relaxed.
Day 18, Monday August.19: Bremen-Ekeren. Home. It’s been F A N T A S T I C. Only disappointment was the house we stayed in. But we explored the region, had great excursion and the kids never before were so at ease with our habit of irregular meal times and unexpected lunches.
I have read following books on this holiday: Nightwing 2 (‘New 52’ series by DC Comics), Superman Earth One vol. 2, Quarks, chaos and christianity by John Polkinghorne, Mike Scott – Adventures of a Waterboy, De Maagd Marino by Yves Petry. The Polkinghorne book was meager, but the other ones were great. I particularly enjoyed Mike Scott’s lively tales of his various adventures!
I have an endless stock of books I still have to read (in our private library), but keep a list of specific books I want to read next. For diverse reasons my holiday reading made me overwrite my short term list and replace it with Rimbaud (Illuminations and Une saison en enfer), Nabokov (Lolita), Nietzsche (re-reading some works and consuming new wisdom), Stephen Hawking and Ludwig Wittgenstein.
Omdat onze oudste zoon zijn eerste tentenkamp achter de rug had met de scouts kregen wij de kriebels om nog eens te gaan kamperen met het gezin. Dat was verleden week. De weerberichten waren gunstig. Dus wij vertrokken zaterdag laatstleden naar Ambleteuse in Frankrijk. Ambleuteuse is een dorpje in het westen van Frankrijk bij het Kanaal.
Onze aankomst verliep niet helemaal onopgemerkt omdat een busje butaangas, bij een nochtans correct uitgevoerde vervangingsoperatie door mezelf, spontaan vuur vatte :-( Onze attente Belgische buurman gaf ons in alle kalmte een natte doek en het vuur was daarna zo weer uit. Mijn armen zijn enkel geschroeid, en mijn armhaar is dus wat gekortwiekt.
Maar verder verliep alles zalig. Lekker krapjes zitten aan de picknicktafel, en zondag een prachtige dag aan zee. De zee kwam nochtans erg snel op na onze aankomst, maar daar werden we netjes voor gewaarschuwd door een zeewachter. Zondagavond hadden we een erg geslaagde mini-barbecue. De kindjes lagen 2 dagen laat in ‘bed’ (slaapzak/tent).
Maandag sloten we af met een bezoekje aan Cap Gris Nez en Cap Blanc Nez. En toen zat het er weeral op. Het was G E W E L D I G !
Scrum is a framework designed to help teams create and sustain complex software products in complex circumstances through the scientific method of empiricism. Scrum has replaced the industrial, plan-driven paradigm with well-considered experimentation to better deal with the complexity and unpredictability of modern software development. And although the use of Scrum is free, its roles, artifacts, events, and rules are immutable. Implementing only parts of Scrum is possible, the result however is not Scrum. By breaking its base design it is likely that problems are covered up, instead of being revealed.
The purpose of Scrum is to help people inspect & adapt, to provide transparency to the work being undertaken, to know reality to base decisions on, to adjust, to adapt, to change, to gain flexibility. The rules, principles and roles of the framework, as described in the Scrum Guide, serve this purpose. These are the rules of the game of Scrum, the base setup to have in place.
But we distinguish principles from techniques, the what from the how, the rules of the game from tactics to play the game. It’s like in all games and sports, all players and teams play upon the same rules, yet some teams seem more successful at playing than other teams. It depends on many factors, and not all are equally controllable by the teams themselves. One factor are the tactics used by the team to play.
There are many tactics to use within Scrum. Good tactics serve the purpose of Scrum. Good tactics re-enforce the Scrum values, not undercut them.
I’ve previously described how practices from eXtreme Programming provide great tactics, ways to play Scrum, even when not mandatory from the Scrum perspective.
The Scrum Guide suggests that in the Daily Scrum meeting every player of the Team answers 3 questions (Done? Planned? Impediments?).
But the players might just formally answer the questions, limit it to a personal status update, and talk to the walls or to the Scrum Board. They just make sure that they -well- answer the 3 questions. Because the Scrum Guide tells them to, or some smart coach or Scrum Master or manager.
But is the team seeing Scrum as a methodology? Or use Scrum as a framework for discovery? It doesn’t help much if they don’t talk to each other. It doesn’t help much if they don’t surface the information to optimize their collaborative work plan for the next 24 hours against the Sprint Goal. Maybe they use the meeting only as a reporting obligation in which they make sure all their microtasks are logged, to cover against possible blame. They miss the opportunity to gain insight in the real situation, to inspect it and to adapt upon it.
Maybe Scrum should describe only ‘what’ is expected from the Daily Scrum in the time-box of 15 minutes. Although, actually, the Guide already does so by saying: “The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours.” We could eliminate or rephrase how this is exactly to be achieved, in turning the 3 questions into a good, yet non-mandatory, tactic.
The Definition of Done was rightfully given a lot more attention in the latest version of the Scrum Guide. However, some people wonder why it isn’t an official artefact. I did so too, even launching the suggestion to make it one. However, I got to see that the Definition of Done is an aid to transparency, and I overcame my urge to turn it into an artefact.
Here’s how the Definition of Done helps playing Scrum:
So, what Scrum requires is transparency. The Definition of Done is a way to provide that transparency at several levels and several occasions. It’s a great tactic that stresses the importance of seizing the opportunity to ship.
Product Backlog grooming is an activity in which the Development Team and the Product Owner look at Product Backlog currently sorted for one of the next Sprints. Certainty that the included items actually are going to be implemented is growing. So teams might want to unveil dependencies or help a Product Owner understand what is useful to know from a development perspective. Grooming increases the chances to pull the work in more easily when it is presented at the next Sprint Planning.
Product Backlog grooming is not a mandatory (time-boxed) Scrum event. The ambition of Scrum is to remain simple, yet sufficient. The ambition of Scrum is to help people and teams discover additional practices that may or may not be appropriate in their specific context. Product Backlog grooming is an activity that seems to help many teams to smoothen their Sprints, and certainly limit turbulence in the first days of a Sprint. Other teams however cope without it, and perceive it as optional or even overhead if it was mandatory from the Scrum framework.
Product Backlog grooming is a great activity within a Sprint, a good tactic to collaboratively manage Product Backlog. Some can do without however.
Sprint Planning meeting is an opportunity to inspect the actual state of Product Backlog and identify what work is most useful and feasible at the actual point in time, with the option of pouring the work into a work plan for the Sprint.
The empiricism of Scrum assumes following for the Sprint Planning:
Currently the Scrum Guide prescribes the flow of the Sprint Planning meeting:
It is however possible to respect the IN and OUT of the Sprint Planning meeting upon a different flow of the meeting. Maybe Scrum can suffice by describing only ‘what’ is expected from the Sprint Planning in its time-box without prescribing ‘how’ the Scrum Team should achieve this. Organizing it in a part 1 + part 2 might be a great tactic, but it’s probably not the only one.
Notice: following is my original description of the Scrum Values. I won’t be touching this description. I have however since the inception of this description (2012) slightly updated the descriptions. Find the latest version at https://guntherverheyen.com/the-scrum-values/ and the international translations at https://thescrumvalues.org.
Find and book a seat in the planned sessions of my Scrum Pocket Class to explore “The Value in the Scrum Values” via my webshop.
Scrum is not a methodology. Scrum is a process, but of a non-repeatable kind. Scrum is a framework of rules, roles and principles. The framework helps people and organizations discover what works best for them. Their real process emerges, and is specific and fitting to their time and context. Scrum can wrap existing product development practices or render them superfluous. The benefits of Scrum are greater when complemented by improved or revised engineering, product management, people and organizational practices. The prescriptions of Scrum have been limited to the essence. Every element of Scrum has a goal. Changing the core design of Scrum, leaving out elements, not playing the game by its base rules, covers up problems and limits the benefit of Scrum and any additions on Scrum, up to the level of making it utterly useless.
Less known than the process of Scrum and probably under-highlighted, but therefore not less important, are the core Scrum Values upon which the framework is based: Commitment – Focus – Openness – Respect – Courage. These values relate to the ethics of Scrum, thereby -from a social point of view- turning Scrum into a value system.
Although not invented as a part of Scrum, or exclusive to Scrum, these values give direction to our work, our behavior and our actions. In a Scrum context the decisions we take, the steps we take, the way we play Scrum, the practices we add to Scrum, the activities we surround Scrum with should re-enforce these values, not diminish or undermine them.
I have found it very useful to bring these more out in the open, as a way to assess the desirability our actions and activities. It’s even a great help in thinking about applying the Scrum framework itself. It is possible to do Scrum as if it was a methodology; organize the meetings, direct all players on every possible detail for every possible action within the framework. But is the framework then being used for what it’s designed for? Won’t it leave the individual, the team and the organization with limited improvements?
A good illustration is how I’ve observed some teams doing their Daily Scrum. Everybody answers the 3 questions (Done? Planned? Impediments?), in a slightly spontaneous way or -worst case- when asked for by a Scrum Master-pretend. But does the team use the meeting to share information, to collaborate in re-planning their work for that day, making sure they don’t get out of line with one another for more than 24 hours, to get the most out of the Sprint, in moving forward to the Sprint goal? Or do they talk to the board instead of to each other? Do they only use the meeting to make sure that the board holds all their micro-tasks so their work is logged?
There is a widely spread misinterpretation of the word commitment in a Scrum context. This originates mainly from the past expectation of Scrum for teams to ‘commit’ to the Sprint and the selected Product Backlog items. Upon the old, industrial thinking (that ruled software development for too many years) this was wrongly turned into the expectation that all scope would be delivered, no matter. ‘Commitment’ was wrongly turned into a hard-coded contract although it was always intended as an indication that the team would do the maximum possible effort in the Sprint and be completely transparent about progress. And in the complex, creative and highly unpredictable world of software development a commitment on scope is impossible anyhow.
And the definition of the word, according to Oxford Dictionaries, describes exactly how it was originally intended in Scrum:
So, commitment is about dedication and applies to the actions, the effort, not the final result.
Yet, in the Scrum Guide we replaced commitment as a result of the Sprint Planning with forecast. Because of the relationship with scope it helps getting explicitly rid of the wrong interpretation. And fortunately ‘forecast’ greatly aligns with the empirical nature of Scrum too.
Still, commitment is and remains a core value of Scrum.
We commit to the team. Commit to quality. Commit to collaborate. Commit to learn. Commit to do the best we can, every day again. Commit to the Sprint Goal. Commit to be professional. Commit to self-organize. Commit to excellence. Commit to the agile principles. Commit to create working software. Commit to look for improvements. Commit to the Definition of Done. Commit to the Scrum framework. Commit to focus on Value. Commit to finish work. Commit to inspect & adapt. Commit to transparency. Commit to challenge the status-quo.
An iterative-incremental approach like Scrum and the time-boxing of Scrum allow us to focus. We focus on what’s most important now without being bothered by considerations of what at some point in time might stand a chance to become important. We focus on what we know now and YAGNI (You Ain’t Gonna Need It) helps retaining that focus. We focus on what’s most nearby in time as the future is highly uncertain and we want to learn from the present to gain experience for future work. We focus on the work to get things done. We focus on the simplest thing that might possibly work.
The empiricism of Scrum requires transparency, openness. We want to inspect reality in order to make sensible adaptations. We are open about our work, our progress, our learning and our problems. But we are also open for people, and working with people; acknowledging people to be people, and not resources, robots or replaceable pieces of machinery as software development -after all- is still the work of humans. We are open to collaborate across disciplines and skills. We are open to collaborate with stakeholders and the wider environment. Open in sharing feedback and learn from one another. Open for change as the organization and the world it operates in change unpredictably, unexpectedly and constantly.
We show respect for people, their experience and their personal background. We respect diversity (it makes us stronger). We respect different opinions (we might learn from it). We show respect for our sponsors by not building features that nobody will use. We show respect by not wasting money on things that are not valuable or might never being implemented or used. We show respect for users by fixing their problems. We respect the Scrum framework. We respect our wider environment by not behaving as an isolated island in the world. We respect each other’s skills, expertise and insights. We respect the accountabilities of the Scrum roles.
We show courage in not building stuff that nobody wants. Courage in admitting requirements will never be perfect and that no plan can capture reality and complexity. Courage to consider change as a source of inspiration and innovation. Courage to not deliver undone software. Courage in sharing all possible information (transparency) that might help the team and the organization. Courage in admitting that nobody is perfect. Courage to change direction. Courage to share risks and benefits. Courage to promote Scrum and empiricism to deal with complexity. Courage to let go of the feint certainties of the past. We show courage to support the Scrum Values.
Paul van Vliet heeft vele mooie liedjes, maar eentje heet “Veilig op de fiets”. Het beschrijft de veiligheid en geborgenheid die een zoon voelt, jawel, achterop bij zijn vader op de fiets.
Veilig achterop bij vader op de fiets
Vader weet de weg en ik weet nog van niets
Veilig achterop, ik ben niet alleen
Vader weet de weg, vader weet waarheen
Onbewust dreven het voorbije weekend mijn gedachten in de richting van dit lied, het weekend dat we de aanhangfiets voor onze Down-zoon, Jente, in gebruik namen. Deze aanhangfiets zorgt ervoor dat we voor korte trips niet steeds de auto moeten nemen. En ik hoop dat Jente ook vreugde en veiligheid voelt onder het mom “Veilig aangehaakt, bij vake aan de fiets”.
| Scrum Artifacts: Wha… on Meetings in Scrum, actually | |
| Zmiany w Scrum Guide… on There’s value in the Scr… | |
 | yy on A Foundation for the Future |
 | ServiceNow CSA Exam on There’s value in the Scr… |
 | Prepare for ServiceN… on There’s value in the Scr… |