Archive for the
‘Verification’ Category

The blog “Testers Do Not Break the Product” was posted on LinkedIn and there were considerable responses and exchanges.  In an effort to continue that same discourse, I post some of that exchange. Many thought the language “breaking”, as did many others, to be unclear or ambiguous. The language in this discussion originates from the […]

Agile Verification Blog Recollection In our past blog posts we discussed a conventionally executed (staged gate) project with constituent parts (the verification) being executed using agile techniques. We realized we missed some pertinent information in our series post of agile verification in a conventional project. Agile Verification Prediction We talked about the burn up chart based […]

As we execute the test cases, we will likely find failures. These failures or faults will be reported into a reporting system that will allow us to track the failure resolution. We can also use that here in our progress tracking sheet.

Agile in Conventional Project Line Management The following is a story from a couple of years back.  The story is about lengthy set of verification activities (multiple iterations) in a large conventionally run project.  As many a test engineer will relate, testing is always cramped for time. Meaning, the time we want the answers is much […]

What is concurrent engineering? Concurrent engineering is when activities are paralleled that could be sequenced. Concurrent engineering can help us deliver the product earlier since we have compressed the schedule by overlapping the various development activities.  There are certain risks associated with this way of working. To be successful and not incur massive rework, it […]

Recently, on twitter, I had an occasion to express my discontent for the word Pragmatic.  My spontaneous outburst so amazed me that I decided to explore this further.  The definition on dictionary.com[1] is: Of or pertaining to a practical point of view or practical considerations Philosophy of or pertaining to pragmatism Of or pertaining to […]

The project organization should use the Configuration Management process to script the project and product growth – instead of just the version control. In this way the product content is adjusted formally from the learning that should have happened in the prior work.

We have referred to Stochastic Testing in an earlier blog post as an exploratory technique.  We provide a Google definition of exploration below: Exploration – the action of traveling in or through an unfamiliar area in order to learn about it. Stochastic testing is not compliance testing (requirements) even though we are exercising the product […]