The Latest
Six Impossible Truths about Developing Software - All Before Breakfast[presentation] Alice laughed. "There’s no use trying," she said, "one can't believe impossible things." |
![]() |
|
Transitioning to Agile Development[presentation] The Agile development movement has started to transform the software landscape. |
Jean Tabaka, Rally Software Development
|
|
Project Retrospectives[presentation] At the rate Web vulnerabilities are being discovered and exploited, the security industry cannot afford to continue trying to keep up with patches and fixes. |
Lucille Parnes, Software Process Improvement Consultant
|
|
Multi-Attribute Software Analysis[presentation] Although the methods for measuring individual quality characteristics of software (performance, functionality, etc.) are well known, few organizations have developed useful metrics to evaluate overall software quality. |
![]() |
|
Building a Requirements Foundation with Customer Interviews[presentation] Whether you are building a brand new product or evolving an existing system, understanding the business needs of your customers is the foundation of a marketable product or valuable internal application. |
![]() |
|
Negotiating the Defect Minefield for a Successful Product Release[presentation] Software success is strongly influenced by how you finish a project. For that, a special set of skills is required. |
Robert Galen, Thomson/Dialog
|
|
Twelve-Step Program for a Better Test Process[presentation] We can't make software better by testing the quality into it. However, if we manage our testing processes and educate the rest of the team about what it takes to make better software, we can make a difference. |
Judy McKay, Test & Automation Consulting LLC
|
|
(Almost) Painless Code Reviews[presentation] Peer code review is universally acknowledged as a valuable practice that often catches 60 percent to 90 percent of the bugs in code. |
Frederic Boulanger, Macadamian Technologies Inc
|
|
Unitizing Legacy and New Code for Unit Testing[presentation] All code is unit testable, regardless of its origin and current state. Although it may not appear so, there are techniques you can use to safely get any piece of code under automated unit tests. |
![]() |
|
Using Code Metrics to Target Refactoring[presentation] Often times, deciding what code to refactor (rewrite) is based upon the code's smell, a subjective determination by developers. |
![]() |
|
Defect Prediction with Reliability Growth Modeling[presentation] Although typically used at places like NASA, reliability growth modeling also can be used for common business and financial applications. |
Michael Allegra, GSX
|
|
You've Just Been Named Manager of Software Process Improvement[presentation] We have all heard of the accidental project manager, but how about the accidental irocess improvement manager? |
Sandi Oswalt, First American Credco
|
|
Establishing a CMMI Compliant Metrics Program[presentation] Implementing a useful measurement program that also addresses the measurement requirements of the SEI CMMI® process areas can be a daunting task. |
Steven Lett, The David Consulting Group
|
|
A Manager's Survival Guide to Going Agile[presentation] When software development teams move to Agile methodologies, they often leave the project managers behind. |
Michele Sliger, Rally Software Development
|
|
Agile Process Improvement and the Evolution toward Software Factories[presentation] The concept of software factories is becoming a hot topic in software engineering circles. So, how can the factory model fit with Agile development practices? |
Damon Carr, AGILEFACTOR
|