Twitter

 Last time I checked Twitter, it made me feel like an old man, sitting on a bench, close to another old one, who happened to still be on the bench close to me.

Not that we were close friends, not that we did great things together...

We both had better times in the past, we both did great things...

But at the end, Twitter is just a social network. They would show me ads, promoted tweets, and sometimes I would find an interesting thread that would bring me elsewhere.

Yes, I been there for 11 years, yes that seems a long time, yes I made wonderful connections with people, but I've seen people I liked leave the network, and I've seen a lot of things I didn't really like happening there, so the good old times seem both good and old these days.

And as I write this short post, loggin in to twitter to complain about how the old days were does not make sense either.

One day I will be an old man, but there is no hurry, I don't need to go to the bench.

Zen and the Art of Motorcycle Maintenance

 I used to read books about software testing.

And when I moved to Product Management, I started reading books about Product Management.

But last year, when the whole world changed upside down because Covid-19 and I got fired, I was unable to read anything work related.

The only thing I could read was Terry Prachett's Discwork books.

I started reading them for my kids as bedtime stories, and as they grew up and didn't want bedtime stories anymore, I continued reading them for myself. I found very pleasant to read about Discworld, it would allow me to catch sleep in very difficult times, and I got over the first 20 books in one year.

Sam Vimes it has been a pleasure meeting you, but I really feel like going back to reading about software testing, and quality, whatever that is.

This is the second time I read this book. The first time must have been around 2009, when we started writing blogs and learning about testing and quality. It's fun to observe how different the book feels when you read it for the second time, 13 years after, since the book has not changed, it must have been me!

The book is an autobiographical story about a bike trip that Robert M. Pirsing went to across United States in 1968 with his 11 Year old son riding a small Honda.

I like riding motorcycles, and last month we went for a 3 day trip with my wife and out 13 year old kid.

What might have changed in 50 years of motorcycle road trips according to this book ...

Pirsing did his trip in a Honda CB 450, a medium sized bike that would do 180 kmh with his 43hp twin engine.

We did our trip in a couple of Honda CMX 500, a low seat cruiser that has a 47 hp twin engine, and whose top speed I'm not aware of, since I never bothered to test.
On paper, you would say both motorcycles look very similar.

They are not.

Pirsing depicts how he would service the bike, change oil, adjust carburation, tighten valves, weld a loose chain guard and perform several other maintenance tasks.
I did none of that. These newer bikes require a service every 12.000 km, this means I could ride from Valencia (Spain) to Moscow, ride back home, and then do the whole trip again before needing a new oil change. Motorcycles have gone a long way when it comes to maintenance.

Now we have fuel injection, so we don't need to adjust the carburator needles when reaching higher grounds, we have ABS so we don't worry about riding in wet weather, we have bluetooth comms so we communicate from rider to rider the whole trip.

Of corse you need to take care about things when you are riding. You still need to get fuel, food and rest when tired, those things remain the same.
Your intercom devices need recharge and they don´t like getting wet, your mobile phone can run out of signal or battery, so you better know where you want to be riding, just in case your Google maps is not able to tell you where you are.

To became one with the landscape, to be part of it, to get cold when crossing long tunnels and high peaks, to get burnt by the sun and to become amazed, when a road suddenly opens to a landscape you did not expect.

To feel alive, to understand that 11 months of working from home are worth if you can ride one week out in the wild.

This has not changed in 50 years, and I hope it does not for the time I will be around.

I think that the same thing applies to Software Testing.

Yes, the tools are evolving, we now automate a lot of the setup, the testing, the monitoring, our systems require a lot less of maintenance than before, and are able to scale way better.

But yet, it is about the people who are working on a project, it is a matter of the relationships we have inside the team and the company.

It is about describing problems, helping others understand the risks and what coices we have.

Yet we have not figured out quality, we are not able to bake it into the product, it can not be created afterwards, it has to be the most important thing to consider when building a product, or it won´t be.

I might get back to this book some years from now. I plan to continue riding, and to make software testing a living for a while.

And to ride with my kids.

Looking back to 2020

