Two weeks ago I went to the Test Leadership Congress conference<\/a> in NYC, absolutely loved the content and speakers. It was at a very opportune time while we were working on IT transformation and myself looking after the processes and quality expectations in our new ways of working.<\/p>\n With the prevalent wisdom of fully automating \u2018testing\u2019 and less need for test leadership, the conference was loaded with evidence on the contrary. In the post-agile apocalypse, the system level thinking and the pivotal role of testers to question what and why we are building what is user story says and the current build demonstrates, is all getting lost in the mushroom cloud of buzz words and time to market.<\/p>\n There were a lot of amazing sessions<\/a> including psychological techniques to figure out your own and your organizational values, using Improv to make a point and learn look at things from a holistic perspective, playing games designed to improve thinking and test design and a board game to understand the important aspects in continuous delivery. Most of the sessions were so great, it was hard to pick which one to go to.<\/p>\n The organizers especially Anna<\/a> and Andrea<\/a> did a great job in choosing the speakers to have a great mix and schedule the activities. Typically you would see topics around specific tools or technologies, this one was more about developing leadership which I feel is need of the hour.<\/p>\n It\u2019s going to take me a while to digest and share my thoughts around the sessions. On top of my head here were the few learnings that really stuck with me:<\/p>\n Dr John P. Thomas\u2019s keynote on systems approach to software testing was very refreshing. Having a similar background of working with safety critical systems, I have always felt the absence of certain things in the agile world like spending time in understanding and questioning the requirements, mapping the entire system and looking at how the control flow works. STPA was a process introduced to us by John which felt like a systematic process to codify how that system thinking is supposed to be done. Will share more in a separate post.<\/p>\n<\/div><\/span> Ive always struggled with finding out values of other people to act according to their and the organization’s commonly held values. I always try to do ‘only’ the right thing which now I feel might not always be the best way. In most cases should try to be resonant of the organizational values and try to start operating from there instead.<\/p>\n The protreptic dialog explanation and demonstration in which Ole <\/a>and Anders <\/a>did a great workshop which showed a way to understand other people\u2019s perspectives and learn more about their values.<\/p>\n In the dialog, you ask the other person to describe an event and have follow up questions while being genuinely curious to understand what it means for them. Try to understand:<\/p>\n Ole S Rasmussen<\/a> talk on Personal leadership was great and this stood out for me out the whole workshop. He explained what being robust and flexible meant and how to become a ‘flexible robust’ leader.<\/p>\n The technique to do a self assessment and find out what your personal values are and your own limits. In a short exercise we identified what does fragility mean for us and what corner is most significant for us in the philosophical triangle (shown below). It was a good demonstration to see how to journey inwards and understand your own self.<\/p>\n<\/div><\/span> As a leader, understanding your own self is very helpful, gives an idea of your own limitations, strengths and weaknesses. For me the exercise revealed Fragility for me meant fearful, and from the triangle ‘attention to what matters most’ was most important. stitching them together we figured I may be fearful of not focusing on the right thing and waste my energy and my team’s on doing what does not matter the most.<\/p>\n<\/div><\/span> Tanya’s<\/a> session on continuous delivery was nice in which she explained the guiding principles for DevOps – CALMR. Working on SAFe framework I had been exposed to these principles, but what was new was the second half of the talk, a continuous delivery board game!<\/p>\n Looked like monopoly of DevOps. I’ve always been very passionate about having dry runs of complex problems to do some up-front thinking instead of just trying a whole bunch of failures and then finding what works. The board game instilled the importance of certain aspects in coding CI\/CD which are otherwise hard to comprehend without practical experience.<\/p>\n For instance, how it’s important for features to be in production instead of having a whole heap of them at different stages in the pipeline, unless it’s out there, you cannot make money!<\/p>\n<\/div><\/span> There were many other sessions which were great, I’ll add more details on them in separate posts. I learned not only in the sessions, but outside the workshops and presentations networking with others was a great opportunity to learn. Talking\u00a0with leaders in other organizations and practitioners there was so much more we learned from each other.<\/p>\n The biggest take away from these talks was: “EVERYONE IS STRUGGLING WITH CONTINUOUS TESTING”. One would assume the big names and thought leaders in our industry would have everything figured out, but we are all struggling, some are quite close, others might be far behind, but it seems no one has it nailed down with all their products working in a complete DevOps culture across the enterprise<\/p>\n That means,<\/p>\n those of us looking for greener grass on the other side, try to cultivate some green grass where you are, no one has the magic formula to continuous testing.<\/p>\n<\/blockquote>\n The games and round table session was amazing. We all had a blast designing test strategy for products of our choosing and then demonstrating them.<\/p>\n<\/div><\/span> There was a separate games time in which Eddie <\/a>and Jordan<\/a> organized a lot of different games. I got pulled into playing story cubes, we all enjoyed it very much, it was so hilarious the kind of stories we came up with.<\/p>\n<\/div><\/span> End of last day we had an after party, lots of great conversations and new friends. Had a wonderful time.<\/p>\n<\/div><\/span> A fellow tester and I tried to meet during my last time visit to the US. This time he was determined and I’m glad we did it. He had to travel such a long distance in one day, just to learn and improve his skill set. I shred the details of the story in this post<\/u><\/em><\/strong><\/a>.<\/p>\n Met a lot of people I had been interacting with in the testing community on social media, Ajay <\/a>being one of them. While traveling back from the conference Ajay<\/a> and I happened to be on the same flight. While waiting at JFK we recorded<\/em> a short video <\/u><\/em><\/strong><\/a>about how the conference went and what we liked about it.<\/p>\n<\/div><\/span> Accompanying me on this trip was Head to QA at Emirates, to whom I had suggested the conference. She loved the setup too and while going back we recorded our thoughts, what we learned and some key take aways, you can watch in this video<\/em><\/strong><\/a>.<\/p>\n<\/div><\/span> And enjoying the comfy Emirates A380 business class \ud83d\ude42<\/p>\n<\/div><\/span>Overview<\/h3>\n
Key learnings<\/h2>\n
System Theoretic Process Analysis – STPA.<\/h3>\n
The Protreptic dialog.<\/h3>\n
\n
If You Really Want to Make a Difference, Be the Flexibly Robust Leader<\/h3>\n
The game of continuous delivery<\/h3>\n
‘No one’ has it all figured out<\/h3>\n
\n
Fun with a Capital F<\/h2>\n
The most inspiring event<\/h2>\n
Travel back<\/h2>\n