Blog

Part 16 in a series of 17. To start at the beginning, first read Agile vs Fragile: A Disciplined Approach or an Excuse for Chaos.
In the traditional development space we are all very familiar with the testing tools that are available. We know about industry leaders such as HP Quality Center, QuickTest Professional and Performance Center.  We understand the value they add to large projects and how they are essential to ensuring that the testing process is well managed and delivered.  But what about Agile?  Do these same tool Read Entire Entry

Part 15 in a series of 17. To start at the beginning, first read Agile vs Fragile: A Disciplined Approach or an Excuse for Chaos.
Often times teams make the argument that Agile means that there is no longer a need for  “independent” teams of testers that verify that the solution was built correctly according to the requirement specifications.  They argue that this is now the role of the “super developer”, and the business representative, who are both embedded into the team.  After all, the business knows what they Read Entire Entry

Part 14 in a series of 17. To start at the beginning, first read Agile vs Fragile: A Disciplined Approach or an Excuse for Chaos.
If you were to survey a group of very frustrated testers about why they have problems with their Agile teams, you would find that in almost all cases they get frustrated trying to get any documentation that helps them identify what to test.  Every time they request even minimal documentation, the development team pushes back and says that documentation isn’t needed because Agile eliminates the need Read Entire Entry

Part 13 in a series of 17. To start at the beginning, first read Agile vs Fragile: A Disciplined Approach or an Excuse for Chaos.
The last Agile principle is all about retrospectives. This is one area where a lot of teams have dropped the ball. They don’t take the time to do retrospectives because people don’t understand the value they bring. They are perceived as a waste of time that could be spent on the next development sprint.  What they fail to realize is that on a long marathon, it is the small corrections in the Read Entire Entry

This is the fourth installment in a multi-part series to address the basics of performance testing applications. It’s for the beginner, but it is also for the experienced engineer to share with project team members when educating them on the basics as well. Project Managers, Server Team members, Business Analysts, and other roles can utilize this information as a guide to understanding performance testing process, the typical considerations, and how to get started when you have never embarked on such a journey.
Let’s use a case Read Entire Entry

Part 12 in a series of 17. To start at the beginning, first read Agile vs Fragile: A Disciplined Approach or an Excuse for Chaos.
Agile principle eleven deals with the team itself. This principle focuses on the enablement of the team to leverage their unique position as the closest people to the problem manage the work.  It also enables the team to safely take risks. The team is typically creating new solutions, and doing it in a rapid fashion. Agile promotes the team trying new things without worrying about being chastised for Read Entire Entry