TimeLine Postmortems We should use project postmortems to improve our software process. But few teams do, and fewer teams reliably learn from project postmortems. You can introduce postmortems to your team easily with a timeline postmortem process. If you are already doing postmortems, a timeline-based approach may improve your results.
|
Seth Morris
January 9, 2005 |
|
![]() |
Not Your Father's Test Automation If you think that test automation is mostly about executing tests, then you're missing out on a big opportunity. Or rather, you're missing a lot of small opportunities adding up to a big one. Consider this: stop thinking about test automation as merely executing automated tests, stop thinking about test automation as something you need expensive tools for, and start discovering automation you can implement in a couple of days and usually with extremely inexpensive tools or tools you already have available. In this week's column, Danny Faught and James Bach suggest taking a more Agile approach to test automation. |
|
Best Practices for Software Projects–Software Measurements The key to efficient measurement is to first determine what goals you are trying to accomplish and what problems you are attacking. Many organizations waste time and money by measuring more things than are necessary. Before beginning a measurement strategy, determine the goals for your measurement. |
Steve Miller
December 6, 2004 |
|
Learning Speed from Quality Programming As software professionals we spend far too much time fixated on speed and asking questions about how long a task is likely to take. In this week's column, Mike Cohn says we need to focus more on quality than speed. When something is done well, it's only a matter of time until it is done quickly. |
||
![]() |
Being Resourceful When Your Hands Are Tied You work hard to find tools that can help you. You learn how to use and configure them. Then you find yourself working in an environment where you can't even use them. Have you encountered this frustrating situation? Danny and Alan have encountered this frustration many times before, and in this week's column, they're here to say you don't have to abandon all hope. If you're creative, you can still find tools to use–even in the most inhospitable environments. |
|
Outsourcing Testing Tasks IT's continuing push towards cost reduction has led to the burgeoning of the outsourcing industry. Implementing an outsourcing strategy is quickly becoming the competitive advantage for companies that need to test software and related components. Outsourcing firms offer other advantages and benefits that may have been previously overlooked, including cost savings. Jose Fajardo examines these benefits and other competitive advantages associated with outsourcing testing tasks for companies interested in transitioning to an outsourced testing strategy. |
Jose Fajardo
August 26, 2004 |
|
Design and Code Inspection Metrics In this study, historical inspection data from large real-time embedded systems were analyzed with the intention of improving the current review process. |
||
The Future of Code Coverage Tools Modern optimizing compilers are becoming increasingly dependent on dynamic profile information. Because the profile information collected by these compilers also is sufficient for QA, it is likely that code-coverage analysis will become an integrated development environment option. This integration should help to simplify your code development and testing processes and should also improve the accuracy of your coverage information and the performance of your optimized code. |
||
A Strategy for Risk-Based Testing The fact that you test an application extensively does not itself render the application more stable. However, NOT testing an application increases the risk that the software may not comply with the requirements and won't necessarily provide the expected business value. Here is a method for approaching risk-based testing. |
||
White Paper: Sarbanes-Oxley and the Need to Audit Your IT Processes The first section of this paper discusses the role that IT will play in complying with the Sarbanes-Oxley Act. We examine the sections of the Act that IT executives should take most interest in and how they can be at the table when key decisions are made regarding Sarbanes-Oxley. The second section discusses three popular frameworks or methodologies that can be employed to help establish internal controls for the purpose of complying with Sarbanes-Oxley. |
Jeff Smith
May 28, 2004 |
Pages
Upcoming Events
Sep 22 |
STARWEST Software Testing Conference in Anaheim & Online |
Oct 13 |
Agile + DevOps USA The Conference for Agile and DevOps Professionals |
Apr 27 |
STAREAST Software Testing Conference in Orlando & Online |