This posting will be a small experiment using Twitter. As Gojko’s session was one of the most commented ones on Twitter I just distilled this blogpost out of all the corresponding tweets. One nice effect of this is that the re-tweets already show which topics have been seen as the most important ones. So have fun with “Agile Tweeting”!
(read more…)
category: Agile Testing | 
1 Comment so far
This post is written on 14. October 2009 by Thomas Jaspers.
This was really an excellent session and it was especially great as the things teached do not only apply to one’s professional life, but can really be useful beyond. Probably I still have to do some thinking on this, but here is what I was able to note down from the session.
(read more…)
category: Agile Testing, Agile Testing Days | no comment
This post is written on 14. October 2009 by Thomas Jaspers.
Are you now or have ever been … on a team that was pressed or overruled into releaseing flawed or unfinished work? I guess everybody has. After in introduction to Scrum he comes to the value of the “Definition of Done”. How it helps to have consensus and common understanding, manages expectations so that a release does not surprise the customer and have repeatable quality.
You should have a Definition of Done on different levels, for Tasks, Stories, Sprints and Releases. For example:
category: Agile Testing, Agile Testing Days | no comment
This post is written on 14. October 2009 by Andreas Ebbert-Karroum.
So, this session is apparently about TPI, and the acronym was now already mentioned a few times, and maybe I should now it, but I don’t. So in contrast to yesterday, where I was expecting everybody to know what BDD is, now I am the one who does not know what most of the others (a quick show of hands confirmed that) do know. So let’s find out.
category: Agile Testing, Agile Testing Days | no comment
This post is written on 14. October 2009 by Andreas Ebbert-Karroum.
Correctness can be confirmed at any time is the subtitle of Mary’s talk and it start off with the clear statement that Waterfall does simply not work. So let’s hear what works 
.
The question is how to deal with complexity and the answer to some extend is divide and conquer. Mary continues with some history on how to archieve this. Basically everything has been “structured” back in the 70s, which does also not really solve the problem as we know today. But what we really want is not to inject defects already from the very beginning. An early answer to this was given by Edsger Disjkstra which basically was a form of layered architecture.
category: Agile Testing, Agile Testing Days | 2 Comments so far
This post is written on 14. October 2009 by Thomas Jaspers.
Visited and written by: Andreas & Thomas
The answer to the question from the tile of this keynote is: Yes! As already partly in the tutorials yesterday Lisa has again emphasized how important it is that there are no silos in agile teams. Instead it is all about solving the given task (developing quality software) in a collaborative mode. To do so (agile) testers are as important as (agile) developers and all other potential members of the team.
(read more…)
category: Agile Testing, Agile Testing Days | 2 Comments so far
This post is written on 13. October 2009 by Thomas Jaspers.
