<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Ender Yuksel on Medium]]></title>
        <description><![CDATA[Stories by Ender Yuksel on Medium]]></description>
        <link>https://medium.com/@ender.yuksel?source=rss-35edec9320cc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*ByclSmjN6_w0agW2.jpg</url>
            <title>Stories by Ender Yuksel on Medium</title>
            <link>https://medium.com/@ender.yuksel?source=rss-35edec9320cc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 01:20:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ender.yuksel/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How we converted our classroom agile training into a virtual interactive one?]]></title>
            <link>https://medium.com/@ender.yuksel/how-we-converted-our-classroom-agile-training-into-a-virtual-interactive-one-f649e9c18228?source=rss-35edec9320cc------2</link>
            <guid isPermaLink="false">https://medium.com/p/f649e9c18228</guid>
            <category><![CDATA[interactive-training]]></category>
            <category><![CDATA[virtual-training]]></category>
            <category><![CDATA[remote-training]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Ender Yuksel]]></dc:creator>
            <pubDate>Wed, 17 Jun 2020 15:37:33 GMT</pubDate>
            <atom:updated>2020-07-01T16:03:39.062Z</atom:updated>
            <content:encoded><![CDATA[<h3>How we converted our classroom agile training into a virtual interactive one</h3><p>When you join SimCorp, you feel the genuine interest of a company in your development. You are invited to a 3-weeks training that is called SimCorp Dimension Academy where you enjoy gaining new skills, and start growing your professional network.</p><p>After the academy, you continue to receive training offers, such as <em>Agile Ways of Working at SimCorp</em>. This training is a full-day classroom training, with minimal teaching or lecturing. Most of the day, participants join cleverly designed exercises that would let them experience and figure out the drawbacks of non-agile approaches, and realize the WHYs of the ways of we work.</p><p><em>That was, until the world changed with a pandemic.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fy_VkAo32JvC3ak9ZLXAdg.jpeg" /><figcaption>Illustration by Virpi Oinonen from <a href="https://www.businessillustrator.com/">https://www.businessillustrator.com/</a></figcaption></figure><p>As a company we were not behind in any ways, when it came to transformations and adapting to new situations. We were also lucky that we were still onboarding new employees, and there was the need for continuing our agile training as a part of onboarding. In this article, I will tell our short story of turning classroom agile training into virtual interactive training, mostly sharing the practical side, hoping that it can inspire and help others trying to achieve similar goals. Remember the academy from the first paragraph? That also responded fast, as my good colleague Susan Johansson explained in her article <a href="https://www.linkedin.com/pulse/how-transform-classroom-training-remote-from-ilt-vilt-susan-johansson/?trackingId=dPZelEUxfiOgJhXvvEJC%2Fg%3D%3D">How to transform classroom training to remote: From ILT to VILT in 2 business days</a></p><h3>How to convert your highly interactive classroom course?</h3><h4>Gather your team to design and deliver the course</h4><p>As soon as you learn about the needs (i.e. sufficient number of new employees) and the limitations (i.e. physical gathering is not a possibility), you better start building your team to prepare and deliver the online training. I reached out our community for volunteers, and gathered a team of 8 spanning three different roles and three different countries. Yes, we run the training with volunteers, and yes we have a big (agile) community that can give a hand with such initiatives.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tGWKRSVKW8i7OauGlDEszg.png" /></figure><p>Why is the team so big? For many reasons:</p><ul><li>Ensuring continuity</li><li>Benefiting from diverse perspectives</li></ul><p>On the other hand, no one needs to stay present during the whole training — though the more one can stay the better, for both helping the facilitators and joining breakout rooms to help participants with their exercises.</p><h4>Design the course</h4><p>We collaborated in gathering the needs and generating ideas, both synchronously (on two touch points) and asynchronously (using chat channels, also with the community)</p><p>In this phase we focused on</p><ol><li><strong>content, format, timing</strong>: Obviously, getting this part right is something to be prioritized. Because we could not announce the new session of the training without the date/format/content. Besides, when you set these parameters, then you have an agenda with <em>who will do what, and when, and for how long </em>kind of information in front of you.</li><li><strong>division of labor</strong>: After setting the content, it is important to make team members own the content. Based on experience, I facilitated forming pairs to own each topic. This way, we both have higher quality content, and a backup per content in case an owner gets ill or somehow becomes absent.</li><li><strong>check points / syncing</strong>: After pairs owning topics, they are expected to self-organize and decide their own ways of collaboration. However, we also need to sync periodically and show us how far we came. Based on experience, designing parts of a course in pairs may easily lead into isolation, and if we don’t sync and align, we can end up with overlapping content and even worse overlapping exercises.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7FUCR4exEq2S8UyzLw6neA.png" /><figcaption>Full day classroom course agenda turned into a three half days virtual course agenda.</figcaption></figure><p>We decided to work with one-week sprints, at the end of which we would review the progress and provide each other feedback, and ensure alignment and coherence. In the end, this whole training must be felt as a single-stream by the participants. We can easily come up with a list of DOs and DON’Ts:</p><blockquote>DO</blockquote><ul><li>Make sure that learnings from an earlier topic can be used in the latter topics</li><li>Spread the course time in several days, each day not being more than 3 hours</li><li>Try to stick to the tools and teaming from the beginning of the course</li><li>Make use of asynchronous communications, by pre-recording parts of the course so that the participants can watch them on their own time and in their own pace.</li><li>Use the remote sessions mostly for discussing, and elaborating the parts that participants are in doubt about.</li></ul><blockquote>DON’T</blockquote><ul><li>Use too many different tools</li><li>Plan full day remote sessions</li><li>Lecture or run long slide shows.</li></ul><p>We initially planned two-sprints, with the following sprint goals:</p><p>Sprint 1: topic owners start working, and share their plans and ideas in the end of the sprint</p><p>Sprint 2: topic owners finalize their parts and share how they will deliver their parts</p><p>Then we had to move the dates forward, in order to accommodate public holidays in different countries, which won us an extra sprint to prepare.</p><h4>Know Your Technology and Tools</h4><p>This is one of the tricky bits, as participants engagement can be damaged, and unfamiliarity with the tools can backfire, and participants can forget the fact that tools are just the means and not more; in the case of anything going wrong.</p><p>We have devoted the first session to make sure that the participants have a working setup, and they can get the necessary support for getting up and running. This session not only included the video communication tool, but also the various collaboration that would be used throughout the training. In addition, there is a certain culture that we must reinforce. Keep your camera on, mute your mic when you are not talking, raise your hand (physically or use the button) to have a word, etc. If you want to raise the bar even higher, use a headset instead of your laptop’s mic and speakers, use an external webcam so that you can adjust (especially brightness and zoom) better, pick a background photo that conceals any messy background, use two screens (one dedicated to the video feed, and other for any collaboration tool being used).</p><p>We also based our tool selection on our needs and the capabilities of the tools. For example, we need to keep the energy and engagement as high as possible, hence being able to see all the faces at once was a distinguishing criterion on the video communication tool selection (I am sure you guessed the tool correctly, here). Another example, being able to interact without the need to create a user account or any sort of login was a similar differentiator on the whiteboard tools selection. And then some tools are almost flawless in mimicking the physical (using flip-charts, index cards, markers, voting dots, timers, etc.) experience for instance when running Lean Coffee or retrospectives, so we also benefited from those, while not exaggerating the number of digital tools we introduced to the audience.</p><blockquote>In this article, I am not naming the tools we used or posting artifacts (except for the group photo screenshot below which reveals the communication tool), yet I will be happy to share experiences if you contact me directly.</blockquote><h4>Remember that Icebreakers, Recaps, and Breaks are even more important</h4><p>When everyone is sitting on a chair alone, in front of a screen, wearing headsets, it becomes even more important to create the feeling of a group with common purpose. It is harder to make connections and sustain the focus. Therefore, auxiliary parts of the classroom course suddenly become game changers.</p><p>You might have seen the viral video of students passing a pencil between their video feeds during an online course. Try it as an icebreaker, you will realize that it is harder than it seems, yet it is one of the best ice breakers nurturing coordination and team feeling in such an online training.</p><h4>Find cyber walls for your flip-charts</h4><p>We love to fill al the vertical spaces during classroom trainings! Mostly the results of the exercises during the day, but also stationary posters such as Goal of the training, Agenda, Ground Rules, Parking Lot, Continuous Feedback, Sharing good resources, etc.</p><p>You can still keep those, in a shared medium. In our case, we used a OneNote notebook where each tab corresponded to what we would have as a flip-chart poster. Besides, the participants would be able to write on those, and add new ones if needed.</p><h4>Know your audience</h4><p>Typically the design of the training is done before the participants register. Still, there may be room for fine tuning and making adjustments in order to best accommodate the diversity in the participants. In our case, our participants were joining from Denmark, Germany, Italy, and Ukraine; generally possessed development team member roles, and already started working in different parts of the organization.</p><h4>Take a group photo</h4><p>Taking a group photo has never been easier! Besides it is such a nice way to end the training. Ask for permission from the audience, of course. In case there are people who would not like to be in the photo they can always turn their camera off or leave the session temporarily. Then take a screenshot! There you go! Don’t forget to ask for another permission, this time using it for the training promotion :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QTSJR4tSP8pR8sPuFL60ng.png" /></figure><h3>Acknowledgements</h3><p>First and foremost, all the work and insights I presented above come from the talented team of facilitators that designed and delivered the course: Christian Eske Bruun, Dmytro Balaba, My Ngoc Diem Tran, Oleksandr Kramarov, Pawel Olchowik, Renato Andre Takayama Claudino, and Sven Kühnel. You are such an amazing team to work with!</p><p>Many thanks to Frank Olsen and Piet Syhler, who built the classroom course in the first place, and started running it with volunteers.</p><p>Kudos and many thanks to Kateryna Dmytriieva for the great support on the course organization and promotion.</p><p>Last but not least, thanks to all the participants (only a subset of them being in the group photo above) who brought their best versions and helped us to think and improve with their great questions and feedback!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f649e9c18228" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My XP Conference Experience]]></title>
            <link>https://medium.com/@ender.yuksel/my-xp-conference-experience-eab3d78415c6?source=rss-35edec9320cc------2</link>
            <guid isPermaLink="false">https://medium.com/p/eab3d78415c6</guid>
            <dc:creator><![CDATA[Ender Yuksel]]></dc:creator>
            <pubDate>Fri, 12 Jun 2020 12:03:19 GMT</pubDate>
            <atom:updated>2020-06-12T12:03:19.110Z</atom:updated>
            <content:encoded><![CDATA[<p>My keen followers, if such thing exist, would perhaps remember my very first post in this medium: <a href="https://medium.com/@ender.yuksel/my-agile-conference-experience-ad395308774d">My Agile Conference Experience</a>. In that post, I took the time to share as much as possible in terms of my learnings, from my hand-written notes from the sessions I attended, and really took the time to make a full-fledge and rather detailed story.</p><p>This time, I would like to write about the <a href="https://www.agilealliance.org/xp2020/"><em>XP Conference 2020</em></a><em>, another flagship </em>(and special, in the sense that you can listen to both academic work and practitioner work) conference in Agile . However, in a very different way. It is not about the sessions I attended, but more or less everything else.</p><p>Disclaimer, I don’t have the time (and perhaps ability) to write short, hence here is yet another long read</p><h3>How it all started?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G6DhlcIh3MfBo_GwrogPUA.png" /></figure><p>Sharing experience was something that SimCorp’ers were good at it, with amazing reports that I always recommend people when we talk about organizational topics, such as <a href="https://www.agilealliance.org/resources/experience-reports/what-safe-doesnt-tell-you/">What SAFe doesn’t tell you</a> (XP’18) and <a href="https://www.agilealliance.org/resources/experience-reports/is-team-self-selection-the-obvious-choice/">Is team self-selection the obvious choice?</a> (XP’19). As you can see in my Slack post from March 2019 above, that is where my story started, namely I decided to “share” in a relatively more formal way, with a relatively more diverse audience.</p><p>We had multiple areas that I thought sharing would be interesting, and with a little bít of courage I decided to have two submissions in two of my favorite areas: “recruitment and onboarding for agile teams” and “the collaboration between manager and scrum master”. I wouldn’t expect that both of the submissions would be accepted, but I didn’t intend to increase the chance of acception by multiple submissions, either. It had something to do with exploiting the convenience of the location, as I wouldn’t have to deal with travels and accommodation since the conference venue was simply 5 minutes of cycling distance from my workplace. Eventually, both of the submissions were found interesting (by their abstracts and related content we provided), so the writing journey started.</p><h3>All estimations are wrong!</h3><p>You might know the cases where you try to come up with your safest estimation for how much effort it would take to accomplish something, and then you multiply the estimation by 3, because you know that your estimation would still be far off from reality! This was one of the cases, so with one of my co-authors, we started weekly meetings from October, even though the experience that we were going to share was already there, it was merely producing a decent report structure and writing. Though we haven’t invested too much time per week, the process lasted until around May, hence there is a significant effort in total.</p><h3>Then comes the Pandemic!</h3><p>The first time I attended a conference as a speaker was in 2005, and it was an academic conference, where I presented my research work. After that I constantly presented in academic conferences until 2012, as in academia making research and publishing the findings, and then presenting, is the name of the game. After leaving academia, I still had a fair relation with (this time practitioner) conferences, however this was the first time with a <em>premium </em>conference that had to be fully virtual, due to pandemic! It was also the first time, for the conference organizers.</p><p>Would it be possible to run such a huge conference (9 different tracks spanning 5 days), using the existing remote collaboration tools?</p><h3>What did I learn?</h3><p>Our submissions were in the Experience Reports track, where the track chairs decided to pre-record the presentation, also cutting down the durations. And, there comes <strong>my biggest learnings from XP 2020</strong>:</p><h4>How to produce a video recording, showing both speakers videos and a dynamic background (e.g. slide deck)?</h4><p>For this part, I tried different solutions, such as recording functionalities of the video communication / colaboration tools, and then decided on <a href="https://obsproject.com/">OBS Studio </a>— an open source software for video recording and streaming. It was also easy for me to give an introduction and kick-start to my co-authors who haven’t used it before.</p><p>I purchased an extra microphone to capture sound better, though using a headset would also do. I used an external camera, instead of an embedded camera, so that I could adjust a lot of things such as brightness, zoom, etc. Below, you can see my setup where the camera is between two screens (upper one has the transcript that I am reading and the lower one is the recording software.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6w-yipELs8lW6S1D_iQeUw.jpeg" /></figure><h4>How to edit the video recordings produced by me and my co-authors, so that it fits in the timebox, and the discrepancies (in volume, color, etc.) are corrected?</h4><p>For this purpose, I learned to use <a href="https://shotcut.org/">ShotCut</a>, another open source software. When you have pages of content (4500+ words in each of the reports: <a href="https://www.agilealliance.org/resources/experience-reports/what-have-we-learned-from-recruiting-and-onboarding-for-agile-teams/">What have we learned from recruiting and onboarding for agile teams?</a> and <a href="https://www.agilealliance.org/resources/experience-reports/development-manager-a-scrum-masters-best-friend/">Development Manager: A Scrum Master’s Best Friend!</a>) and only 10 minutes to present, it really becomes important to trim even the silent parts between sentences. Following our good habit of working with short batch sizes, I produced a lot of separate recordings. This made editing process more interesting. Besides, I had to equalize the volume level differences.</p><p>Overall, my top two learnings were surprisingly not about the topics of the conference, but about recording and publishing the recordings. Below are the results, obviously there is a long way to go!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FODsIt-62GWg%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DODsIt-62GWg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FODsIt-62GWg%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/d9b2485bf4032efd9f512791513b53de/href">https://medium.com/media/d9b2485bf4032efd9f512791513b53de/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F2kBjiGNNYqM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D2kBjiGNNYqM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F2kBjiGNNYqM%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6bea719c6088237bc28901ef3faff4d9/href">https://medium.com/media/6bea719c6088237bc28901ef3faff4d9/href</a></iframe><h3>The heroes!</h3><p>Obviously, I have many heroes that I would like to thank!</p><ul><li><strong><em>The frontrunners, who paved the way</em></strong>: Frank Olsen, Martin Lohmann, Neil Cook, Niels Harre, Piet Syhler</li><li><strong><em>The leaders in the Experience Reports track</em></strong>: Bonnie Aumann, Frank Olsen (again), Nathalie Hammering, Rebecca Wirfs-Brock</li><li><strong><em>My dear co-authors</em></strong>: Christian Eske Bruun and Martin Schwalbe Lohmann.</li></ul><p>And my super heroes:</p><ul><li><strong><em>Maria Paasivaara</em></strong>: For orchestrating the whole organization as the conference chair.</li><li><strong><em>Jutta Eckstein</em></strong>: For being hiper-active in Slack/Twitter and all possible media to share knowledge and help participants.</li><li><strong><em>Paolo Tell</em></strong>: Running the technical part of the show, in front of a dozen screens.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eab3d78415c6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A selection of my learnings from GOTO CPH 2019]]></title>
            <link>https://medium.com/@ender.yuksel/a-selection-of-my-learnings-from-goto-cph-2019-320b27afaa65?source=rss-35edec9320cc------2</link>
            <guid isPermaLink="false">https://medium.com/p/320b27afaa65</guid>
            <category><![CDATA[goto-conference]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Ender Yuksel]]></dc:creator>
            <pubDate>Tue, 26 Nov 2019 12:33:08 GMT</pubDate>
            <atom:updated>2019-11-26T12:33:08.905Z</atom:updated>
            <content:encoded><![CDATA[<p>Last week I attended the <a href="https://gotocph.com/2019">GOTO conference</a> in Copenhagen, Denmark. Let me share <em>some </em>of my <strong>learnings </strong>with you.</p><p><em>&lt;&lt;All drawing credits (for all the media in this story) to </em><a href="https://twitter.com/MindsEyeCCF"><em>Ashton Rodenhiser</em></a><em> and all photo credits to Farhood Hakha.&gt;&gt;</em></p><h3>from Stephen Carver</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sVuliEcOSMOzbULVU409yA.jpeg" /></figure><p>As a fan of Space Shuttles, I honestly was not expecting to learn many new things on the subject. As a relatively new manager, however, I learned important lessons from <a href="https://gotocph.com/2019/speakers/991">Stephen Carver</a>’s opening keynote. Part of it is the “<em>not to do </em>list”, from NASA’s mistakes leading to two disasters with Space Shuttles:</p><ul><li>Too much management</li><li>Too little leadership</li><li>Silos</li><li>Politics</li><li>Management by fear</li><li>Compliance over innovation</li><li>Communication breakdowns</li></ul><blockquote>And wisdom from Einstein: “The intuitive mind is a sacred gift, and the rational mind a faithful servant. We seem to have created a society that honors the servant and has forgotten the gift.”</blockquote><h3>from Roy Osherove</h3><p>This was one of my favorite sessions of all. I recommend it (recording available) to all my colleagues especially the ones that are using metrics.</p><ul><li>Book recommendation: How to Measure Anything: Finding the Value of “Intangibles” in Business by <a href="https://www.goodreads.com/author/show/249999.Douglas_W_Hubbard">Douglas W. Hubbard</a></li><li>Questions to ask your teams: “How confident are you that a) the code in production works, b) the tests will catch bugs in production code”</li><li>Don’t measure how often the build gets broken, measure how quickly it gets fixed.</li><li>Pay attention to the distinction between leading and lagging indicators</li></ul><h3>from Linda Rising</h3><p>No conference is complete without Linda Rising, and here is my favorite quote from her this time:</p><ul><li>You should never have a meeting where everyone is a already a believer. Diverse groups make better decisions!</li></ul><h3>from Jessica Pointing</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kyqzRrwrfTBfKv5fwIDCqQ.jpeg" /><figcaption>Quantum Computing — <a href="https://gotocph.com/2019/speakers/937">Jessica Pointing</a></figcaption></figure><p>I have learned so much in this session, surprisingly <em>in terms of presentations techniques</em>. Jessica used so many visual elements to explain technical concepts from huge plush toys (to represent bits) to a large bag of balls (for mimicking searching algorithms). Besides she set up an experiment on the stage and used her phone as a camera to stream her experiment on the large screens with the audience.</p><h3>from Steve Wozniak</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gdAn-SXcbXSxiQKYMa_xhg.jpeg" /><figcaption>Q&amp;A — <a href="https://gotocph.com/2019/speakers/1111">Steve Wozniak</a></figcaption></figure><p>Woz is a hero for my generation, and this was truly a special experience for me. There wasn’t a talk or speech prepared, but there were many questions from the audience and I was impressed by all the honest answers and the wisdom.</p><ul><li>Happiness is the 3 Fs: Food, fun, and friends!</li><li>Things that might look like simple from outside, are often hard to achieve and take time.</li><li>If it’s your own, you’ll do whatever is needed to make it better than anyone else.</li></ul><h3>from John Le Drew</h3><p>This talk was about the product owner role, and here is the set of pillars for the role:</p><ul><li>Respect people</li><li>Embrace uncertainty</li><li>Small experiments</li><li>Continuous learning</li><li>No complacency</li></ul><h3>from Other Speakers</h3><p>Below are visual-summaries of some more sessions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K6oIouu0f0WkNYE45Oow8Q.jpeg" /><figcaption>Responsible AI for Engineers — <a href="https://gotocph.com/2019/speakers/1184">Ron Bodkin</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YhLGSho3jB0dGePkdwG8JQ.jpeg" /><figcaption>Does agile make us less secure? — <a href="https://gotocph.com/2019/speakers/1182">Michael Brunton-Spall</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*encfGkNMthb0AWfiC305mg.jpeg" /><figcaption>Design For The Utopia You Want, Not The Dystopia You’re In — <a href="https://gotocph.com/2019/speakers/1120">Chris Atherton</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KMHoU3VXcaIUmI5pNY4qqQ.jpeg" /><figcaption>Is Business The Key To Making The World A Happier Place? — <a href="https://gotocph.com/2019/speakers/1051">Evan Sutter</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d73UzjEE6KcAG7tZeN6vnA.jpeg" /><figcaption>Composing Bach Chorales Using Deep Learning — <a href="https://gotocph.com/2019/speakers/987">Feynman Liang</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*k9Z2SWYlIazU8XN0OkOcdA.jpeg" /><figcaption>Thinking Like a Data Scientist — <a href="https://gotocph.com/2019/speakers/1150">Em Grasmeder</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JHRyu15jFobdVCY-CCpAfA.jpeg" /><figcaption>How to Be Human in the Age of The Machine — <a href="https://gotocph.com/2019/speakers/1057">Hannah Fry</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*egFz4rMKKzlYpauAdjMkEw.jpeg" /><figcaption>A Practical Guide to Cybercrime — <a href="https://gotocph.com/2019/speakers/1097">Richard Clayton</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rVrcufMWEwTt5V58-aPq5A.jpeg" /><figcaption>#DigitalNudge — The Hidden Forces that Shape our Digital Decisions — <a href="https://gotocph.com/2019/speakers/1148">Fabio Pereira</a></figcaption></figure><p>Some of these sessions are recorded and the recordings are available in to GOTO Play video app! Some of the sessions are very inspiring, and does not requiring anyone to be technical at all — <em>I already re-watched some of my favorite sessions with my wife!</em> I fully recommend you to have a look at the wide selection of talks in the app.</p><h4>Acknowledgements</h4><p>Once again, thanks a lot to <a href="https://twitter.com/MindsEyeCCF">Ashton Rodenhiser</a> for all the great drawings above and thanks a lot to Farhood Hakha for capturing them.</p><p>Thanks to all the speakers, conference organizers, my sponsor SimCorp (also a sponsor for the conference), all the fellow participants, and finally the Copenhagen Airport where I wrote this story while waiting for my flight to Kyiv, Ukraine.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=320b27afaa65" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to be Agile when writing your Master Thesis]]></title>
            <link>https://medium.com/@ender.yuksel/how-to-be-agile-when-writing-your-master-thesis-e31885dc6f02?source=rss-35edec9320cc------2</link>
            <guid isPermaLink="false">https://medium.com/p/e31885dc6f02</guid>
            <category><![CDATA[academia]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[science]]></category>
            <category><![CDATA[thesis]]></category>
            <dc:creator><![CDATA[Ender Yuksel]]></dc:creator>
            <pubDate>Thu, 19 Sep 2019 18:49:15 GMT</pubDate>
            <atom:updated>2019-09-19T18:49:15.786Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jRIx-2vso4TMgx6sST9GCA.jpeg" /></figure><p><strong>Why should you read this story (always starting with <em>why</em>)?</strong></p><ul><li>You will find out how being agile helps getting the most out of academic work.</li><li>You will read about a concrete example from a recent master thesis, that can inspire both students and supervisors to try some agile practices.</li><li>You will be provided with interesting pointers along the way.</li></ul><h4>Part I: From software professionals to academia</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/1*aP6-Pe0ue2-AuosGGcaQYQ.jpeg" /><figcaption>An iconic article from the history of agile from 1986. Jeff Sutherland, co-creator of Scrum, states that Scrum was directly modeled after this paper.</figcaption></figure><p><a href="https://agilemanifesto.org/">Manifesto for Agile Software Development</a> turned 18 this year. Even though there are people that would visit Snowbird Ski Resort in the Wasatch mountains of Utah — where the Manifesto was crafted — as their Mecca, the movement dates way back than that. The first paragraph of <a href="https://hbr.org/1986/01/the-new-new-product-development-game">Hirotaka Takeuchi and Ikujiro Nonaka’s iconic Harvard Business Review article</a> dating January 1986 goes:</p><blockquote>In today’s fast-paced, fiercely competitive world of commercial new product development, speed and flexibility are essential. Companies are increasingly realizing that the old, sequential approach to developing new products simply won’t get the job done.</blockquote><p>Agile removes the heaviness of the traditional development methodologies, in order to promote quick response to changing environments.</p><p>Although the research community devoted a great deal of attention to it, <strong><em>agile is not a concept that is invented in the academia and then transferred to industry</em></strong>. It is something that primarily came from software and product professionals.</p><h4>Part II: Do you need a manifesto for being agile?</h4><p>Taking the manifesto concept and re-branding for another area is not a new thing: <a href="https://www.agilehrmanifesto.org/">agile HR manifesto</a>, <a href="http://agilemarketingmanifesto.org/">agile marketing manifesto</a>, <a href="https://agilebusinessmanifesto.com/agile-business-manifesto/">agile business manifesto</a>, <a href="https://bbrt.org/the-beyond-budgeting-principles/">beyond budgeting principles</a>, and even <a href="https://beyondagilemanifesto.org/">beyond agile manifesto</a> suggested by Kent Beck (one of the signatories of the original manifesto and the brain behind extreme programming) in 2011.</p><p>Obviously, enough googling will help you hitting a manifesto that is modified to fit the academic work. Here is <a href="https://xamat.github.io/AgileResearch/index.html">agile research manifesto</a> that is using exactly the same format of four value statements and twelve principles of the agile manifesto, by Xavier Amatriain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HxH0j43ECQbgV4Mbey53xw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/856/1*4ZMa21V4n8p7oXPfMFL6ZA.png" /><figcaption>If you are too lazy to read all principles in a new manifesto, I would recommend performing a simple diff to see the differences to the original manifesto.</figcaption></figure><p>I would say, <strong><em>one does not need a manifesto for being agile in a domain, nor abiding a manifesto automatically makes you agile</em></strong>.</p><h4>Part III: What are the benefits of being agile in the research context?</h4><p>There are certain behavior that come natural to a researcher such as being curious and having a questioning mind, in addition to certain other behavior that the publication system require such as courage to accept feedback and willingness to improve.</p><p>On top of that, there are tangible advantages of being agile. Below is an incomplete list of benefits of being agile in the research context.</p><ul><li><strong>Faster time to <em>academic market</em></strong>: as in the industry, if you have a good idea or a good approach, then you need to be fast in delivering that to the community by different means.</li><li><strong>Increased academic value</strong>: If you prioritize your work based on the value, and incrementally deliver results, you would ensure that academia and eventually the society will receive the greatest value out of your efforts.</li><li><strong>Reduced waste:</strong> Iterative research, short iterations, and faster feedback will reduce the risk of waste in your work.</li><li><strong>Better quality:</strong> Although quality can be interpreted in different ways, continuous and relentless improvement in the process and ensuring close collaboration of researchers and applying technical stakeholders will result in better quality regardless of your definition of good quality research.</li></ul><h4>Part IV: A good example from a very recent Master thesis</h4><p>Mads Schnoor Hansen conducted his master thesis studies in computer science, contributing to a large project — <a href="https://www.qualityoflifetechnologies.com/">Quality of Life</a> — headed by associate professor Katarzyna Wac, in the University of Copenhagen. The research and development task at hand was unfamiliar to him and together with his supervisors they expected unforeseen challenges and changes along the way. Hence, being agile was necessary! They stuck to the values and principles that are common to agilists, and synthesized practices from various different development methods:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C7xyjSRwVVatdG6PRNKLow.jpeg" /><figcaption><em>The </em><a href="https://www.qualityoflifetechnologies.com/">Quality of Life</a> technologies lab<em>, founded and headed by Katarzyna Wac (fourth from the left), conducts research at the University of Copenhagen, University of Geneva, and Stanford University.</em></figcaption></figure><ul><li><strong><em>Small cross-functional team</em></strong>: team of five, combining skills in theory and practice</li><li><strong><em>Iterative development</em></strong>: pulling work into iterations of two weeks — not planning everything upfront</li><li><strong><em>Virtual Kanban board</em></strong>: visualizing the status of work items in an iteration (they used Trello as a free solution)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-AdH37Sn1xJvy5enLmX4BA.jpeg" /><figcaption>A virtual board with states Backlog (not pulled into iteration), ToDo (pulled into the current iteration), Doing (work items in progress), Blocked, and Done.</figcaption></figure><ul><li><strong><em>Sized work items</em></strong>: relative estimation for work items (they used story points and agile poker)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TyaGydKtBz-_StkDv1y1mQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4YMf6YZU2WPD2Pz0DyMpqA.jpeg" /><figcaption>The team used the <strong><em>original </em></strong><em>(not modified)</em><strong><em> </em></strong>Fibonacci Sequence for relatively sizing the work items. And to do that, you do not need any fancy cards or apps, just use standard cards (ace, 2, 3, 5, 8) and overload King as 13, Joker as 21 (or infinity). From left to right: Mads Schnoor Hansen, Jamshed Gill,<strong> </strong>Vlad Manea (co-supervisor). Ece Elbeyi and Katarzyna Wac (supervisor) were also part of the team, though they are missing in the picture.</figcaption></figure><ul><li><strong><em>Technical excellence</em></strong>: white board discussions around architecture, XP practices such as pair programming, different levels of testing</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/985/1*Fs5Bo9yOU03L9vPaHVMPnQ.jpeg" /><figcaption>A state machine annotated with data security details.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/1*c6GdGJc-veSei5e3Vf8quA.jpeg" /><figcaption>System design.</figcaption></figure><h4>Retrospective</h4><p>One of my recent aha moments is while reading <a href="https://www.goodreads.com/book/show/261666.Fearless_Change">Fearless Change</a> (authored by Linda Rising and Mary Lynn Manns) where there is a quote from Anne Frank’s diary:</p><blockquote>How noble and good everyone could be if, every evening before falling asleep, they were to recall to their minds the events of the whole day and consider exactly what has been good and bad. Then without realizing it, you try to improve yourself at the start of each new day.</blockquote><p>I guess I was too young to see the wisdom in the lines above, when I first read the diary. Now looking at it, I cannot formulate a better way of explaining retrospectives and continuous improvement.</p><p>When Mads and his team recall the events of the whole master thesis and consider what has been good and bad, they see a lot of benefits of being agile throughout their study. As they expected in the beginning, many things changed along the way, and they could adapt with minimum waste and maximum value.</p><p>Did you find this interesting? Then please share it with someone you know that is about to start a timeboxed academic work. Do you have questions? Then please leave a response below. Thank you for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e31885dc6f02" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What can development teams learn from Copenhagen buses?]]></title>
            <link>https://medium.com/@ender.yuksel/what-can-development-teams-learn-from-copenhagen-buses-5b254896550b?source=rss-35edec9320cc------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b254896550b</guid>
            <category><![CDATA[copenhagen]]></category>
            <category><![CDATA[lean]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[flow]]></category>
            <dc:creator><![CDATA[Ender Yuksel]]></dc:creator>
            <pubDate>Sun, 08 Sep 2019 19:23:24 GMT</pubDate>
            <atom:updated>2019-09-09T12:13:47.543Z</atom:updated>
            <content:encoded><![CDATA[<p>Foreword: Thanks to my good colleague Vadym Volkovynskyi for the analogy that I use in this story.</p><h3><strong><em>CHAPTER 1: A tale of two bus lines</em></strong></h3><p>Do you recall the country that is always on the top of the world happiness and life satisfaction indexes? Yes, we are talking about Denmark, and to be precise the capital city of Denmark, Copenhagen! This <a href="https://www.visitcopenhagen.com/">wonderful city </a>had a famous bus line, 5A, that served the capital between 2002 and 2017. It was the first A line (special line that runs more frequently and it has many bus stops with relatively shorter distances) bus, and its route was relatively long, passing through the city center in the middle of the route. Besides, it was the busiest bus line of the whole country, carrying more than 20 million passengers every year.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/950/1*KUvLz7TiLyRIKTc7ThNLaA.png" /><figcaption>Route of 5A as of October 2015, between Husum Torv (northwest) and Copenhagen Airport (southeast), passing through the city center. Source: <a href="https://da.wikipedia.org/wiki/Linje_5A#/media/Fil:Copenhagen_bus_line_5A_2015.png">Wikipedia</a></figcaption></figure><p>The buses used in the line were regular sized (13.7 meters), and the passengers would enter from the front door, exit from either the middle door or the rear door.</p><p>As it was the busiest bus line, you would occasionally read in the newspapers various optimization suggestions from the experts — not selling ticket on the bus, different door entry/exit combinations, route optimizations, etc. Besides, there were many attempts to observe other cities and experiment with different set ups in order to ease the capacity problems, especially in the rush hour.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cjQnPzJZw7KFdADo_2DVAw.jpeg" /><figcaption>A 5A bus on a bridge that connects two islands that Copenhagen is located on. The red stripe indicates that it is an A-line. Source: <a href="https://da.wikipedia.org/wiki/Linje_5A#/media/Fil:Movia_bus_line_5A_on_Langebro.jpg">Wikipedia</a>.</figcaption></figure><p>After years of experimentation, line 5A was transformed to line 5C in 2017. C-line was new, indicating city line concept, and 5C is the first example of a C-line. It was a transformation (!) like the agile transformations or cloud transformations that you can hear frequently these days. New bus type, more seats (147 instead of 82 in 5A) and space, more doors, new entry/exit combination (all 5 doors could be used for entry/exit), dedicated bus lanes in some parts of the route, option of checking in/out the using the card readers in the bus stop, rather than doing it using the card readers inside the bus, biogas engine, and more!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Il-ALXOQSRHWpp2yGemVCg.jpeg" /><figcaption>5C bus on the day of launch. Source: <a href="https://da.wikipedia.org/wiki/Linje_5C#/media/Fil:First_day_of_Movia_bus_line_5C_on_Bernstorffsgade_07.jpg">Wikipedia</a>.</figcaption></figure><p>Years of research and experiments, longer buses with more doors and more seats, environment-friendly engine; what was not to like? Sadly, the buses reported two major problems: <strong><em>delays</em></strong> and <strong><em>accumulation of two-three buses in succession (a.k.a. bus bunching)</em></strong>.</p><p>These were not new problems to be fair, as 5A was notorious with both of the cases. However, the problems <strong><em>got magnified</em></strong> with the transformation from 5A to 5C.</p><p>The author of this article together with the originator of the analogy, Vadym Volkovynskyi, experienced both of the problems by first hand. They would wait in the bus stop for longer time (compared to before) in the cases of delay, and when the bus showed up, it would often be followed by one or two more 5C buses. In other words, upsetting the passengers (a.k.a. clients) and making them miss the 5A (the previous product), even though it was notorious with the same problems, just not as bad as 5C (the new product).</p><h3><strong><em>CHAPTER 2: Poppendieck family brings the learnings from the lean manufacturing to the software world!</em></strong></h3><p>A year after the 5A line was launched, Mary Poppendieck and Tom Poppendieck decided that the time had come for a new paradigm in the software industry and published their book, “<em>Lean Software Development: An Agile Toolkit”</em>. It was transferring and adapting the learnings from the Lean Production — that was Toyota’s approach to manufacturing — to the software development world. Of course, there is much more to that, and interested reader can find <a href="http://kth.diva-portal.org/smash/get/diva2:1046485/FULLTEXT01.pdf">a faithful account of the history</a> in the recently published doctoral thesis of Liv Gingnell (chapter 4).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/655/1*ST6zAZSIaGVGy-jDEu1r3g.jpeg" /><figcaption>Mary and Tom Poppendieck. Source: <a href="https://planet-lean.com/poppendieck-lean-software-development/">Planet-lean.com</a></figcaption></figure><p>No, Poppendieck’s are not among the signatories of the Agile Manifesto (2001, Utah) but their contribution to the Agile world is undeniable.</p><p>Among other things, Lean Software Development was focusing on reducing waste and improving <strong><em>flow</em></strong>.</p><p>But, what is flow? It is flow of software, value, solutions, and of course BUSes!</p><p>How do we improve the flow? Among other things, we reduce<strong><em> </em></strong>the <strong><em>batch size </em></strong>and reduce the <strong><em>cycle time</em></strong>! Smaller batch size means, faster delivery of the result and faster feedback. Shorter cycle time means, non-value adding waste is eliminated so that the time between client’s request and the delivery of the solution being reduced.</p><p>Having said that, and thanks to Eiler Læssøe Møller, a degree of effort will often be made in order to get wiser and produce a better solution, and exactly what is waste and what is not waste is not always obvious.</p><blockquote>“The fundamental mental shift that lean requires is this: <strong>flow efficiency </strong>trumps <strong>resource efficiency</strong> almost all of the time.” Mary Poppendieck</blockquote><p>At this point we should also mention Donald G. Reinertsen, who is one of the pioneers that studied the flow topic deeper, which was until then basically a topic of discussion that was brought by Lean world but not elaborated. Reinertsen started publishing about “development organizations moving from distinct development phases to continuous flow with overlapping activities” and “introducing queuing theory to product development” in the 90s.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/340/1*2lM-e6Ia_FIfbeQtTF3gZA.jpeg" /><figcaption>Don Reinertsen’s comprehensive book that describes the underlying principles that create flow. Source: <a href="https://www.amazon.com/Principles-Product-Development-Flow-Generation/dp/1935401009">Amazon.com</a></figcaption></figure><h3><strong><em>CHAPTER 3: What does 5C and Poppendieck’s have in common?</em></strong></h3><p>A decent software company would pay attention to improve ways of working and helping their employees, who are all talented and good at what they are doing, in understanding how to optimize globally and delight the customer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lmpvFRTc9CNaD5fJQpw_Rg.jpeg" /><figcaption>Posters from a Flow workshop facilitated by one of our talented colleagues. Source: Iuliia Gumeniuk</figcaption></figure><p>In this quest, and thanks to the guidance from our agile coaches, we have started rolling out workshops (designed by Frank Olsen) where we refrained from teaching/lecturing anything, instead focusing on facilitating a common understanding of flow for our scrum teams. And while thinking of creative examples to demonstrate flow (in this case a <em>flawed</em> flow), my colleague Vadym Volkovynskyi and I found this bus transformation that affected our daily lives as a useful analogy. Let us tell you the story:</p><p><em>With the replacement of 5A buses with 5C, where the buses are longer with more seats, the buses started to get even longer delays in the bus stops. This has multiple root causes, some of them being the slowed maneuvers of the long buses and longer times for entry/exit to the buses.</em></p><p><em>When a bus (B1)gets delayed, the following bus (B2) actually catches up the delayed bus B1 somewhere in the route. That is partly because, as B1 is waiting for collecting all the passengers from a stop, not many passengers are left for B2 to collect so it spends less time in the stops. Often there would be a third bus also catching up (B3) because it will have even fewer passengers to serve.</em></p><p>Remember the batch size? We want it to be smaller, right? How about 5C, it got much bigger. Remember the cycle time? We want it to be shorter, right? And for a passenger to be transported from stop A to stop B, got longer in this case — even if you omit the bus bunching effect, it was due to the limited maneuver abilities of the new long buses.</p><h3><strong>CHAPTER 4: What can we learn from 5C?</strong></h3><p>Here is some of the things that can help your skilled colleagues think about the flow, inspired by the Copenhagen’s busiest bus line:</p><ul><li>The client wouldn’t be happier if you send her a bigger, spacier solution (in this case 3 buses, two of them being almost empty) if the solution arrives late.</li><li>The client wouldn’t appreciate those loads of functionality that you deliver (in this case, more space, more check in options, environment-friendly engine, etc.) if you fail satisfying her main needs.</li><li>It is a good way of losing clients, to release intermittently with a non-constant flow.</li><li>More rapid flow of value, is better even though it doesn’t have all the bells and whistles (5A was a very crowded bus, but got less delayed).</li><li>Resource efficiency is the mindset that needs to be replaced with flow efficiency. In the bus case, having all the fleet on the route does not help if buses are bunching in threes where two out of three are not carrying passengers. In the development case, having all your employees fully utilized and busy with work does not make sense, if the client is not getting constant value in shorter time.</li></ul><p><strong><em>Acknowledgements</em></strong></p><p>Thanks to Vadym Volkovynskyi, the public transformation system in Copenhagen, all the thought leaders from lean and agile community, enthusiastic scrum teams of SimCorp, many great colleagues including but not limited to Frank Olsen, Piet Syhler, Neil Cook, and Iuliia Gumeniuk.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b254896550b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Agile Conference Experience]]></title>
            <link>https://medium.com/@ender.yuksel/my-agile-conference-experience-ad395308774d?source=rss-35edec9320cc------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad395308774d</guid>
            <category><![CDATA[agile-2019]]></category>
            <category><![CDATA[conference-review]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[conference-experience]]></category>
            <category><![CDATA[agile-conference]]></category>
            <dc:creator><![CDATA[Ender Yuksel]]></dc:creator>
            <pubDate>Fri, 16 Aug 2019 21:40:05 GMT</pubDate>
            <atom:updated>2019-08-20T06:02:55.377Z</atom:updated>
            <content:encoded><![CDATA[<h3>My Agile Conference Experience: #agile2019</h3><blockquote>Good news: I attended 20 great sessions!</blockquote><blockquote>Bad news: I missed 280 great sessions!</blockquote><p>In this post, I would like to share my experiences from Agile 2019, the flagship conference in the Agile community — if I may put it like that. Though I have been to academic and industrial conferences for the last two decades, with different types of badges on my chest, this is my first Agile (Alliance) conference, so in a way you will read a first-timer’s impressions. I will try to limit my personal opinions and instead give pointers to further resources in case you are interested in a specific topic.</p><p><strong>Table of Contents</strong></p><p>Section 1:</p><ol><li><a href="#c54f">Things that I never heard before</a></li><li><a href="#9a40">Book suggestions from speakers</a></li><li><a href="#4394">The Sessions I have attended</a></li></ol><p>Section 2:</p><p>4. <a href="#e329">The Conference Anatomy</a></p><p>5. <a href="#2f3a">How I prepared for the conference</a></p><p>6. <a href="#a944">General Impressions</a></p><p><a href="#18fb">Notes and Acknowledgements</a></p><h4>Let’s apply the Pareto Principle into the organization of my story! Here is the 20% of my story that can give you the 80% value:</h4><h3>1. Things that I never heard before</h3><ul><li><strong>Career jungle gym</strong> is a metaphor created by Sheryl Sandberg. As Doc Norton puts it: “On a jungle gym, there are infinite paths. You can ascend as you choose. You can stay at the same level and move side to side, exploring the full 360 perspective from this height. You can move diagonally. You can ascend in a straight line to the top. Run into an obstacle? No problem. Move around it. Someone else on the jungle gym? No worries, there’s room for several of us and we can adjust around each other as we explore.”. Read more <a href="http://docondev.com/blog/2014/02/jungle-gyms-not-ladders">here</a>.</li><li><strong>Deming’s 14 key principles to managers </strong>is a set of management principles to help companies increase their quality and productivity, also credited with launching the Total Quality Management movement. Read more in <a href="https://en.wikipedia.org/wiki/W._Edwards_Deming#Key_principles">Wikipedia</a>.</li><li><strong>Experiential Learning</strong> is the process of learning through experience, and is more specifically defined as “learning through reflection on doing”, as stated in <a href="https://en.wikipedia.org/wiki/Experiential_learning">Wikipedia</a>.</li><li><strong>Flipped classroom </strong>is an instructional strategy and a type of blended learning that reverses the traditional learning environment by delivering instructional content, often online, outside of the classroom. Read more in <a href="https://en.wikipedia.org/wiki/Flipped_classroom">Wikipedia</a>.</li><li><strong>Habitual excellence</strong> is a term coined by Paul O’Neill, you can read <a href="https://www.linkedin.com/pulse/habitual-excellence-paul-oneills-three-questions-joshua-kerievsky/">this article</a> about it by Joshua Kerievsky</li><li><strong>Kent Beck’s Beyond Agile Manifesto</strong>. <a href="https://beyondagilemanifesto.org/">Here</a> is the manifesto, and <a href="https://www.forbes.com/sites/stevedenning/2011/05/04/innovation-applying-inspect-adapt-to-the-agile-manifesto/#20fa581f68b1">there</a> is an article from Steve Denning.</li><li><strong>Nonviolent communication</strong> is a concept that was developed by Marshall Rosenberg, read more in <a href="https://en.wikipedia.org/wiki/Nonviolent_Communication">Wikipedia</a>.</li><li><strong>Satisficing</strong> means going for good enough, coined by joining satisfaction and sufficiency, and helps countering perfectionism.</li><li><strong>StrengthsFinder</strong> is an online personal assessment test that outlines the user’s strengths. You can read a <a href="https://www.goodreads.com/book/show/8123742-strengthsfinder-2-0">book</a> about it and purchase the test from Gallup.</li><li><strong>Three Horizons Model</strong>, a conceptual model to aid people thinking about current assumptions, emerging changes, and possible and desired futures. Here is an <a href="https://hbr.org/2019/02/mckinseys-three-horizons-model-defined-innovation-for-years-heres-why-it-no-longer-applies">HBR article</a> about it.</li><li><strong>Toronto Empathy Questionnaire</strong>, is a brief measure of empathy. You can try it <a href="https://psychology-tools.com/test/toronto-empathy-questionnaire">here</a>.</li><li><strong>Wabi-Sabi</strong> is a(nother) Japanese wisdom, that accepts imperfection.</li></ul><h3>2. Book suggestions from speakers</h3><ul><li><strong>A Simpler Way</strong><br>by Margaret J. Wheatley, Myron Kellner-Rogers (suggested by Al Shalloway)</li><li><strong>Accelerate: Building Strategic Agility for a Faster-Moving World</strong><br>by John P. Kotter (suggested by Dean Leffingwell)</li><li><strong>Badass: Making Users Awesome</strong><br>by Kathy Sierra (suggested by Joshua Kerievsky)</li><li><strong>Crucial Conversations: Tools for Talking When Stakes Are High</strong><br>by Kerry Patterson, Joseph Grenny, Ron McMillan, Al Switzler (suggested by Bob Galen)</li><li><strong>Immunity to Change: How to Overcome It and Unlock Potential in Yourself and Your Organization</strong><br>by Robert Kegan, Lisa Laskow Lahey (suggested by Lucia Baldelli and Cherie Silas)</li><li><strong>Nonviolent Communication: A Language of Life</strong><br>by Marshall B. Rosenberg (suggested by Cheryl Hammond)</li><li><strong>Project to Product: How to Survive and Thrive in the Age of Digital Disruption with the Flow Framework</strong><br>by Mik Kersten (suggested by Dean Leffingwell)</li><li><strong>Project to Product: How Value Stream Networks Will Transform It and Business</strong> <br>by Mik Kersten (suggested by Dean Leffingwell)</li><li><strong>Radical Candor: Be a Kickass Boss Without Losing Your Humanity</strong><br>by Kim Malone Scott (suggested by Bob Galen)</li><li><strong>The Age of Agile: How Smart Companies Are Transforming the Way Work Gets Done</strong><br>by Stephen Denning (suggested by the author himself)</li><li><strong>Thinking, Fast and Slow</strong><br>by Daniel Kahneman (suggested by, <em>many</em> speakers)</li><li><strong>Team of Teams: New Rules of Engagement for a Complex World</strong><br>by Stanley McChrystal (suggested by Jeff Patton and Stephen Denning)</li><li><strong>The Chimp Paradox: The Acclaimed Mind Management Programme to Help You Achieve Success, Confidence and Happiness</strong> <br>by Steve Peters (suggested by Portia Tung)</li><li><strong>The Fearless Organization: Creating Psychological Safety in the Workplace for Learning, Innovation, and Growth</strong><br>by Amy C. Edmondson (suggested by Joshua Kerievsky)</li><li><strong>Visual Intelligence: Sharpen Your Perception, Change Your Life</strong><br>by Amy E. Herman (suggested by Lisa Cooney)</li></ul><h3>3. The Sessions I have attended</h3><p>Below you can find the sessions I have attended, and thus I want to share with you. Note that I use brackets prefixing the titles, and here is how I use them: [session type] [track name] [audience level].</p><h4>[Keynote] <a href="https://agile2019.sched.com/event/OERN/how-to-manage-your-attention-in-a-world-of-distraction-chris-bailey?iframe=no&amp;w=100%&amp;sidebar=yes&amp;bg=no">How to Manage Your Attention in a World of Distraction</a> (Chris Bailey)</h4><p>A wisely selected topic for the beginning of a busy week full of learning, where the speaker talked about attention and interesting concepts such as “biological prime time”, “email sprint”, “novelty bias”. I suggest you google these terms, and in case you are interested you can find much more in his website <a href="https://alifeofproductivity.com/">https://alifeofproductivity.com/</a> and in the books he authored: <a href="https://www.goodreads.com/book/show/36959766-hyperfocus">Hyperfocus</a> and <a href="https://www.goodreads.com/book/show/25733994-the-productivity-project">The Productivity Project</a>. You can watch the keynote in <a href="https://www.agilealliance.org/resources/videos/how-to-manage-your-attention-in-a-world-of-distraction/">this video</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*svv9XQFSRfChcz8Nd9JyTg.jpeg" /></figure><h4>[Workshop] [Leadership] [Learning] <a href="https://agile2019.sched.com/event/OD6s/scientific-method-to-hire-great-scrum-masters-pavel-dabrytski?iframe=no&amp;w=100%&amp;sidebar=yes&amp;bg=no">Scientific Method to Hire Great Scrum Masters</a> (Pavel Dabrytski)</h4><p>This talk was inspired by Daniel Kahneman’s book <a href="https://www.goodreads.com/book/show/11468377-thinking-fast-and-slow">Thinking, Fast and Slow</a>, where the traditional recruitment practices are criticized and a more rational scheme is explained. In this talk, the speaker showed us how he created a similar method for hiring scrum masters and helped us to create our own method, that is defining the criteria and scoring. The idea is, instead of relying on intuition and memory (oh, that was a good candidate), scoring the candidate both before and during the interview on predefined criteria and using those scores instead of intuition. Makes me think that AI can be used to predict an applicant’s future behaviour.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lbmzuhZWzEguE3yETzIM1A.jpeg" /></figure><h4>[Talk] [Enterprise Agile] [Advanced] <a href="https://agile2019.sched.com/event/OD1m/the-road-to-real-business-agility-dean-leffingwell?iframe=no&amp;w=100%&amp;sidebar=yes&amp;bg=no">The Road to Real Business Agility</a> (Dean Leffingwell)</h4><p>As Dean Leffingwell said, everyone has at least an opinion about what Business Agility is, and in this talk he referred to Mik Kersten’s <a href="https://www.goodreads.com/search?q=mik+kersten">book(s)</a> about it. Also mentioned Design thinking as a series of two divergent and conergent problems: “do I understand the problem?” and “how do I solve the problem?”. He stated that we need to have agile people management teams and we have to change the basic hiring paradigm. Talked about value streams, and underlined that it does not come from Agile, but from Lean. He reminded us the difference between technology value stream (<em>building</em> the system) and operational value stream (<em>using</em> the system), and expressed that business agility comes from the operational value stream.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/832/1*IYpUwuvlhnTpXx-W4EyfgA.jpeg" /></figure><h4>[Workshop] [Learning] [Practicing] <a href="https://agile2019.sched.com/event/ODCU/collaboration-in-agile-brain-based-learning-mehmet-baha?iframe=no&amp;w=100%&amp;sidebar=yes&amp;bg=no">Collaboration in Agile: Brain-based Learning</a> (Mehmet Baha)</h4><p>Mehmet Baha talked about experiential learning, and facilitated a fabulous workshop on collaboration and synchronization using small rhythm instruments with all the participants. It was an amazing experience but very hard share the feeling and learnings with written language. You can at least have a look at the slide deck <a href="https://submissions-production.s3.amazonaws.com/attachments/attachments/000/005/871/original/20190805%20Agile%202019%2C%20Mehmet%20Baha.pdf?X-Amz-Algorithm=AWS4-HMAC-SHA256&amp;X-Amz-Credential=AKIAIKK35CR3V3P7N25A%2F20190816%2Fus-east-1%2Fs3%2Faws4_request&amp;X-Amz-Date=20190816T164846Z&amp;X-Amz-Expires=600&amp;X-Amz-SignedHeaders=host&amp;X-Amz-Signature=a5b1095d859a1b40515ce16592c93e3b4f7fa7f1880e46c322b2ca775cfe8b27">here</a>.</p><h4>[Experience Reports] <a href="https://agile2019.sched.com/event/ODCN/how-do-we-know-if-a-scrum-master-is-good-enough-for-our-teams-sarah-baca?iframe=no&amp;w=100%&amp;sidebar=yes&amp;bg=no">How Do We Know if a Scrum Master is “Good Enough” for our Teams?</a> (Sarah Baca)</h4><p>Sarah Baca shared her experience as a scrum master who turned into a people leader for scrum masters. She used “proxy measure” concept from Esther Derby. Hence, instead of assessing a scrum master with measure about the role, she measured the teams of the scrum masters. An interesting point she made was, that the teams hated agile maturity and agile health check assessments. Her experience was asking the scrum master to perform, for example 12 agile principles assessment, without the team until the team gets mature enough to see the value of such assessments.</p><h4>[Talk] [Collaboration Culture &amp; Teams] [Learning] <a href="https://agile2019.sched.com/event/ODAa/diversity-without-disclosure-norms-to-broaden-inclusion-and-intersectionality-cheryl-hammond?iframe=no&amp;w=100%&amp;sidebar=yes&amp;bg=no">Diversity without Disclosure: Norms to Broaden Inclusion and Intersectionality</a> (Cheryl Hammond)</h4><p>Cheryl Hammond, who is at the same time co-chairing the Enterprise Agile track, gave a lot of useful advice and examples on diversity and inclusion. Among others, she provided us with five important techniques: 1) “yes, and” from improv, 2) “user manuals” such that if you communicate with me this way, you will get my best version(I found them a bit similar to the personal mind map concept in Management 3.0), 3) “StrengthsFinder” that helps finding a persons strengths, 4) “Nonviolent communication” trying to find out the real needs that has not been understood, 5) “Clean language questions” neutralizing the ‘assumption’ in the questions. One of the many good advice: “if you are into inclusion, remove ‘culture fut’ from your dictionary”. Another good advice: “as power dynamics can damage these good techniques, start practicing these with your peers first”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nulLbv4NZ2CJbrB2mMu62A.jpeg" /></figure><h4>[Talk] [Learning] [Learning] <a href="https://agile2019.sched.com/event/OD2P/brain-agility-overcoming-cognitive-bias-lisa-cooney?iframe=no&amp;w=100%&amp;sidebar=yes&amp;bg=no">Brain Agility: Overcoming Cognitive Bias</a> (Lisa Cooney)</h4><p>This talk was also based on Kahneman and Tversky’s work, and started videos of some experiments that were reported in the famous book of the Nobel laureate. Lisa Cooney covered topics such as inattentional blindness, confirmation bias, availability heuristic, and more. I was convinced that it would be a good session, when I saw Linda Rising in the audience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nP6bapFWRCdw4JaCYSNa6A.jpeg" /></figure><h4>[Workshop] [Leadership] [Practicing] <a href="https://agile2019.sched.com/event/ODBV/build-your-modern-management-mindset-adapt-how-you-lead-for-agile-success-johanna-rothman?iframe=no&amp;w=100%&amp;sidebar=yes&amp;bg=no">Build Your Modern Management Mindset: Adapt How You Lead for Agile Success</a> (Johanna Rothman)</h4><p>A veteran in the industry, there are many things I noted from Joanna Rothman’s session, such as: “you cannot divorce management and leadership”, “many people experienced that one person destroys the team and manager does not take action” (reminded me <a href="https://hbr.org/2005/06/competent-jerks-lovable-fools-and-the-formation-of-social-networks">an HBR article</a>, blinking Rikke Sick Børgesen Hoffmann), “if you are a perfect blamer, then you should have a job at a competitor”, “10x engineer”, “if you don’t think before you speak, try writing it on a paper before speaking”, “encourage wide-scale growth instead of career ladder”, “if a product owner is worrying about ‘are people in the team going to be busy next sprint‘ that is an example of measuring busy-ness rather than outcomes” which reminded me of Melissa Perri’s book. Then there is one thing she said, that reminded me of a previous session above: “go above the teams to measure, for example number of new customers, customer retention, etc.”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/758/1*JPa2vruXWaAH3owafMtgPg.jpeg" /></figure><h4>[Stalwarts] <a href="https://agile2019.sched.com/event/OCzM/stalwarts-jeff-patton-jeff-patton?iframe=no&amp;w=100%&amp;sidebar=yes&amp;bg=no">Jeff Patton</a></h4><p>This was an interesting session with sharp criticism to agile today. Jeff Patton talked about what he calls “bad agile” or “evil agile”, and suggested that it is time to rename agile and write the <em>new testament</em>. Complained about lack of customer involvement, (pleasing) the product owner/manger role (instead of the customer), process-companies rather than product-companies, etc. As the stalwart session is formed by the questions of the audience, he had a chance to share his opinions about many different subjects including diversity, role of managers, and even Kent Beck’s version of agile manifesto.</p><h4>[Keynote] <a href="https://agile2019.sched.com/event/OERP/ish-the-problem-with-our-pursuit-for-perfection-and-the-life-changing-practice-of-lynne-cazaly?iframe=no&amp;w=100%&amp;sidebar=yes&amp;bg=no">ish: The Problem with our Pursuit for Perfection and the Life-Changing Practice of Good Enough</a> (Lynne Cazaly)</h4><p>In this keynote, Lynne Cazaly told us that perfectionism and high performance are not related. She described three types of perfectionism, where “socially prescribed” (that is perceiving others have unreasonable expectations for you) perfectionism is the most dangerous. You can read more about the subject in her book “ish”, and she even authored a book called “agile-ish”. You can watch the keynote in <a href="https://www.agilealliance.org/resources/videos/ish-the-problem-with-our-pursuit-for-perfection-and-the-life-changing-practice-of-good-enough/">this video</a>.</p><h4>[Workshop] [Leadership] [Practicing] <a href="https://agile2019.sched.com/event/OD6p/crucial-leadership-conversations-a-chance-to-practice-what-you-preach-bob-galen?iframe=no&amp;w=100%&amp;sidebar=yes&amp;bg=no">Crucial Leadership Conversations — A Chance to Practice What You Preach</a> (Bob Galen)</h4><p>Bob Galen has a distinctive style walking around all the tables and trying to keep steady eye contact with all the participants. In this workshop, he facilitated dojo (similar to troika consulting in liberating structures) where we tried crucial conversations with other participants. As he explained nicely, a leaders job is not done after pointing out deficiency; you need to help and mentor. And to get better at that, keep practicing (dojo all the time).</p><h4>[Stalwarts] <a href="https://agile2019.sched.com/event/OCzQ/stalwarts-melissa-perri-melissa-perri?iframe=no&amp;w=100%&amp;sidebar=yes&amp;bg=no">Melissa Perri</a></h4><p>In this no-nonsense session (smaller audience, good questions, detailed and to-the-point answers, frequently changing fishbowlers, even a guest speaker “Trace Wax” when there was a question about design sprints), Melissa Perri emphasized that agile is not enough and one needs to get good product skills. She touched upon the financial industry as an example of a different product mentality where the approach to the products needs to be rethinked. She also gave insight about hiring product managers, such as looking for people who are open to learning (avoiding candidates that think they know everything) and system thinkers. She gave a lot of pointers around the areas of strategy, roles, learning, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/871/1*-bF8td2fi5TdLfaKdLsiGg.jpeg" /><figcaption>I got a signed book from Melissa Perri.</figcaption></figure><h4>[Stalwarts] <a href="https://agile2019.sched.com/event/OCzt/stalwarts-linda-rising-linda-rising?iframe=no&amp;w=100%&amp;sidebar=yes&amp;bg=no">Linda Rising</a></h4><p>Linda Rising was very inspiring and caring, as usual, and this was a full house session with many book-lovers and thoughtful people. She brought copies of different books, and gave them as a gift to everyone that asked questions to her. Daniel Kahneman and psychology took also some part in this session. In fact, the topics were diverse, and she had a lot of experience and stories to share. Of all the stories, her bonobo analogy, which was a keynote in an earlier agile conference, was really amazing, and perhaps you can get a glimpse of it in <a href="https://www.infoq.com/interviews/linda-rising-agile-bonobos/">this interview</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6g44c9jEvuK2vK_Opz2H8Q.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D8Zth3BQUoJdh7-ZEmkF9Q.jpeg" /><figcaption>Linda gave a book to every single person who asked her a question, also signed me a copy of her own book.</figcaption></figure><h4>[Workshop] [Coaching &amp; Mentoring] [Practicing] <a href="https://agile2019.sched.com/event/OD1O/brain-talk-using-clean-and-other-language-patterns-to-enable-deeper-conversations-mike-bowler?iframe=no&amp;w=100%&amp;sidebar=yes&amp;bg=no">Brain Talk: Using “clean” and other language patterns to enable deeper conversations</a> (Mike Bowler)</h4><p>In this workshop, we learned about “clean”, where the intention is not to change/contaminate others’ metaphors — keeping in mind that in average we use 6 metaphors in a minute. Asking clean questions is a useful skill for both leaders and team members.</p><h4>[Stalwarts] <a href="https://agile2019.sched.com/event/OCzZ/stalwarts-joshua-kerievsky-joshua-kerievsky?iframe=no&amp;w=100%&amp;sidebar=yes&amp;bg=no">Joshua Kerievsky</a></h4><p>Among many other things, Joshua Kerievsky told us this: “see if people are interested in learning, and if they are not, try to make them curious or try to be curious and understand what is their reason.”. Of all the speakers I have listened to, he was the only one mentioning/quoting Martin Fowler (<em>change your organisation, or change your organisation</em>), who is my all-time favorite thought-leader. As he had many fans in the audience, he was also asked to explain how he came up with the terms such as “modern agile” and “making people awesome”. And here is a quote from him: “If your PO tells you what to do and you can’t experiment, then you don’t have an experimentation culture.”</p><h4>[Talk] [The Future of Agile Software Development] [Practicing] <a href="https://agile2019.sched.com/event/ODBE/agile-in-its-third-decade-al-shalloway?iframe=no&amp;w=100%&amp;sidebar=yes&amp;bg=no">Agile in its Third Decade</a> (Al Shalloway)</h4><p>Al Shalloway had a lot of wisdom shared in his lecture-style talk, here are some of the quotes I noted:</p><ul><li>Resistance is not to “change”, it is to particular process of change rather than creation.</li><li>Comparing two things is not an experiment, at least scientifically. Validating your predictions <em>is</em> an experiment.</li><li>XP and Scrum is not the same as XP</li></ul><h4>[Workshop] [Coaching &amp; Mentoring] [Advanced] <a href="https://agile2019.sched.com/event/OD1e/uncover-and-overcome-immunity-to-change-lucia-baldelli-cherie-silas?iframe=no&amp;w=100%&amp;sidebar=yes&amp;bg=no">Uncover and overcome immunity to change</a> (Lucia Baldelli, Cherie Silas)</h4><p>The speakers interactively presented the immunity canvas concept, that can be used both by individuals and teams to uncover immunity for change. The purpose is creating awareness, rather than problem solving. Based on the book <a href="https://www.goodreads.com/book/show/5962102-immunity-to-change">Immunity to Change</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bfFi-9WR9ew5RKyHNy-wvw.jpeg" /></figure><h4>[Workshop] [Enterprise Agile] [Advanced] <a href="https://agile2019.sched.com/event/ODB5/mapping-the-enterprise-agile-journey-stephen-denning?iframe=no&amp;w=100%&amp;sidebar=yes&amp;bg=no">Mapping The Enterprise Agile Journey</a> (Stephen Denning)</h4><p>Another full house session, full of good insights from storytelling, to good/bad examples. From three laws of Denning (law of customer, law of small teams, and law of network) to a good account of agile history. Based on the speaker’s most recent book, <a href="https://www.goodreads.com/book/show/34963438-the-age-of-agile?from_search=true">Age of Agile</a>. Last part of this session was facilitated by a guest speaker, where she made us watch a video with the same title as the book, (I could not find the video on the Internet) and the video featured the Royal Danish Ballet as well as a very nice former colleague of ours from SimCorp, Rósa Björk Einarsdóttir.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uZuuNzds41RTdmH2yl3nOw.jpeg" /></figure><h4>[Workshop] [Agile Midway] [Learning] <a href="https://agile2019.sched.com/event/OEPc/soyou-want-to-submit-to-be-a-speaker-chris-murman?iframe=no&amp;w=100%&amp;sidebar=yes&amp;bg=no">So…You Want To Submit To Be A Speaker</a> (Chris Murman)</h4><p>This was an interesting session by one of the track chairs, giving good insights and advice to potential speakers. And the bonus was, Johanna Rothman was also in the room and she also gave many tips. One good point is the 3-whys: why you. why here, why now? Another one was the use of <a href="https://en.wikipedia.org/wiki/Bloom%27s_taxonomy">Bloom’s Taxonomy</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z5MlZCivjKuY1swIya976w.jpeg" /></figure><h4>[Keynote] <a href="https://agile2019.sched.com/event/OERS/playful-leadership-how-to-enable-transformational-change-and-have-fun-doing-it-portia-tung?iframe=no&amp;w=100%&amp;sidebar=yes&amp;bg=no">Playful Leadership — How to enable transformational change and have fun doing it</a> (Portia Tung)</h4><p>This was the closing keynote, and the speaker already impressed us by walking around and greeting the audience one by one. Then she impressed by using images on her slide backgrounds that she have taken during the conference — including her title slide. The keynote was about <em>play</em>, and how to be a playful leader. This included answers to questions like why should adults play, what is the opposite of play, and what are models for change process. She shared a good deal of personal experience, and it was very inspiring and encouraging. You can watch the keynote in <a href="https://www.agilealliance.org/resources/videos/playful-leadership-how-to-enable-transformational-change-and-have-fun-doing-it/">this video</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lg8bz-w14JpJrTnVc96nbg.jpeg" /></figure><h4>Here is the rest of the story that can tell you more about the dynamics of the conference and how I prepared for it.</h4><h3>4. The Conference Anatomy</h3><p>The conference had 24 different tracks, below is a list I compiled (from <a href="https://www.agilealliance.org/agile2019/">https://www.agilealliance.org/agile2019</a>) including number of sessions each track had, written between parentheses.</p><ol><li>Agile Companies (14)</li><li>Agile Foundations (7)</li><li>Agile in Government (10)</li><li>Agile Midway (6)</li><li>Audacious Salon (12)</li><li>Coaching &amp; Mentoring (19)</li><li>Coaching Technical Skills For Less Technical Coaches (12)</li><li>Collaboration Culture &amp; Teams (21)</li><li>Customers &amp; Products (15)</li><li>Data &amp; Metrics (7)</li><li>Dev Practices and Craft (15)</li><li>DevOps (10)</li><li>Enterprise Agile (16)</li><li>Experience Reports (24)</li><li>Keynotes (3)</li><li>Leadership (18)</li><li>Learning (17)</li><li>Lightning Talks (3)</li><li>Project Program &amp; Portfolio Management (16)</li><li>Self-Care (12)</li><li>Stalwarts (9)</li><li>Testing &amp; Quality (11)</li><li>The Future of Agile Software Development (9)</li><li>User Experience (10)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/529/1*RjuMzB6wdVEsiU506LxPFg.jpeg" /></figure><h4>Notes:</h4><ul><li><strong>Keynotes</strong> had the same duration as regular sessions, except that there weren’t any parallel (or competing) sessions with keynotes.</li><li><strong>Lightning Talks </strong>sessions used regular time slots, yet each Lightning Talk session had many short talks ranging between 3 to 7 minutes.</li><li><strong>Agile in Government</strong>, <strong>Coaching Technical Skills For Less Technical Coaches</strong>, and <strong>Self-Care</strong> tracks were the three new tracks in the conference.</li><li><strong>Stalwarts</strong> is a special track that used the fishbowl format, where audience members can get on the stage and start a conversation with a well-known speaker. Speaker is always on the stage, and the courageous individuals that ask questions are changing. Often there are seats for 2–3 individuals next to the (celebrity) speaker.</li><li><strong>The Future of Agile Software Development </strong>is the academic track, and its proceedings are published in IEEE Software.</li></ul><blockquote>Here comes an opinion: my favorite track is definitely the Stalwarts; talking to thought-leaders that I follow and read their books, is sufficient to justify spending hours in transportation. I am also a big fan of the Enterprise Agile track, though I served as a track reviewer and hence cannot be objective in this case.</blockquote><figure><img alt="Thanks for honoring the reviewers, using the large screens!" src="https://cdn-images-1.medium.com/max/1024/1*KdikgGOfrWQnzsFBA83zkQ.jpeg" /><figcaption>Thanks for honoring the reviewers, using the large screens!</figcaption></figure><h3>5. How I prepared for the conference</h3><p>Below is a part of my preparation, not readable (intentionally) but I can explain. It consists of 15 tables, each of them representing a time slot (excluding the keynote time slots, where there is no alternative). In each time slot there are <em>at least</em> <strong>19</strong> different sessions. So basically, I noted my priority order in these tables for every time slot. In some tables, I have #1, #2, meaning that if I cannot find a seat in my #1, than I will stroll to my second priority session. All in all, I marked 52 sessions that I wanted to see, but I knew that I could only see 15 of them (in total I attended 20 sessions)!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kEz3DddXp75Gm5XUibWhng.jpeg" /><figcaption>Helicopter view into my handmade priority-ordered schedule, in order to share sessions with my colleagues, where each table is a time slot, and color coding indicates different tracks.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5eq4OlHgLQTRnHmdoOmARA.jpeg" /><figcaption>A random time slot (zooming into the picture above), where there are 20 sessions (plus a lab) that one can choose to attend. No offense with my priority order, and in reality I ended up in my third preference. Distorting Eisenhower’s battle quote: all plans are wrong, but planning (and preparation) is crucial.</figcaption></figure><p>At this point, I need to tell you the law of two feet. That is, if you don’t see the value in a session you attended, you just use your feet to navigate to another sessions. No wasted time, and no hard feelings. I had a few cases that I used the law, and enjoyed the remaining part of a better (that is, better matching my needs and wants and expectations) session.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lMcHDGaVAw4MqRgqMqhBQg.jpeg" /><figcaption>My Agile 2019 session stats.</figcaption></figure><p>I need to mention that I decided to take my time on preparation, including searching for previous talks (preferably video recordings) of some of the speakers on top of reading their abstracts. The learning objectives appended to the abstracts are also good in setting the expectations from a participant point of view.</p><h3>6. General Impressions</h3><p>Words cannot describe how big of an opportunity to learn, share, and network. Besides, having the chance to talk to people you follow. I met people whose books I read and whose podcasts I listened to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pagD_6iL7Qd4KwdHIDGSDA.jpeg" /><figcaption>Together with speakers, track chairs and reviewers of the Enterprise Agile track. From left to right: Aruna Chandrasekharan, Nienke Alma, Ryan Ripley, Cheryl M Hammond, Alex Kanaan, Ender Yüksel, Al Shalloway, Archana Joshi</figcaption></figure><p>Due to my role and interests, I created my schedule heavily on leadership, learning, recruitment, and enterprise. I figured out that a good number of the sessions I attended were either referring to or inspired by, or even heavily based on the work of Daniel Kahneman (and Amos Tversky) that is recorded in the book <a href="https://www.goodreads.com/book/show/11468377-thinking-fast-and-slow">Thinking, Fast and Slow</a> — aka the bible of cognitive bias. Some speakers even assumed that the audience knew about System 1 and System 2. I felt very lucky to have read the book before, and amazed that it inspired so many people. Here is a formula that I came up with:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wOrZPKMDERUO5K_SBKHg6w.jpeg" /></figure><p>Workshop/Talk distinction is quite useful, as the workshops are interactive and usually audience make exercises or at least discuss things with fellow participants.</p><p>There were also some unexpected benefits for me. By chance I met a few people, that work in companies that are getting products from the company I work for, namely our clients. Even though I don’t have a product-related role, I was happy to hear feedback.</p><p>You might think otherwise, but I frankly think that attending some sessions with my very own manager was a great thing. Learning new concepts together and aligning on topics and approaches was yet another unexpected benefit for me.</p><p>This conference can be enjoyed best with a good physical and mental condition. A full week of sessions is not easy to take in and digest. Notes to myself: bring a huge water bottle, use a digital keyboard (I wanted to take notes on computer, but didn’t do in order not to disturb others with my keystroke noise), remember to take walks outside in the breaks, make room for meditation, etc.</p><p>As I said in the beginning, this was the biggest conference I have attended. But at the same time, the conference resulted into a big volume of social media feed. If you search for #agile2019 hashtag in Twitter, LinkedIn, and Instagram you will see what I mean.</p><p>Thanks for your persistence and focus, as you are still reading. Below, are my additional notes about the conference, and my acknowledgements.</p><h3>Notes and Acknowledgements</h3><ul><li>Cindy Cruz has fantastic videos that makes a great summary of the first two days: <a href="https://www.linkedin.com/posts/cindyscruz_agile2019-activity-6564915916725895168-JBU1">one </a>and <a href="https://www.linkedin.com/posts/cindyscruz_agile2019-activity-6564597990630182912-I-j4">two</a>.</li><li>You can follow Erin Perry’s sketches, here are some of the sessions that I have missed <a href="https://www.linkedin.com/posts/erinmperry_agile-bosssa-nova-activity-6564193950582784000-atWw">Beyond Agile: Thriving on Digitalization with Beyond Budgeting, Open Space &amp; Sociocracy (Jutta Eckstein, John Buck)</a> and <a href="https://www.linkedin.com/posts/erinmperry_mindful-writing-activity-6564254908076310528-dfKW">Mindful Writing for your Self-Care Tool Kit (Toby Sinclair)</a></li><li>More sketches can be found on the Twitter feed of the <a href="https://twitter.com/sketchingsm">Sketching Scrum Master</a></li><li>And among others, I recommend having a look at <a href="https://twitter.com/chaos_olga">Olga Yiannakis</a>’ twitter feed if you don’t want to miss any moment (of the sessions she attended)</li><li>Prior to the conference there were Women in Agile and an Agile Coach Camp that I have missed. I heard good things about both, and people did have their own combo events combining them with the Agile Conference</li><li>You know that you are talking to a veteran when you hear somebody mentioning total quality management (TQM).</li><li>A speaker used the phrase Apple Danish, and sitting at a table of participants living in Denmark we looked at each other, as we didn’t know what she meant.</li><li>Thanks to many people that made the exhibition interesting, for example this gentleman who was as creative as bringing and playing his uke. By the way, the last keynote speaker also mentioned ukulele in her keynote so it could be <em>the</em> instrument of agilists.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-bIajnV8RqAxKujsGu84Vw.jpeg" /></figure><ul><li>Thanks for the copies of Agile Manifesto in many different languages including my mother-tongue:</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1021/1*5DjpAw7au2J-g0S8b_Vibg.jpeg" /></figure><ul><li>Thanks to the SimCorp team (including SimCorp alumni) and thanks to SimCorp leaders for valuing the learning and growth of their employees:</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1019/1*3x8FnVwWFN4mFS6OmOUP-g.jpeg" /></figure><ul><li>More thanks to more SimCorper’s for the best book that I could have read on the flight:</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FUZfm98QtPlnEE-K" /></figure><ul><li>Thanks to Scrum Alliance for sponsoring the notebook that I almost completed by taking notes during the conference.</li><li>Thanks to the premises of Dulles and Munich airports, where I have written this post.</li><li>Finally, thank you dear reader, for taking time to read this post.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad395308774d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>