Related Content
Staying Competitive in Software Testing In today’s global economy, staying competitive may be more important than ever. Three ways to contend are by focusing on price, niche (addressing a particular group’s needs), or differentiation (doing things better in some way). Which tactic you choose could make all the difference for your software team. |
||
Building a Business Case for Automation in Your Software Lifecycle To remain competitive, organizations should consider implementing a well-integrated set of automation capabilities—not just for testing, but across the entire lifecycle. Making the investment might take some convincing, so here are some questions to ask in order to assess the potential benefits of automation. |
||
The Best Way to Communicate Project Quality Concerns When you encounter quality concerns in a project, it's important to let management know. But building an overly detailed list of faults and shortcomings undermines the impact of the important points and muddles communication. To effectively convey the crucial issues, you have to prioritize. |
||
Contemplating What Constitutes an Organizational Crisis It can be hard to envision what would constitute a crisis for your organization until you’re facing one. But defining what events could be disastrous for your company is the first step toward planning for them—and having an emergency plan could be the difference that helps you respond in time. |
||
Go-Live Lessons: The Path from Software Development to Production On systems integration projects where a vendor is building or configuring a system for a client, you sometimes cross the canyon from development to production and maintenance in several smaller bounds rather than one big leap. A warranty period after go-live can help stakeholders confidently monitor quality. |
||
Why Is Estimating Software Testing Time So Difficult? Management loves to ask testers to estimate how long their efforts will take. But so many important factors elude measurement that it makes it difficult to predict. If you need to explain why estimation is so tough, here are nine factors that significantly influence our ability to estimate testing time. |
||
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. |
||
Here There Be Monsters: The Value of Data Profiling Monsters appeared on medieval maps to identify the unknown dangers of the sea. Likewise, the data profiles for an organization identify the points within its data. A robust data-profiling strategy can provide a more accurate picture of an organization’s data systems and find risks before they become monsters. |