Here at Lighthouse, we’re awful passionate about software testing and quality assurance. But even as thought leaders, we like to keep ourselves up-to-date on the latest cutting-edge insights and industry trends. In that spirit, here are some of the most interesting things we heard at StarEast 2017.
For some IT leaders, software development projects can feel like an endless cacophony of defect-related rework and delays—especially for people involved In software testing and QA. But as frustration mounts, pinpointing a path to improvement can prove difficult. Our solution? Start with quality exit criteria.
Everyone’s had at least one software project release off schedule and over budget. But while delays may seem like a ubiquitous hardship for software testing/QA teams, they don’t need to be. In our upcoming June 29th webinar, we’ll delve into why projects so frequently get blown off course, and break down the steps you can take to get them back on track.
Every software project is judged by four factors: time-to-market, agility, quality, and cost. But while those are typically seen as your developers' domain, aren't your software testers and QA engineers the ones really responsible for them?
Doing the same thing over and over again and expecting different results is the definition of insanity. So if your software projects are releasing off schedule, over budget, or without their expected scope and/or quality, why not sign up for our upcoming webinar and learn how to prevent the root cause of software failures?
If the 3 Perils of Software Development™—Defects, Delays, and Dollars—are regularly driving your projects off schedule and over budget, getting your QA and testing team back on course can be hard. That’s why applying a metrics-based testing methodology is so important—it’s the most reliable course correction there is.
Talk to anyone well-versed in eCommerce, and you’ll likely hear the same refrain: the user experience (UX) is king. But while no one’s disputing that, it’s important to note that the reign of UX has also signaled the ascension of another two-letter acronym: QA—or as it’s also known, quality assurance.
Everyone says that software testing teams need to have a plan. They need to be proactive, metrics-based, and thorough; not reactionary or improvisational. But consider this: if an organization’s goals aren’t aligned with the business they serve, is their plan really all that good anyway?
Imagine trying to launch a new website for the holiday season, and your offshore developer delivers defect-laden code with far more bugs than you expected. Do you launch the site anyways—risking widespread user frustration—or do you correct the defects while missing the busiest shopping season of the year?
When it comes to software testing, improvement comes in one of three fields: people, process, and tools. But while you might think processes and tools are the smarter categories to consider first, did you know the bulk of your improvement comes solely from having the right people, with the right skills, in the right roles?