Related Content
Is Our Innovation in Software Testing Keeping Up with Technology? The world of software testing has made many important advances in techniques and approaches, but is it keeping up with the leaps and bounds of technology's progress? Mike Sowers is an advocate for a revolutionary breakthrough in software testing, and to get there, we all need to become innovators. Here's how. |
||
Scaling Product Agility: More Product, Not More Process Focusing on scaling product discovery that feeds product delivery is valuable to scaling frameworks. A cross-team product discovery cadence highlights work that's valuable to everyone and facilitates workflow for all the teams, helping them produce more of what they really need (and less of what they don’t). |
||
Test Automation Is Mandatory, Thanks to Agile Unlike waterfall, where people had to do their best to explain the value of automation, agile more naturally promotes that need for these tools through its rapidity and integration of testing throughout the development process. Agile assumes automation is the key ingredient of your mission strategy. |
||
Do You Design Your Software Process for Flexibility or Repeatability? Manufacturing design looks a lot like software: You iterate through possible solutions, and the manufacturing itself is about repeating the making process. But building software means learning about the problem as you solve parts of it. For that, you want flexibility. How do you find your ideal process? |
||
Make Better Software by Learning from Your Mistakes If you accept that it’s OK to make the same mistakes over and over, you’ll never give yourself the opportunity to grow. If you don’t grow, you won’t improve your software. A writer should always ask why an editor did what he did, and a developer should understand how he can fix the code he broke. |
||
To Deliver Value in Your IT Projects, Understand Context First Starting a project without understanding can lead to a mess from a usability perspective. Too often, we build what we can without taking the time to question whom we are building it for and why. A user story is a simple but effective tool to determine how much we understand about the context of a problem. |
||
IoT Security Concerns for Quality Assurance Teams In addition to the typical Internet-related security concerns, applications are being made specifically for IoT devices, all of which bring about additional security concerns that quality assurance teams need to consider. |
||
How Poor Testing and an Early Release Can Damage Your App and Business Mobile or PC apps that crash, have poor user experience, don’t run smoothly, or lack features give your customer the idea that whatever they bought didn’t get the tender, loving care it deserved—even if they know the issues can be fixed in a later release. |