One of the big problems I see with a product orientation (as opposed to a project) is in preparing for ongoing work. You might not start the next project for this product after you complete this project. You might have to round-robin projects for various products because you don’t have enough people to do all […]
I posted my slides from my keynote from Belgium Testing Days 2012 at slideshare.net. The keynote was “QA or Test? Does it Matter? You Bet it Does!” I hope you enjoy it. “This person has more stories and may be funnier in person than the slides appear to be.”
Who’s in Charge of Quality? At the Agile 2010 conference a couple of weeks ago, I heard many people say, “When QA gets the software, …” In an agile project, that makes no sense to me, unless the team has not developed its own definition of done. In more traditional projects, the people in the
I spoke at a joint meeting of the RI PMI and ASQ last night. My presentation was “Predicting Project Completion.” I offered a simulation for people to try: predicting the time it would take and then sorting two decks of cards. We learned a lot and had fun. At the end of the meeting, one
INTRO: We all have different attitudes and policies toward finding and fixing defects. The choice about whether and when to fix defects depends upon many factors, one of the least understood being the actual cost of fixing a defect. In this week’s column, testing expert Johanna Rothman shares a formula for calculating the system test
© 1999 Johanna Rothman. Abstract Companies create a variety of products, and different releases of those products, for many reasons. These range from market-testing trial balloons disguised as ‘beta tests’ to releases forced by incompatible changes in operating systems. Some have many changes, some have few. Some can tolerate fairly glaring defects, others have to
© 1996 Johanna Rothman. Introduction Many software organizations are working actively to improve their product and process quality. We can review their implicit and explicit management activities and ask: Which activities have had a positive impact on process and product quality improvement? Which activities have had a negative impact? We can then develop a list