Yes, a lot of things happened, but since we're going to forget many of them, let's review a few worth remember.

European Testing Conference.

I was invited to Amsterdam to give a talk explaining my journey from Tester to Product Owner.

The conference went fine!
I had the chance to de-virtualize people I knew for a long time, to meet new people and to see old friends.

The talk went quite well, and somebody thanked me for waking up their tester soul.

Hey, that was a nice praise! and that was a great last European Testing Conference.
I want to express my gratitude and admiration for all the people involved in running those 5 events, and for letting me help a bit along the way, it's been a pleasure.

And yes, somehow we turned this conference trip into a family adventure, but this is how we like doing these kind of things.

MoT Tour.

So, my good friend Tomislav came up with a fun idea, how about delivering 3 talks in 3 days in 3 cities?
Of course, I accepted, and there we went. 

We delivered three talks in Madrid, Barcelona and Valencia in 3 days. I got the chance to meet a lot of people and had a great time, even that I finished quite tired at the end, but as Bon Scott once said, it's a long way to the top.

Family time.

As the situation evolved, and quarantine was imposed, I moved to work from home, and the kids moved to study from home as well, so we got a lot of time together.
We have been playing games, watching movies, discussing life and finding ways to adapt to this ever changing situation, and it didn't go bad, at least we made it through the year, one day at the time.

My wife and I we have been together for 20 years now, and one thing we been doing more often this year is going for a ride.

As Keith Klain well said, the road is the journey, and there are plenty of roads out there waiting for us.

Tenerife.

Summer came and we didn't have any plan. With all the situation evolving, there was no way to make plans, let alone going for a road trip like we have been doing since 2013.
But then, things happened, and Iberia announced a discount for healthcare workers, and in a couple of weeks we went from not having a plan, to flying to Tenerife and spend a week in this wonderful island.

Good times never come alone, you need to plan for them, but sometimes plans come together in unexpected ways.

Voicemod.

I'm back to testing!
I never went too far away, but starting in July, I joined the Voicemod team as a Software Tester to help with the testing thing. 

You know, make questions, evaluate requirements, test working software, write bug reports and test session reports, have fun with the team, automate tests, learn about software, processes, infrastructure, tools, users, competitors, grow as a professional, be a professional skeptic, all things I love from this job.

I got lucky that we also hired Belén, and that together we have been building an interesting automated test suite that is helping the team to achieve the levels of quality we're searching for. She even wrote an article about it. 

Good things will come out of this team, just wait and see.

Flywire.

My former company made it to the news, but this time it was because they decided to do a layoff due to COVID and the change in the business context.

It was not the first time I saw this happening, but the perspective of being one of the laidoffs was new and interesting for sure. 

As it happens in any spaceship, it turned out that I didn't have my astronaut suite, I was part of the fuel.

But hey...

Pradeep Soundararajan wrote a book, The buddha in testing, this book helped me understand that it was just a business as usual.

He also wrote an article with a new job description, Product Owner's Testing Assistant, and featured me, along with Jon Bach as somebody that would fit in that job description.

I'm very grateful to Pradeep, for helping me understand many things, for many years, in different ways.

And I'm grateful as well to all the flymates, for these good years we had.

As Johnny Cash sings...

"Now I been out in the desert, just doin' my time, Searchin' through the dust, lookin' for a sign
If there's a light up ahead well brother I don't know, But I got this fever burnin' in my soul
So let's take the good times as they go, And I'll meet you further on up the road"

Ride to Cabo de Gata

In July 2020, we went for a three day ride, the longest bike trip we been to, up to this date.

Some context.
My wife is my riding partner. I been riding since I was 17, she got her license after we got married. I bought a Vespa PX200 back in 2002 when I worked as a courier and I needed a cheap bike that was easy to maintain.
At some point, back in 2012 we started renting a second bike and going out for a ride, and since we did enjoy this time together, we do go for a ride every now and then, so in January 2019 we bought a Honda Rebel 500 as a second bike.

