Bugs don’t just magically appear. They are there because of a reason. Someone, somewhere made a mistake, and now it’s a problem. Making sure these mistakes aren’t made, is the responsibility of the entire team.
If a bug does come out, it means someone failed to do their job correctly.
Continue reading “Dehuminization of a bug”
It’s me the tester of your, our, project. I’m writing you this letter to explain what I’m doing. Why I’m an asset to the project and how I can help you! Continue reading “Dear developer,”
This beast slumbers in the mind of developers and testers alike. It is the killer of all creativity and blocks all involvement or ownership in the product. It enables people to pick up a task, drop it off and never look at it again. Why should they, the ticket is now in an other column!
Continue reading “The Ticketmachine”
Because my 99 second talk at Brighton wasn’t completely as I expected, I decided to try it again. You can read my previous post were I go into depth on what happend an what I’ll try to change in my next talks! So I got out my camera and made a video, with these tips on mind. You can watch the result here:
Continue reading “My 99 second talk do-over”
Last month I went to TestBash Brighton. As is the habit, a TestBash ends with people doing 99 second talks. This is an open slot for anybody who’d like to share anything after all the talks are done. I gathered my courage and joined the line!
Continue reading “99 seconds to die on stage”
On my current job we have several development teams developing several smaller applications. This also means we have a lot of deadlines for the releases to production.
Continue reading “The purpose of a release”
During our sprint planning there was a discussion about the files that should be uploaded. What they should look like, and how we should process them.
During this discussion I trying to make my point to the team when suddenly a developer yelled:
Then why don’t YOU do it!
Continue reading “Why a what is better than a why!”