Making Sense of the Information AgeTM A Web Site By David H. Gleason |
| Project Impact Project impact analysis should be done several times during a large IT project, and at least twice for smaller projects. The first audit should occur once the initial project plan is in place, the last one just before rollout. Intermediate audits on large projects can identify risks before the threaten outcomes. As IT professionals know, risk mitigation becomes increasingly expensive as a project progresses. We use a new approach to auditing software projects called the "Software Development Impact Statement"*, or SoDISTM. The technique uses stakeholder analysis to identify, evaluate and mitigate risks. SoDISTM applies the principles of the Software Engineering Code of Ethics and Professional Practice to software development projects. It identifies risks, reduces costs and significantly increases the chances of project success. The SoDIS Project AuditorTM is a software package that facilitates the process of auditing projects. It can be applied by qualified individuals to ascertain areas of significant risk that would otherwise remain hidden. Click here for a brief white paper on the SoDISTM process. Note: This file is in PDF format. Click here to download the Adobe Acrobat Reader® *SoDIS is a trademark of Don Gotterbarn and Simon Rogerson. The Software Engineering Code of Ethics and Professional Practice was adopted by the IEEE-CS and ACM in 1998. |
|