Monthly Archives: December 2012
#6 – CHANGES COMING SOON TO ISO 9001 AND COSO – SANDFORD LIEBESMAN – QUALITY@RISK
I’m a committee member for two very different standards—ISO 9001 and the COSO internal control guidance document used to comply with the requirements of the Sarbanes-Oxley Act (SOX).1 While these documents cover different activities in an organization, they share a need to update the current versions.
COSO is a management system that was originally developed in the 1980s in response to the savings and loan scandal. It is used for internal control over operations and compliance to external financial reporting requirements. COSO consists of five elements used to manage systems of internal control: Continue reading
#6 – SOFTWARE DEFECT ORIGINS AND REMOVAL METHODS – (C) CAPERS JONES – TECHNOLOGY@RISK
The cost of finding and fixing bugs or defects is the largest single expense element in the history of software. Bug repairs start with requirements and continue through development. After release bug repairs and related customer support costs continue until the last user signs off. Over a 25 year life expectancy of a large software system in the 10,000 function point size range almost 50 cents out of every dollar will go to finding and fixing bugs. Continue reading
#6 – WHAT YOU SHOULD NEVER DO WITH A SUSPICIOUS COMPUTER – CAROLYN TURBYFILL – TECHNOLOGY@RISK
#6 – HOW TECHNICAL PEOPLE BLOW INTERVIEWS – ELIZABETH LIONS – CAREERS@RISK
It’s a shame when a technical person blows an interview. It makes me uncomfortable because I get concerned we may have missed something in our hiring process. What if our process caused some great engineer to not get the job? What if all the skills were there, but we failed to ask the right questions.
Interviews are by and large difficult – for anyone. The potential employee feels pressure and unnatural. Technical people may have the most difficulty if their communication isn’t strong or clear.
Here are the five common things that go wrong in a technical interview: