In this presentation I will address questions like
Storytelling is one of the oldest communication methods. Through stories, we transmit experience, culture, morals and lessons. We are not always aware of it, but we are constantly telling each other stories and playing the starring role in our own story. As humans, we are pre-programmed to react positively to stories, which makes them powerful and effective ways to transfer our visions, strategies or ideas. Their power reaches through our work as an agile professional and our projects, but also through our own organization and life outside of work. In this talk, Huib will share stories. We’ll look at how stories are designed, how they help people and how to take them apart to understand them better. Storytelling is also inherently communicative – we’ll look at how storytelling isn’t just about the person telling, but also about the people listening.
Hi, I’m Huib Schoots, nice to meet you. My personal mission is shaping better people and software quality by connecting, innovating, facilitating, coaching, enabling and teaching. I’m fascinated by mindset, thinking, behaviour and collaboration. I’m active in many communities. Some keywords about me: humanist, open, direct, creative, idea generator, result driven, humor, problem solver, curious, confronting, critical thinker, passionate and energetic, lifelong learner, entrepreneurial, analytic and continuous (world) improver. I like hanging out with friends, play trombone in a brass band, board & computer game, LEGO, photography, running, beer brewing, magic tricks, travelling and reading. I work as an operational director & quality coach at qualityaccelerators.nl and an agile test expert, trainer and consultant at deagiletesters.nl
Anna Gamalielsson has been working with test for 17 years, previously building up the Test Center at IKEA. Listen to her story about how she is now building up a Test Center from scratch at Region Skåne! How is testing different within the public sector compared to the private? What challenges lies ahead now that we are expanding digitalization withing health care in Skåne? Also, listen to her describe how they have implemented agile methods for building, developing and maturing the Test Center itself!
About the speaker
With a Bachelor of Science in Multimedia Engineering, Anna has spent the last 17 years working in different roles connected to test. With experience from Ericsson, IKEA and Region Skåne, she has developed a passion for both test and leadership. She now works as a Unit Manager at Region Skåne for their Test Competence Center. An opportunity she could not afford to miss out on!In 2019 she started her own company (https://vattnadardetgror.com/) where she works as a coach, mentor and leadership developer. She now has this as a side business along side with her job at Region Skåne.
Teams deploy new application versions more frequent than ever; some teams even deploy several times per day. How do we ensure the quality of each deploy is good? How can we build confidence that we don’t introduce any problems or changed behaviors? In this session we talk about how we use our CI/CD pipeline as our first and last line of defense. How we can use it to run different test, work with temporary environments, deployment techniques and smoke testing. We will look deeper into some CI/CD tools and certain public cloud providers for cloud-based applications.
Jimmy is a Cloud Architect and Developer specialising in AWS Cloud. With a broad interest in serverless and IoT. Highly passionate about Automation, DevOps, GitOps, ChatOps, and all new ways of working. Experience from large organisations such Sony, Infor, IKEA, and AssaAbloy.He loves to share his knowledge and experience. Holds several AWS and is always aiming for the next one. He is total into coffee and BBQ. Building his own connected BBQ thermometer using Rasperry PI and AWS.
Session type: Panel
There are a myriad of different types of pure testing topics and an almost infinite array of IT subjects to help us testers understand our place and context in the digital now. One look at LinkedIn or Udemy and you will be bombarded with articles, classes and certifications “for your next step” in the testing world. It's too much for one human to learn over a lifetime! So, what should we be focusing on with our precious time? What technical skills should we be adding to our toolbox, what do our developers expect from us, and what secures that coveted and rare spot in the forefront of the hiring process? And once we have figured out all the things we should be learning, what is the best method to learn them and just how does one keep motivated to continue learning throughout an entire career? These questions and many more will be answered by our eminent panellists, all bringing unique experiences and perspectives on the topic; Test coach Huib Schoots, test manager Anna Gamalielsson, developer Jimmy Dahlqvist and test consultancy CEO Håkan Ramberg moderated by test lead and specialist Sasan Fallahi. Join us in this important discussion and enter the fall with a new sense of direction!
Session type: Workshop
How we develop software has changed for most of us over the last twenty years. We often find ourselves in a fast-paced environment working with volatile and very complex distributed systems. Failure is inevitable, you just don’t know when and where it will happen. Despite all the testing you have done and all the environments you have tested in you have probably experienced loads of problems in production, some more critical than others. There seems to be a belief that we can prevent failures from happening by predicting how the system might fail. To some extent we can, but there will always be events occurring which we could never predict. We might tell ourselves that we could have predicted the event if only we had done “this or that”, but that’s just the hindsight bias affecting you. What we need to do is embrace the idea of failure as something inevitable.
We must add or even replace some of the activities we do today to create an environment that enables us to quickly find the problems. This is where feedback and observability are very important aspects. A slow or non-existing feedback loop limits the creativity and the ability to explore the system, which is needed in order to discover the unknown unknowns. The ability to see and understand what happens in our system is the kind of feedback we need, to quickly detect important problems or opportunities no matter whether the system runs in production or is under development.
This workshop focuses on why feedback and observability throughout development is valuable to not only testers but everyone involved in software development. *Warning - it might require a shift in perspective and mindset. It is also a workshop that is highly interactive.
Maria is a generalist with a deep knowledge in software testing and agile development. She has been working in software development for over twenty years in many different roles and industries. Since 2018 she has her own company Black Koi Consulting. What she appreciates the most in each and every assignment she’s had is the learning opportunities. Maria loves sharing her experiences and helping others to improve. She has spoken and organized workshops at many national and international conferences. Occasionally she shares her thoughts on mkedemo.wordpress.com
The journey towards automation: Pitfalls and possibilities for teams and testers. We talk to them every day: Organisations and businesses on the verge of committing to automation. Behind them are countless hours, considerations, and discussions leading up to the decision to automate. Coincidentally, it’s not just one single decision – but several. The problem is, most decision-makers aren’t aware of this. Very often, the focus is on the tool rather than the method. As a consequence, automation gets off to a rough start. In my role as Chief Evangelist, I have seen many of these situations, talking to leading IT organisations all over the world. I want to share our lessons learned from these experiences with our target users – the skilled, functional testers. As I see it, automation has to be based on an understanding of the business processes; an insight deeply founded in any experienced tester. In this presentation, I will touch on some of the missed, but critical, considerations when embarking upon automation. Some are relevant for the test managers – some for the testers. All of them are crucial for a successful automation journey. And I promise: Not one single word about any automation tool.
The most important topics are:
- The value and contribution of a tester: Beyond executing the test script.- What are the key enablers for long-term sustainable automation? (Hint: It’s not the tool)- Automation: NOT business as usual (Hint: Not because of the tool)- Where does the automation effort begin (Hint: Not with the tool)
The purpose of this presentation is to empower, engage and educate the functional tester towards the automation journey. Because automation is mistakenly perceived as an agenda specifically for the engineers. Hint: It is not.
For more than 20 years I have been passionate about bringing business, people and technology closer together. Overall the story has been business process development and optimisation. Within this, it has been a story of facilitating business processes and rulesets that would let themselves translate into IT – and further into usable and understandable solutions for users, internal as well as external. After having built *a lot* of business systems over the years, the next logical step was to make users lives even easier – by eliminating quality issues and bad code through automated test. But – firmly in the hands of the business savvy functional tester – after all; it is more important to know what to automate to obtain the best quality; rather than how.
Who should take the end-2-end responsibility? Why is our integrated test environment down all the time? Why can’t we just get nice test data when we need it? These are the three usual suspects in many large development organizations of today. But what happens inside a development organization when we twist the mindset of development towards seeing it as medical surgery performed on the digital twin of our own business? A digital twin that is in fact just as complex as our digital reality really is? How can we implement digital sensors to monitor our ‘patient’, gather indicators and understand the power of simulations to mathematically calculate confidence in our treatments?
Listen in on my experience on how I started to guide a really cool fintech development organization into a modern way of using systems thinking and what we all could benefit from accepting the fact that our digital surroundings are far too complex for us to comprehend or even imagine. And then, when we understand this, how to start acting according to this in a professional manner.
Fredrik Scheja works as a QA/Test advisor at Sogeti. He is described by others as incredibly positive, creative and humble with a very deep knowledge of testing and agile ways of working. Fredrik likes to pick up pieces of different practices to create new ways of thinking. Some say that he once was invited to hold a speech on test automation for a Swedish government agency but avoided talking about test automation the entire session. And - seems to have gotten away with it. He aims to turn complex matters into something tangible through his storytelling ability. His is on a mission to enable humans to constantly make better and more intelligent decisions throughout the entire spectra of software development.
As human beings we have different styles of communication and ways of handling conflicts. Meeting through the screen is today the default mode, but as human beings we are since thousands of years wired to meet in person. How does meeting online affect the quality of our meetings and work-related relationships in long term? And what are the skills we need as employees in the future to really succeed in a digital workplace?
In this interactive session we’re going to take a closer look at:
- Digital non-verbal language and the importance of emojis- Conflict management in a digital context- Engaging the audience when facilitating video meetings
Henrik Ladström, Digital HR & People Facilitator at Knowit Insight, is an experienced educator and facilitator focusing on digital employee interactions.
When I started my career, I was a learner and now after 8 years in the industry, I will say I am an experienced learner. Learning is a continuous process and that is how it should be. I started my career as a manual tester and that followed automation testing as well. But my interest to try something different than what I was doing led me to explore the Performance testing field. I started exploring this field three years back and during this learning phase, I explored many options and got captivated with the JMeter tool. The most important reason being it is free as compared to other leading performance testing tool. But being an open-source tool, it is not limited in any capability and that is what my session will unfold. I will cover my learning experience of JMeter tool and how I implement my learned skill into an actual assignment.
1. The basic concepts around the Performance testing2. JMeter tool basic and advance features.3. JMeter usage as a performance testing tool for an ecommerce application.
It is for those for whom Performance testing field is completely new but want to explore it. I will be precise about JMeter tool and its usage as a Performance testing tool.
My name is Bharti Ahuja, I work as a Test specialist at Knowit Quality. I have around 8 years of testing experience and worked with a different client under the e-commerce domain. I am positive person who believes learning is a continuous process and I always thrive to be best with what I do. I am mom to a toddler who is a fussy eater and that has inspired me to explore the other side of me as experimenting with different food combinations and to make it more nutritious. I love being organized. I belong to India and living here in Malmo is fun of course excluding the dark winter days.
The frequency of deliveries seems to be ever increasing in our line of work. Our ability to deliver value faster without jeopardizing quality becomes imperative, and building a reliable deployment pipeline, with the right kind of test coverage, is essential for achieving this. Yet, in our hectic day-to-day work there is always a risk of neglecting the basics, such as good smoke test coverage, in favour of chasing whatever new functionality the clients need to be done right now. You may tell yourself you’ll get around to dealing with the technical debt of your test suite, only to realize that as the project rolls along it becomes increasingly difficult to catch up with all the things you “should have done.”
This is a personal story, from a tester’s perspective, of how my team and I worked to reel ourselves in. It is meant to serve as a useful reminder to experienced testers, an encouragement to testers who are new to their profession, and hopefully an inspiration to all. Why smoke testing is important and useful - especially in CI/CD lifecycles - and why it is important to implement it early. It is my hope that you will leave this talk thinking about in what ways smoke tests can bring value to your own team or project. What challenges are you facing that smoke testing might be part of the answer to? This talk will give some insight into how we have worked on this in my current project; what we have done, why we did it, and what our “lessons learned” have been.
I have been working as a tester for seven years now. Coming from a seemingly unrelated background in the arts and humanities, I have come to love this profession and discipline. I try to balance the technical with a sincere interest in the fluffy things, like people and culture, both in the work we do and the workplace. Nothing is better than learning and growing together! I work as a test consultant for Knowit Quality in Oslo, where I live with my fiancée and our glorious cat.
Do you feel safe knowing that dystopian fantasies about our social media-controlled surveilled society where capitalistic sociopaths are exploiting our easily manipulated brains never could become reality? Or do you already fear that we are on a highway to technology hell? Either way, the reality of today is that technology has entered almost all areas of our lives, if not all, and if we do not start incorporating an ethical mindset in our software development we might very well plant the seed of a future we do not wish for. Let’s make a difference and let me show you my keys in accomplishing this. In this talk you will learn how to start looking at technology from an ethical perspective and understand why this is important. I'll share some tips & tricks on how to succeed in making a change. Because even without extrapolating towards an Orwellian future, I think a world where our daily life is increasingly controlled and monitored by software & hardware, we who build that technology need to start to consider how that technology affects others. Almost everyone in the world comes into contact with software in one form or another on a daily basis, but far from everyone understands how it works, or sometimes that it is even there at all.This means that we have a responsibility towards the user and in fact society at large. This holds true for everyone who works within software development and it needs to permeate the entire organization. But what does it mean to take this responsibility? How do we change ourselves and succeed in convincing the stakeholders that ethical consideration is important?I want to share my view of why it is important to ask the relevant ethical questions and to inspire you to act when something doesn't feel right. I will include how to deal with the doubt if one person really can make a change. The future's not set. There's no fate but what we make for ourselves.
My name is Carin Cedergren, I am often happy, sometimes angry and preferably at the same time. I am a positive person who thrives on irritation, I hate doing things the same way just because it has always been like that. What happens when we dare to make that change? How can that improve us as a company, a team and as individuals? That’s what I want to find out! I have more than 10 years of experience in software testing and I love what I do, and I love getting better at it. I almost never wear anything other than black since lighter colours seem to hurt my soul. I also love kittens.
More sessions will soon be announced!
More about Testit