Related Content
 |
The Mismeasurement of Software Having participated in a number of unsuccessful metrics programs throughout his career, Lee Copeland has identified and distilled four key principles that help prevent the mismeasurement of software. Evaluate how your metrics work against these four principles. Do you need to make any changes? |
|
 |
Mobile Testing: The First Step—or Two On many mobile projects, testing is not practiced well—or sometimes not done at all. Many testers from the desktop world are moving into mobile, and there is much they can take from traditional testing into the mobile space. Here are some ideas to get you thinking about testing mobile devices. |
|
 |
Are Your Metrics Causing Unintended Consequences? When you collect metrics that involve people, it will change the way they behave—but not always for the better. Attaching numbers to how people work often makes them perform their work differently. Every time you gather metrics, you should try to analyze what the unintended consequences could be. |
|
 |
A Tale of Two Projects Large IT projects are challenging. Complexity is hard to estimate well. Big systems are tough to implement. But when you're staring at a fast-approaching deadline and you know your system will not be functional in time to meet it, there are ways of handling the situation that are better than others. |
|
 |
Using Assessments and Standards to Improve Your Process Process improvement is a fundamental endeavor that any successful organization must embrace. The challenge many companies face is how to effectively implement IT process improvement. A good place to begin is with an assessment of current operations; then measure those findings against good criteria. |
|
 |
Accessibility Testing: It's Essential More than 27 percent of the world's population has some form of disability, meaning they could have special needs when it comes to accessing the Internet. Following accessibility guidelines improves the overall usability of the software under consideration, which helps all people using it. |
|
 |
Stop Making the Same Mistakes We keep changing the names of the development processes we use, but we do not fix the fundamental error they all suffer from: the failure to set a date and control the scope of the project—including proper estimation of testing efforts. Customers and IT must work together to truly be successful. |
|
 |
Tips for Improving Your Geographically Distributed Agile Team Many people on agile teams have at least one person who is not collocated. Those on collocated teams indicate that more of their projects are successful; those on far-located teams have the highest number of challenged projects. What can you do if you're part of a geographically distributed team? |
