Tag Archives: it-agile-blog-planet

Agile Testing, Exploratory Testing, Kanban, Scrum, XP

Tell a story at the daily standup

1 Comment

Yesterday during my keynote at the Agile Testing Days 2012 I said I see a lot of standups, where testers report on their yesterday’s work in the following way:

Yesterday I tested the thing with the stuff. I found some bugs, and filed them. Today I will test the foo with the bar.

I think this is horrible test reporting. While concluding the fifth beta of Elisabeth Hendrickson‘s upcoming book Explore it! I found a few more hints in the same direction. On the same line I will relate good test reporting during the standup to what for example Michael Bolton talks about when it comes to test reporting – we should tell three stories during test reporting:

  • a story about the product
  • a story about testing
  • a story about the process
Continue reading Tell a story at the daily standup →
Scrum

Certified Scrum Manager – somewhat more than a rant

18 Comments

In the past I have been more than skeptic about certifications. I even wrote about my minimum requirements for a certification programme that might (or might not) add value in an article called Meaningful Certification?. Despite the split between the two larger organizations (and their early leaders) on Scrum – the Scrum Alliance and Scrum.org – yesterday I noticed that the certification scam has taken on new levels with a program called Certified Scrum Manager (IAPM). Here is my honest critique about it, and I will try to rant as few as possible about it.

Continue reading Certified Scrum Manager – somewhat more than a rant →
Agile Testing, Context-driven Testing, Testing

A testing landscape

2 Comments

On my way to EuroSTAR 2012 I was starting to think about the Cynefin model, and landscape diagrams which I know from giving some courses. I tried to relate them to software testing, different techniques, and I was not sure where this could lead me.

I had some exchanges with Michael Bolton, Bart Knaack and Huib Schoots on my early draft, and I wanted to share what I had ended up with. So, here it is.

Continue reading A testing landscape →
Agile Testing, Testing

Code Coverage – useful or misuseful?

8 Comments

This year I took all three courses on Black-box Software Testing. Each of them means an investment of four weeks of my time, usually up to 2-4 hours per day. This was quite a blast, and I am happy that I made it through the courses.

One thing that stroke me in the first course was the different uses and misuses of code coverage discussed in the first part, the Foundations course. Here is a short description of things I have seen working, and not working so much.

Continue reading Code Coverage – useful or misuseful? →
Agile Testing, Context-driven Testing

GATE No. 2: A transpection report

1 Comment

Two weeks ago the second GATE workshop took place in our offices in Munich. Unfortunately some of the participants couldn’t make it. So, there were the three of us, Meike Mertsch, Alexander Simic, and myself. Although we were a bit low on energy in the morning, the day turned out to be a wholesome day of transpection – or if you prefer, we did a lot of test chat. Here’s what still sticks with me from the day.

Continue reading GATE No. 2: A transpection report →
Agile Testing, Context-driven Testing, Leadership

ALE2012 Lookback

1 Comment

It has been about three weeks right now since the second Agile Lean Europe in Barcelona. Although I had the best intentions back then, I promised to write a blog entry about my experiences there, I didn’t do it until now. It seems the best stuff I take away from the break-out conversations in the coffee breaks these days when at conferences, not so much from the session itself. This also holds for the ALE 2012.

Continue reading ALE2012 Lookback →
Context-driven Testing, Testing

Trip report from the Ukrainian Testing Days

2 Comments

Last weekend I was invited to Odessa, Ukraine for the Ukrainian Testing Days, a conference that Andrii Dzynia co-organized. Andrii has organized public testing dojos in the Ukraine in the past. He asked me to put the reports from their sessions on my blog in an English translation. I think he does great work there for the Ukrainian community. So, I was eager to see that community in action. I had a pleasant trip, staying in Odessa was very comfortable to me, especially since Julia Cherniak dropped me from the airport, and led me around in town on the first day. Here is a full report from my roughly two days in the Ukraine.

Continue reading Trip report from the Ukrainian Testing Days →
Agile Testing, Software Craft, Test Driven Development

Testautomation Coderetreat No. 1 – A report

3 Comments

Last Saturday we had the first testautomation coderetreat in Munich. Woohoo! This was a kickstart for this new coderetreat format – besides the original one from Corey Haines, and the Legacy Coderetreat format from J.B. Rainsberger. Here is my report from the facilitator’s point of view and with some hints about what I am going to try at different other follow-up coderetreats.

Continue reading Testautomation Coderetreat No. 1 – A report →
Agile Testing, Testing

The BDD pitfall

2 Comments

Last week I went to the 2bd SoCraTes conference, the German Software Craftsmanship and Testing conference. We did two days of open space discussions, and we all had great fun. One thing though that caused me some extensive amount of trouble, was the amount of sessions around BDD.

Some time ago, I wrote about the given/when/then-fallacy. But this time was different. Despite the amount of emphasize that BDD puts on the ubiquitous language, I was shrugged by the fact that folks were pointing to different things while talking about BDD: It seems BDD suffers from the same thing that it tries to prevent: having a common understanding about stuff.

I don’t know where this particularly comes from, and I also saw a couple of bad scenarios when it comes to the usage of tools like Cucumber or JBehave. I don’t consider myself a BDD expert, and people pointed out that I do something different around acceptance tests. Still I thought to expose some of my thoughts about some of the examples that I ran across recently – and helped out improving. Here’s my though process on two of these scenarios.

Continue reading The BDD pitfall →