Scope Change and Failure Change happens in that there can be no doubt.  Projects must contend with this pitching deck of an operating environment while achieving the end objective.  A significant negative impact can be change.  Even controlled change can have a detrimental effect on the project success.  To fit the classification of controlled change […]

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 […]

We see some company responses to economic downturn are to eliminate staff as if that were the only way to become a viable company once again. We wonder if these companies have some cost improvement methodology behind them that would give their management other options than summarily removal of personnel.

With Agile, Every Day is a Review Day The constant reviews of status of the project activities via daily Agile sprint meeting, provides the mechanism for the latest state of the project.  This includes the scrum master and product owner apprised of the situation.  I like the analogy of a pilot making course corrections. If […]

Conventional Project The previous two blogs demonstrated a way to employ agile techniques. At the top level the project was executed as a conventional project.  The project had gates, a steering committee and numerous schedule layers.  The organizational structure is balanced matrix (for the most part).  The organization is distributed both by function and geographic […]

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 […]