Related Content
 |
A Strange Story of Version Control and Software Customization As he was doing an inventory of a company’s commercial software and version control, Payson Hall got an odd response from a vendor: Their software has no versions. Each client has a unique, customized edition of the software. How can the vendor possibly support that many products? How would that work? |
|
 |
Validate Your Core Business Assumptions Early On Verifying whether a product is being built per specifications is only solving half of the problem. Validation is a very significant activity performed by testers to ensure that the final product is ready for consumption by users and answers an important question. Are we building the right product? |
|
 |
IoT Devices: Why Accessibility Should Be Your First Priority Just because something is new, shiny, and more fully featured doesn’t mean that everyone is going to want to use it. Even if your IoT-enabled smart grill is voice-activated, it still has to be both consistently functional and as easy to use as a regular grill. |
|
 |
The Consequences of Project Delay An often overlooked and underappreciated aspect of project schedules is the consequences of delay on others. Due dates and commitments sometimes matter more than they appear. Knowing the larger context of your project can help you prioritize how you undertake it, consider options, and improve problem-solving. |
|
 |
Moving into a World of Conscious Quality Conscious quality is a quality effort that is independent, end-to-end, and stretches beyond the bounds of the core test team. If conscious quality is not adopted, we run the risk of losing the sanctity of our independence, impacting the quality of the product as well as our careers are testers. |
|
 |
The Ethical Responsibility of Defect Severity Classification When dealing with defect classification, it's important to not blindly adhere to the criteria without consideration for real business or human implications. If your software does safety-critical work, do the defect levels reflect that? Or could something go live with potentially disastrous consequences? |
|
 |
DevOps or NoOps: Can You Have Too Much Automation? Some DevOps thought leaders have been promoting “NoOps,” which is the notion that IT resources can be provisioned in a fully automated way that does not require operations engineers to manage. There have been notable successes with this approach, but also some challenges. Can you have too much automation? |
|
 |
Calculating the Cost of Failure What is the cost to your business of an outage due to a major bug? Usually it's calculated as mean time between failures multiplied by mean time to recovery. But what if you could deploy to a limited number of users and monitor effects? Then the equation includes a third variable: number of users impacted. |
