|
Case Study: Selling the CMM Envision a slow day, a slow meeting, and someone says in a nonchalant manner something like, "Raise your hand if you want to do a CMM." Only two hands go up—but it makes a difference whose hands. From this casual setting develops an all-out effort involving hundreds of people in training, implementing, and integrating the CMM into the development culture. Here is the story of how one large financial services company mobilized for its CMM initiative.
|
|
|
Keys to Setting Achievable Goals David Schmaltz identifies five types of goals—aspirations, constraints, regulators, targets, and legacies—and shows how to find common understanding and create meaningful objectives in team projects.
|
|
|
Testers and Developers Think Differently Appreciating differences is critical for productive teams. Different approaches aid in finding solutions, and mutual respect dramatically improves group problem solving. Testers should not be judged according to developer criteria.
|
|
|
Getting Published Why would you want to get published? Why take time out from doing real work to share your thoughts with others? After all, didn't we gladly leave writing behind when we got out of school? But when you share your experiences, you play a part in a larger picture, leaving your mark on the world, and advancing your field.
|
|
|
Behind Closed Doors: What Every Tester Should Know About Web Privacy The explosion of personal information on the Web has made privacy a primary concern. Here are pointers on making sure your site works for security-conscious users, as well as information to help you avoid inadvertent compromises of privacy.
|
|
|
When Assessments Are Relative Taking development and business contexts into consideration can mean the difference between a correct assessment and a useful assessment. Here's information on how to provide an assessment that's both correct and effective.
|
|
|
Managing the Communication Storm Front The communication storm front is a real phenomenon that crops up in all development teams and in all organizations. You need not be the victim of such storms. You, as development manager, have the tools to reduce the power of the storm front and create a team that is ever more effective and efficient.
|
|
|
Finding the Signal through the Noise A major challenge for software professionals interpreting data is deciding what's real and what isn't, what matters and what doesn't. A useful way to think about it is that you are trying to find the signal in the noise produced by random variation and error. Here is advice on how to extract the useful information from the "noise."
|
|
|
Weinberg on the Essential Team The team is the basic design unit for software engineering processes. Within the team, reviewers can learn without having to admit to ignorance, and their learning is always relevant to the team's tasks. When there are multiple eyes, there are many more chances to see a fault. Learn how to create and get the most from your team.
|
|
|
Automating Requirements Traceability Developing software to meet users' specific needs can be a difficult task. Verification and validation activities can help ensure that you are building the right software right.
|
|