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.
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.
To be truly successful, a project needs more than a list of requirements and good intentions. Here's a way to use project charters to define the big-picture relationship and expectations between Developers and Management.
Management and testers may not often speak the same language. This article takes an unvarnished look at the communication gap between quality advocates and management and offers ways to open a dialogue and gain credibility.
Every day you are faced with juggling resources and attention between customer escalations, current development projects, and planning for the future. With development cycles measured in weeks, you have at least three releases for each product. Multiply that by the number of projects under your responsibility, and you have a dozen or more releases to manage simultaneously.
The chances of getting use from your ISO 9000 certification are greatly enhanced by a registration effort that reflects the real goals and operating principles of your organization. Here are some lessons on how to tailor your effort.
Timely and accurate information is often your only silver bullet against interminable and doomed projects. Learn how to deliver bad news in such a way that Senior Management hears it and acts promptly.
A QA manager is often faced with measuring the impossible. Here is a simple, post-ship metric to help judge the test effort's effectiveness. The Quality Barometer method uses the bug counts found during testing, calculates a percentage, and then uses that percentage as the defect target number that can be tolerated after shipment.