The planning.
Given this is 2020, and we have COVID-19 cases all around us, planning a trip is a complex task.
The problem is around the uncertain evolution of the cases, the more to the future you want to plan, the greater uncertainty you have to deal with, and you don´t want to put your money in advance for a trip you won´t be doing.

So this time the plan was different. There was no plan, we only had options.

We managed to arrange a weekend where the kids would be taken care of, then we decided that we had three places where we would like to ride. We had two nights out, and we were riding out of Valencia, Spain where we live, so...
We could try driving north to mount Tourmalet, West to the Sierra de Cuenca mountains or South to Cabo de Gata.
We also decided not to book a second bike in advance, to not put money in stake, but to just drop by the bike dealer on last Thursday and give it a try if they had anything we could rent. If we didn´t find second bike, I would do the trip on the Vespa.

The bikes.
Then, when the Thursday arrived, I went to the local Yamaha dealer. As any decent bike dealer, they have a set of test bikes you can use for a quick test ride before purchasing one. Many dealers offer this service, but Yamaha Spain went a bit further, and they also offer the chance of renting one of the demo bikes for some days.
They had a spare Tracer 700, so after the brief paperwork, we had the bikes ready.

The ride.
On Friday morning we checked the news and the healthcare information, COVID-19 cases were worse to the North, so we decided to go South.

We managed to travel 1200km in three days. We went all the way down to Cabo de Gata on our first day, then went up north to Albacete by crossing the Cazorla natural park, and the last day we went back home by riding to Requena.

Some lessons.

The Tracer700 is a great bike for travelling, it has fairing, powerful engine, wide tires... and the Honda Rebel did exactly the same trip without any of those. It's not the bike what makes the biker, it's the attitude.

Riding without a GPS is fun, but you will get lost, and by the time you're back on your track you will be tired and late.

Have a bandana on your neck, and if it get's too hot, soak it in cold water when you stop for fuel.

Get a bluetooth intercom, so you can talk with your riding partner.

If you are going to an area with plenty of accommodation, you can book a room by the time you get there. But if the hotels are scarce, you better book in advance and plan accordingly.
Our first idea was to sleep in Riópar, but by the time we went there we could only find a room in Albacete. And this added a couple of riding ours to an already long day.

Some people don't ride out of their commuting route, some people ride a lot and afar. It doesn't matter what others do. Find what kind of riding makes you happy and enjoy the ride.

My last day at Flywire

Yesterday was my last day in Flywire.

How does it feel to be laid off after 8 years working in the same company, the same project, along with the same friends?

Ah, it feels strange, yes the company has given me good exit conditions, yes there was no drama in all the process, yes we are still friends.

But I liked my job there, I liked it more than my exit process.

Looking back, we did a great job, I joined the team when we were 25, and left when we were almost touching the sky.

I got the chance to travel, to develop my career as a Software Tester and as a Product Manager above any expectation I could have when I joined the company.

I had the chance to meet awesome people, inside the company, and getting to events, conferences and trainings.

All those experiences, from sunsets in the Caribbean to sunrises in a frozen Gulf of Finland, from the San Francisco bay, to the bar close to the office.

I got the chance to grow a team, to help other teams grow, to try developing all kind of new skills.

I always saw this job as an adventure, and all adventures come to an end, so that new adventures can start.

My days at Flywire are over, some of my stories will be around for a while, the friendships will last forever.

Looking back to 2019

I like writing a year review post, it comes handy when I want to get back in my memory, Maybe I read this post in the future, maybe my kids read this post in the future, I don't know, the future is hard to guess, but the past is worth remember.

We started the year with a new bike! This nice Honda Rebel 500 is our second bike at home, since we do keep the Vespa up and running. Having a second bike means that going out for a Sunday ride my wife and I is only a matter of finding a plan for the kids. At the end of the year we passed the 6K kilometers with it, all of those were joyful.

When this 2019 started, I was busy producing videos for internal use in Flywire, one of those videos flew me to our London Office, and since I was in the City I went for a beer with Antony Marcano. As a long time follower and reader of this man, I really enjoyed his company.

European Testing Conference came to Valencia! Maaret Pyhäjärvi and her crew organized an incredible two day conference in town, bringing speakers from far away. We helped with the logistics, and with our flywire office space to host the speakers dinner and an Exploratory Testing retreat.

