Monthly Archives: July 2012

LogiGear Magazine – July 2012 – Testing In Agile

LogiGear Magazine July 2012 Testing in Agile



Disciplined Agile Testing

There is a multitude of Agile testing techniques that are quite sophisticated. The DAD process can help guide your process of tailoring decisions.

By Scott Ambler, IBM

Agile developers are said to be quality infected, and disciplined agilists strive to validate their work to the best of their ability.  As a result they are finding ways to bring testing and quality assurance techniques into their work practices as much as possible.  These strategies include rethinking about when to do testing, who should test, and even how to test.  Although this sounds daunting at first, the agile approach to testing is basically to work smarter, not harder.


In The News – July 2012

Chris Floyd Interview on Implementing Agile Development

Michael Hackett sat down with FNC’s Chris Floyd to get his take on numerous Agile topics.

Chris address some of the burning questions surrounding Agile, such as teams switching from waterfall to Agile, challenges and successes his team encountered after implementing Agile, and the path to becoming a ScrumMaster.

Chris Floyd has worked in the financial services sector for 11 years. He loves to eat at dives, and in his spare time he trains diabetic alert dogs for Wildrose Kennels.

The video can be found here:


Agile, Testing and The Need for Speed

Agile, in terms of software development, has incorrectly and for too long come to mean fast and “getting product out the door quicker.” But Agile is not about speed; it is about being flexible.

By Michael Hackett, LogiGear

I always begin my discussions on Agile development by getting a definition for the word Agile.  Agile, in terms of software development, has incorrectly and for too long come to mean fast and “getting product out the door quicker.” But Agile is not about speed.  It is about being flexible and responding to change.  When I say this, I then pull out the Agile Manifesto. Nowhere is speed or faster mentioned.


Ten Tips for Agile Testing

This article presents ten tips for Agile testing based on our experience. However, don’t expect to find the perfect test approach for your company or software project in this article. That is still something you will have to find out yourself!

By Ralph van Roosmalen

Several years ago I started as test manager on a J2EE project. The project team had switched from a waterfall approach to an Agile approach with Scrum a few months earlier. The first question the project manager asked me was, “Can you write a test plan for our first release?”

I quickly produced a project test plan that called for a test phase of a few months and a separate test team. It came complete with a capacity calculation per week for the testers, a MS-project document, and a matrix with all the quality attributes and the effort we should spent to test every attribute. What a mistake!


Agile Methods and Software Testing

Agile methods were developed as a response to the issues that waterfall and V-model methodologies had with defining requirements and delivering a product that turned out to be not what the end user actually wanted and needed.


A software tester’s role in traditional software development methodology, a.k.a waterfall & the V-model can be generally summarized as:

  • Finding defects in development products, such as requirements and design documents
  • Proving that the software meets these requirements
  • Finding where the software under test breaks (whether that is through verification of requirements or validation that it is fit for purpose)

A Tester’s Perspective on Agile Projects

Agile is a philosophy focused on delivering constant value to customers  incrementally and frequently, based on communication and feedback. These two ingredients are vital to a successful Agile recipe.

By Pankaj Nakhat

Agile is no longer a buzzword or an unknown territory in the industry. Agile has progressed leaps and bounds the last few years and has matured to a widely accepted methodology. Testing in Agile projects required a paradigm shift for traditional testing roles. It required a change in tester’s attitudes from a relay race oriented approach to an upfront involved role. The Agile approach focuses on getting things right the first time, reducing the need for QA testers to get something over the finish line. But it’s easier said than done. How does it happen in reality? Does it actually happen?


Agile Testing: Key Points for Unlearning

When quality assurance teams and management who have adopted Agile practices first put the ideas to work, they face a significant impediment in unlearning the traditional mind-set and practices that experience in traditional practices has instilled in them.

By Madhu Venantius Laulin Expedith

“He who knows to unlearn, learns best.” — Anonymous

The following are some of the key aspects that need to be unlearned before attempting to deploy Agile practices from a QA perspective:

  • The testing team needs to be independent and independently empowered in order to be effective.
  • Without a separate test strategy and test plan, it’s tough to manage testing.
  • The V-model for verification and validation cannot be applied in an Agile sprint.
  • Independent testing teams don’t do white-box testing.
  • The value of testing is realized only when defects are logged.
  • Automation is optional and is required only when regression testing is needed.
  • Testing nonfunctional aspects, such as performance of the system, is not possible in a sprint.
  • Testing must follow planning, specification, execution, and completion sequentially.
  • We don’t have to write new test cases for detected defects.
  • Poorly written code is not the testing team’s focus, as long as the code addresses the required functionality.
  • Test-process improvement models do not address aspects of Agile testing.

Let’s look at these assertions one by one.


Proposal For An Open Work Space

Agile stresses instant and easy communication and is built on teams working efficiently together. This necessitates an open work space environment.

By John Roets, ITX Corporation

A characteristic of an effective team is a high level of collaboration, making the physical work environment an important factor. Cubicles should be eliminated in favor of an open work space in an effort to produce a higher level of collaboration, and thus provide more value to the business and a higher level of employee satisfaction.

My claims follow a logical progression. Work space design is important. Collaboration is important. Employee satisfaction is important. Cubicles are a poor choice for work space design and an inhibitor to collaboration. An appropriately designed open work space will improve collaboration and employee satisfaction, and this leads to improved results.


Vietnam Scope: Beaches Abound

Whether you’re looking for a  5-star resort or a UNESCO World Heritage site,Vietnam’s 2025 mile coastline has something for everyone.

By Brian Letwin

Vietnam is a country with a plethora of natural beauty which manifests in many different ways. And with 2025 miles of coastline, the country’s beaches are perhaps the pinnacle of that beauty. The characteristics of these beaches vary widely—some feature pristine natural beauty, while others have been developed and cater to millions of resort-seeking tourists each year. But no matter how developed, these beaches share two universal qualities — rich history and great seafood.