Performance and Scalability testing always comes with a price.  I hear all the time that it is only important when there is a ‘big issue’.  The ‘big issues’ are coming faster and with higher visibility.  If your organization is trying to increase efficiency through more self-sufficient or time sensitive functions (i.e. customer facing website) then it’s critical to have a sound repeatable performance solution for your systems.

This comes at a price as performance and scalability testing is an investment.  However, when you really look at the big picture, can you really afford not to have a sound strategy and solution in place for your customers?

This is something to really think about and consider.

Many organizations encounter the same challenges and problems.

• Tight Release Schedules
• Scope Creep
• Not Enough Resources  (or even qualified)
• Package Software that is delivered late or has a high propensity of defects.

These are typical situations that face all organizations.  The best approach is to deliver your systems with a “risk based” testing approach.  But what does that really mean?

Simply put,  risk based testing is about focusing on key areas of your system and making sure it works at an acceptable level.  “Acceptable Level” can take on many meanings but be clear that this can include many areas but not limited to:  Functionality, Integration and Performance.

The key to a risk based testing approach is starting with a solid Quality Assurance Process.  Many organizations make the mistake of putting a “QA Process” in place that is based on theory and therefore is not effective or practical in their environment (especially when we already know the challenges and problems).

Simple keys to success:

• Develop Test Plans that are working / living documents.
• Understand the integration points and develop Test Strategies based on these key areas.
• Develop a working traceability matrix with is based on critical pathways and testing conditions.
• Design a Testing strategy that understands service level agreements (i.e. not just functionality but performance and scalability.)

The bottom line is we all have challenges.  There’s simply not enough time to test every possible scenario.  Following these simple keys may not “guarantee success” but certainly be a step in the right direction!

Many organizations try to establish IV&V solution. On the surface, it’s a great idea. There are a number of positive best practices that can be used by implementing IV&V. However, when undertaking this initiative, it important to establish an approach, goals and objectives. For example, the role and responsibilities do need to be defined. Meaning: Is IV&V functioning as a simple checklist (i.e. Project Charter Created and on time). Or is it a detailed in-depth audit function (i.e. product specification / design reviews).

Taking the time to establish objectives and goals will make for a much tighter and clearer implementation of IV&V.

The growing popularity of utilizing the Agile Development methodology to develop systems has changed the way software is tested.   Certainly, high quality is still a requirement but the approaches, techniques and artifacts have changed.  In Agile development, there is a common “principle” that for a specific period called a Sprint (usually 30 days), all software will be fully developed, tested and documented and “releasable ready” for production use.

This makes me think about quality and the delivery of system.  Being a huge David Letterman fan,  I would like to mention the top 10 (ten) keys for success when implementing QA within an Agile / Scrum Methodology.

1. We’re all in this together!  Quality is everyone’s responsibility.
2. High Quality is still a requirement  – That doesn’t change!
3. Make sure the User Stories have acceptance criteria.
4. Have an integration test plan
5. Key Processes (Right-Size Weighted!)
6. Concise Artifacts (War and Peace is Over!)
7. Need Right Resources and Skill Sets
8. Automation is critical in Scrum
9. Data Management Setup/Maintenance
10. Finally – Communicate among your team.