Just because we felt like doing so, we had a Formal Friday, a fun event to suit up and have a good time at the office.

The family went to Tenerife, such a nice place on earth. This island is a whole continent by it's own, with mountains, jungles, deserts, forests and valleys. We went up to the Teide top and down to the seaside, and marked this place as somewhere to return in the future.

And we also went to Portugal, this time on a road trip. We like going on road trips to nice places, and the southern coast of Portugal is a nice place to go.

I changed role, I moved from being a video recording product analyst to a bank statements matching and partner integration focused product owner. And I got the chance to join a team with  some of the oldest developers around.
A team where the ego game is low, where people is open to listen to suggestions and crazy ideas, where we take our jobs very seriously, and the serious matters with humor. A team that has helped me grow and learn as a Product Owner and as a storytelling fellow.

Since I moved to the product team, I started going to product related conferences, where I soon noticed that product has it's own folklore, contradicting ways of doing product development ( solutionists vs problemologists ) and a nice and supporting community.

This year, we lost our first tester, (in 8 years, it had to happen someday...), and this big guy left the company to seek fortune in another ship. I wish him the best, we still go for brunch together from time to time, but boy, do I miss this fellow metalhead.

Talking about metal, we went to Madrid to see Amon Amarth perform live. Having a night our with my wife without the kids is a rare happening, but if it is going to be like this, I can't wait for the next time. Turning married life into an adventure!

We went to visit my parents in Bilbao a couple of times, and even that it is easy nowadays to stay close with calls and video-conferences, it is nice to have some time to drink a coffee, talk and hug each other as well.

This summer we went to Scandinavia, in a two week long road trip, keeping with our summer tradition of driving somewhere. We went from Copenhagen to Bergen and then to Stockholm. We saw valleys, fjords, viking towns and overwhelming nature all along the way.

Back from an unforgettable 5 week summer break, I went to Madrid to attend Peopleware conference, where Javier Garzás and his crew are running a nice agile development-centric one day conference.

We also drove to Lisbon to join Productized conference, a two day event with talks and workshops where I learned a lot of things while my wife and kids were exploring the city.

 

Closing the year, the Valencia Product team went to a team lunch where we shared success and failure stories.
This 2019 has been a great year for us. We have integrated with Banks and Partners from Australia, Indonesia, VietNam, China... we have explored new ideas, automated a lot of manual processes, fixed all kind of problems, we have built a solid foundation for what our company will be in the next years.

 

And of course, we did a year closing party, welcoming this new twenties in old twenties style.

For this 2020, I have work to do, a family to care about, places I want to visit and people I want to meet.

Good times.

From Tester to Product Owner

Now that I have done my first 6 months as a Product Owner, I would like to write about four tools I had on my tester belt that came handy when it was time to do the Product Owner thing.

Broken clutch cable == no problem!#Vespa life! #Px200 pic.twitter.com/liaZBaJYDf

— Jokin Aspiazu Jensen (@JokinAspiazu) April 18, 2018

1. Problem bash.
In software testing, doing a bug bash is about getting people around some software, defining the scope and the mission and letting people work around the feature trying to find as many bugs as possible.
As Product Owner, there has been a couple of times where we performed a problem bash, where we sat the whole team around a problem, and talked about how we were going to approach the solution. Once we got the understanding of what the problem was, and what a solution might look like, I started writing the user stories, but not before.

In both cases, you get the benefit of diverse points of view, you get the benefit of a shared process of learning, you build the team that is going to work on the solution, and both cases are a fun thing to do.

2. Cynefin for Product Owners. 
Cynefin is a framework for understanding complexity. Testers who know about this framework know what kind of testing is best depending on the situation the project is in, so, depending if you are learning, if you have experience, or if this is a crisis situation, different techniques should be applied to the development process and the testing.
When it comes to Product Owning, when it comes to writing stories for the team to work on, I realized that we could use the framework.

