The Latest
Creating Team Norms[article] In their eagerness to embark on a new project, project teams sometimes overlook an essential aspect of their effort—building a relationship among team members, which will foster not just a successful project outcome, but also a satisfying work experience. Investing in relationship building is invariably less costly and time-consuming than recovering from the divisiveness and conflict that may result from its absence. And that's where team norms come in. |
||
Turning Data into Information -Tricks of the Trade[presentation] This article explains the difference between a measure and a metric. |
Edward Weller, Software Technology Transition
|
|
Integrating Risk Management into Your Project Plans[presentation] The goal of risk management is to develop information that supports informed decision-making. |
![]() |
|
Techniques for Measuring Software Quality[presentation] A software defect is any flaw or imperfection in a software work product. A software defect is the result of a mistake in the design of a software process. |
James Rozum, Union Switch & Signal Inc
|
|
Project Management and Collaboration: Using the Web to Improve Your Projects[presentation] The speaker requested that these proceedings not be available online. |
Marnie Hutcheson, Ideva
|
|
Software Development on Internet Time-Faster, Cheaper, Worse?[presentation] This article details high profile corporate disasters and how your company can avoid making the same mistakes. Checklists and tips on how to get your team to communicate better are also included. |
Girish Seshagiri, Advanced Information Services
|
|
Judging Use Case Quality[presentation] Great test procedures cannot compensate for poor requirements. Good use cases are hard to write. This article details how to develop an effective use case for your project team. |
![]() |
|
Team Size and Its Effect on Peer Reviews[presentation] This article discusses the prerequisites to quantitative management. How to create effective teams by determining recommended team size for inspections is also discussed. |
Mark Paulk, Carnegie Mellon University
|
|
The Real Job of Software Managers[presentation] Presentation not available online. Speaker will make presentation available electronically to all participants. |
![]() |
|
Creating a Great Team: Ready, Aim, Hire![presentation] Create a great test team by: assessing your team to see where you need which kinds of strengths, defining the job you need filled, asking great interview questions to weed out unsuitable candidates, and by matching their answers to your needs |
![]() |
|
Improving Measurement Capability[presentation] Following CMM can lead to improvements in: productivity, early detection of defects, reduction in time to market, and a reduction in post-release defects. |
Beth Layman, TeraQuest Metrics Inc
|
|
SM/ASM 2003: The Power of Retrospectives[presentation] This paper discusses and explains the differences between post project reviews and retrospectives. Three retrospective case studies are also detailed. |
![]() |
|
Leading Successful Software Projects[presentation] Presentation Leading Successful Software Projects |
![]() |
|
Use Cases for Maximizing Project Success[presentation] This article will teach you to: understand how use cases can be used on non-oo projects, employ solid techniques to develop "good" use cases, leverage use cases to increase user accountability for requirements completeness, and how to apply m |
Carol Dekkers, Quality Plus Technologies Inc
|
|
Gathering Requirements in a Low-Process Environment[presentation] Knowing the requirements for a system means understanding the problem to be solved. If the problem isn't understood, the solution can't address it. |
![]() |