quality management
 |
Software Project Management: The Responsibility of Communicating Quality Trade-Offs Some requirements are negotiable, even if it sounds like they aren’t. But expectations have to be managed carefully to avoid problems. Payson Hall explains that when executives agree to sacrifice quality in order to hit a deadline, it's up to the team to ensure they understand the tradeoff and possible risks. |
|
 |
Agile or Not, You Need a Proper Customer and User Experience Process In order to satisfy the people you hope will purchase or download your software, a proper customer and user experience process has to be built into the software development lifecycle. Whether you follow an agile, waterfall, or completely different methodology, this is a step that can’t be skipped. |
|
 |
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? |
|
 |
Quality in Quantity: How App Quality Is Now Everyone’s Responsibility Quality has increasingly become a responsibility for not just one single segment of the team, but the team as a whole. It’s important for each member of a team to have some hand in making sure that what’s being developed works as intended as it goes through each individual progression. |
|
 |
Handling a Check Failure in Test Automation What happens on your team when a check (what some call “automated test”) fails? Regression tests or checks that are effective toward managing quality risk must be capable of sending action items outside the test/QA team quickly. How do you provide fast, trustworthy quality communications from your team? |
|
 |
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. |
|
 |
The Lean Startup Methodology and Its Value for Testers Testers are rarely part of an entrepreneurial startup team, but are there lessons for them in the lean startup approach? Lee Copeland says yes. The basic idea behind lean startup is that companies should focus their time and resources more efficiently, and this concept surely can benefit testers. |