Simple, When there is no learning to do, when everybody knows and understands what needs to be done. Simple problems can live in the backlog for months waiting to get some time window to get solved, and if all you have are simple problems, you can work in slow one month sprints. Simple issues are rare.

Complicated, When only somebody in the team has the expertise to work in the problem, then writing the issue is not enough, now we need to make sure the availability of the one who understands the problem, and that this person can help others understand it as we fix it. Also complicated is when the learning has a impact in other teams, say Operations or Customer Support, then the learning that will happen with the solution needs to be planned and shared. When you have several complicated issues, you want to move to shorter sprints, say two or three weeks, so you can get the feedback from the involved teams about how all these changes are doing.

Complex, When nobody in the team, the company or anywhere else has solved this problem before, then we need some space to experiment in a safe way, to understand first and learn after. Once you get into this complex problem point, estimations about when solutions will get done are meaningless, since you can not predict the time you need for discovery. When we got into a complex scenario, I tried to run the backlog without a defined sprint, and even that the first weeks the team ran quite well, while everyone was aligned and working in the same problem, it happened that as the weeks passed, we kind of missed the pace you get when you work on sprints, and we moved back to one week sprints.

Chaotic, You run into chaotic situations when the team needs to solve situations without considering backlog, when you are impacting users in production or when you put the business into risk. When this happens, you need to understand that the flow of information is going to be different, that your stakeholders are now support or infrastructure teams, that you need to help for the stabilisation of the problem first, and then do the analysis and the learning.

Disorder, Good old Disorder is when you are not aware of the right situation. So you ask the team to handle a certain problem in a way that doesn't match with the situation the team is in.

3. Context Driven Product Owning.
When I started testing software, the Context Driven Testing approach got me hooked, I understood how to get out of testing with test cases, I understood how I should better use my time as a tester, and when I moved into an agile team, it helped me to fit into this new mindset. Also the community around this principles happened to be very supportive for me, at that moment.
So, when I moved into Product Owner role, I could still make good use of the principles that were defined. I'll give you my top three:

• People, working together, are the most important part of any project’s context. And when we say people, it is not limited to the development team, it has to be wider, and include other teams in the company, Operations, Support, Infrastructure, Security... and also teams who work for other companies trying to build integrations.

• Projects unfold over time in ways that are often not predictable.
  Sometimes you start a project that seems to be the most important thing to work on, and as the project evolves, and the learning happens, some of the assumptions we started with will fade away, developers might run into technical issues that were not anticipated, or anything in between, from marriage, birth and other vital issues, to legal, compliance or whatever other happenings. When you are going to run projects, you better get ready for this, and deal with it.

• The product is a solution. If the problem isn’t solved, the product doesn’t work.
  Sometimes we might develop the solution we want to do, with this team, in the time we want to spend working on it... and once we have built it, we find out that the problem doesn't really fix into our solution, or that now that we have built something new, we run into new issues.

4. Storytelling.
As a tester, you soon understand that part of your success is how well developers are able to understand your bug reports. Writing "This is not working" is not an option, and you need to elaborate your writings, after all, this is your contribution to the team, so you need to learn how to do this.
When you move to Product Owner, the team trusts you to help them understand the problems we want to address, so again, writing "Just do this" is not an option.
A model I find useful, is Campbells Hero Journey, so before I start writing my user stories, I do a sketch about the problem, the characters, the stages and the story line, and once I have this clear, I would start writing my user stories.

I started testing software because the boss had fired all the testers he had in the shop.
I started as Product Owner because C-level director told my manager to change my career, starting tomorrow.
There is a pattern here, I'm not worried about this and the learning curve is exciting and challenging.

I think just as Software Testers come from anywhere, we can move to many roles as well, we can learn new ways to test, we can manage people, or we can try new disciplines, as I am doing with Product Owning.

As long as there is a journey, there is discovery, learning, challenges and a nice project to work on, it's going to be fun.

5. Celebrate
Wait, there is another one... When you manage to complete a project, a milestone, a tricky integration, make some time, grab the team and celebrate. We are all together in this.

Salva, Manel, Andoni, Edgar, Jaume, me, Manel, Paco and Albert