We’re getting quality more wrong than we are right. Which is fascinating, when you get down to it, because quality is the foundation on which project management is built. Why is this a problem? When everything is a constraint, nothing is.
Test functions are often viewed as independent, somewhat isolated parts of the project execution environments. It doesn’t have to be that way…in fact, it shouldn’t be.
Testing has been seen as an unavoidable evil. But as we change and adapt, we must test all of those changes to help ensure they work properly, work as designed, meet the organization’s needs and are secure.
The testing team forms a small sub-group within your project team. They’ll be looking to you for guidance on what to expect--and how you expect them to go about it. Here are five things to remember to tell your testers before they get started.
Many technology project managers focus on building or improving applications. Businesses rely on reliable and high-quality applications to serve customers and maintain operations. If you are in the business of application delivery, read on to see how agile can help.
Anyone who has been involved in application development projects is familiar with the testing squeeze--the compression of time available for testing. How do we manage to prevent it?
Why are so many bugs and defects getting through to production? Even as the time devoted to testing is expanding, the dynamic nature and complexity of systems is outpacing most IT organizations' ability to keep pace. Here are some tips to help improve your testing results.
|
"Tragedy is when I cut my finger. Comedy is when you walk into an open sewer and die." - Mel Brooks |
