How do we bring value? Jeff Van Fleet, Lighthouse’s CEO, thinks we can all do more to bring additional value to our clients, our organizations and our employees … “I believe there are three areas on which good leaders should focus – our clients, our companies, and our employees.” I hope my message finds you doing [...]
It’s October, and odds are your department is waist-deep in building next year’s budget. But while budgeting can be a monotonous, Herculean task, it also can be a transformational one: with a new budget on the horizon, now’s the time to improve your testing team by investing in large-scale, quality-focused initiatives.
Your testing team never slouches, but you always seem to find a bunch of defects in production regardless. But while improving your test coverage, speed, and accuracy is an obvious solution, it’s always seemed prohibitively expensive. With test automation, however, your solution isn’t just affordable—it can cut your budget in half!
When times are tough, it’s easy to get stuck in a rut, dwelling on missed opportunities and past regrets. But instead of fixating on what’s behind us, how can we look forward? Perhaps the solution is as simple as S-W-O-T…
We talk a lot about software testing methodologies around here. And for good reason—they’re a primary component of a consistent and efficient testing and QA organization. But what is a methodology built upon? At Lighthouse, it comes down to 3 things: People, Process, and Tools.
Everyone wants lower costs, shorter schedules, and higher quality in software testing and QA—but you can’t have it all. Upper management wants cost and schedule savings, but you can’t just sacrifice quality, either. Could Risk-Based Testing be the ideal compromise?
How can we be more effective in our relationships? Jeff Van Fleet, Lighthouse’s CEO, thinks we should all take a lesson from Aesop’s Golden Goose…
When things go wrong, it’s easy to dwell on missed opportunities or previous mistakes. But instead of getting stuck in the past, what if we used our negative experiences as an opportunity to improve?
Software is never 100% defect free, so how far should responsible testers go before wading into the murky seas of cost overruns and diminishing returns—and what methods should they use to draw the line?
Everyone fails at one point or another, but what sets the truly great apart is how they learn from it and improve. In the IT world, almost everyone’s dealt with software project failures; but identifying their root causes can be difficult, making improvement impossible—at least until now, that is.
