I am not a developer myself, but for the past ten years I am working in development teams doing one thing or another. Over time, I have seen that one of the factors that makes a team effective is that we need to bring everyone along (if you are interested, you can find the other […]Read More Developer Collaboration Practices
Many of us evaluating our DevOpsishness, have one time or another, answered how well we were doing based on the four metrics defined by the DORA research. Deployment Frequency — How often an organization successfully releases to production Lead Time for Changes —The amount of time it takes a commit to get into production Change […]Read More Intentionally “Failing” the DORA Metrics
I won’t lie. Every time we release something new to our users, I get stressed. Will they like it? Will they use it? Did we miss something? Did we break something we didn’t expect? And over the years, in order to relieve my anxiety, I often wondered: How can we measure the quality of a […]Read More Five Guardrails to Build Up the Confidence to Release
Time after time, whenever I start working in a new team, I find myself gravitating towards the same five practices. I find that once they are in place, our day-to-day work seems to become smoother. Single backlog for all work items One of the first things I do when I start in a new place […]Read More Five Tips for Effective Teams
For the past three years I am working in development teams that don’t employ a professional tester. Even though there are skills I miss working without testers, still these teams manage to deliver software in good quality. Nudged by a Twitter conversation, I started thinking what were the things that needed to be in place […]Read More Prerequisites for Teams Without Testers
Pair programming is by now a quite well known development technique. Developers that have tried it out and chose to go with it, report that they learn more, feel more productive and in general get more satisfaction out of their work. Since I am not a developer I thought I would never be able to […]Read More Pair Product Management
For the past two years I am the Product Owner in teams that don’t have a dedicated tester. Within the team, we discuss in depth the implications of anything new we plan to develop and test before releasing a feature. Everyone has the best interest of our end users in mind and we all strive […]Read More Skills I Miss Working Without Testers
Over the years, swinging back and forth between positions, I found myself often thinking of Charity Major’s The Engineer/Manager Pendulum blog post. The best frontline eng managers in the world are the ones that are never more than 2-3 years removed from hands-on work, full time down in the trenches. The best individual contributors are the […]Read More Balancing Between Stream-Aligned and Enabling Teams
Back in 2017, I wrote an internal blog post about my first visit at Agile Testing Days, called “Are Testers Obsolete? Spoiler Alert, They Aren’t”. Besides the occasional obsolete link, my inability to find the reference to the images (if they are yours please let me know), and my shifting away from testing I still […]Read More Memories of Agile Testing Days 2017
I have been a huge fan of project management with GitHub issues since about 2013. There are two things that make it really appealing to me: The proximity to the code and the overwhelming simplicity that forced you to stay honest when you set up your process. Of course, the lack of a Kanban board […]Read More Trying Out the New GitHub Projects
When it comes to project management tools, my favourite is GitHub issues. I find them simple to use and I like the issue-code proximity. Since adding a label to a repository is so easy, you might lose oversight of all the labels you have and why you have them. Here are some tips for anyone […]Read More Small Tips for Organising GitHub Labels
This post first appeared at Ministry of Testing on November 16, 2020. One of the cornerstones of Continuous Delivery is to establish a reliable deployment pipeline. Each step of the pipeline aims to provide confidence and feedback on the quality of our changes in a timely manner. Removing any blockers from the pipeline should be the […]Read More Broken Pipelines? Somebody Else’s Problem
One of the discussions I keep on having is how practices like Continuous Delivery can jeopardise quality, not allowing enough time for “proper testing”. If every code change can be deployed to production how can we possibly know if the end user experience will remain good? A technique for maintaining a certain level of quality […]Read More Decoupling Deployments from Releases: in Other People’s Words
A couple of weeks ago I had a discussion with my manager whether we can set an initiative that we worked on to “Completed”. We had developed our part and handed it over to another team to consume the changes. But there were good chances that they would come back to us with further suggestions, […]Read More Are we Done? Really Done?
Recently, I was asked to give a 15 minute introduction on Quality Strategy in DevOps for our upcoming “Efficient DevOps with SAP” course and I happily accepted. And then, to my horror of horrors, I realised that I needed to figure out what a Quality Strategy is and what makes it unique in a DevOps […]Read More How does Quality fit in CALMS?