Related Content
 |
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. |
|
 |
Accelerating Your DevOps Processes with Agile Everyone wants to accelerate the application development process. Agile has done a lot to help, but going faster without understanding whether we are going in the right direction has a significant risk of us getting lost. To really achieve development velocity, you need to understand agile in a pragmatic way. |
|
 |
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? |
|
 |
How Can We Get More Business Value Out of Software Development? CIOs and software development managers can tell you what the budget is for a particular project. But what about the value delivered by a software project? Does your organization make that consideration? The Value Visualization Framework can help you define and track that important factor. |
|
 |
Jelly Beans and Defect Classification: Different Strategies for Success When there’s a bowl of jelly beans, some people grab a few at random, but most of us have favorites. If you're crafty and have flexible standards, you can maximize consumption by adjusting your criteria as colors dwindle. Classifying defects should not be like choosing jelly beans; you need firm standards. |
|
 |
Why Problems Are Good Many large enterprise technology systems have suffered incidents that had significant impact to the customers as well as the firm itself. But experienced IT professionals know that learning from our mistakes is good, and so, too, is harnessing the lessons learned from a serious incident or problem. |
|
 |
Stronger, Faster Quality with Simple, Focused Checks Imagine focusing on prioritized business requirements at the software layer closest to where those business items are implemented. Writing just one check—that is, a programmed verification—per business requirement makes for simple, focused checks, supporting stronger, faster quality around the team. |
