Approaching Agile Testing

As many are aware (or should be), "Agile Testing" is not a completely different testing procedure, rather a testing approach, which aligns with the principles of Agile software development. 

But how? Well, the most salient aspect is that it emphasizes testing and close coordination with the end-users or at least with the story owners, throughout the project life-cycle.

Why Agile Fails: The PA-SA-WAKA-DA Theory

It is funny to notice that, more often than not, we only hear the good stories in each segment of our lives. That applies equally to Hollywood, where we only get to see the shining stars, but ignore the struggle that goes behind it, or any successful Agile project, where we see and relish the success, forgetting the relentless effort by a dedicated team. Does success cover the entire story? Of course not! There is a very dark side as well — which is often not too exciting to hear or encouraging to know — but very insightful if you wish to learn what not to do to avoid failure.

It is repeatedly presented that only 42% of Agile projects succeed in truly being Agile. The other 58% struggle (50%) or fail (8%)! So, what are they doing differently that keeps them from success with Agile? This is interesting to know — as doing or being Agile, may sound different, but in reality, they are very closely-related, only differed by the span of its usage.