You may be familiar with the concept of a “project audit.” In terms of software, a project audit is a process of verifying that development is on track, meets standards and compliance needs, is consistent with final specifications, meets contract agreements, and a range of other criteria…
Now, at first glance, this sounds an awful lot like the process of IV&V. You’re right to see the similarities, but they are not one in the same. Today, we’ll look at a few critical differences.
Project Audit Scope
The primary difference to consider here is scope. Project audits can be powerful tools, but are typically limited in depth and frequency of interaction. Whether performed by an internal or external team, project audits typically focus on the following:
• Conflicts of interest
• Policy compliance
• Separation of staff duties
• Sarbanes-Oxley Act compliance
• Security protocols
Understand that project audits can also have other components – these are just some of the most typical. Companies may employ outside auditors for more rigorous evaluations, but most will stick to a similar checklist.
It’s also critical to mention that audits are not ongoing. It may only include a few periodic evaluations at key stages of development.
IV&V Scope
Where the essential goals of IV&V are similar to those of a project audit – verifying compliance and functionality, evaluating code, reviewing budgets, and so on – IV&V goes much, much deeper. The main difference to recognize here is that IV&V is an ongoing process. The third party performing the IV&V processes will become an integrated part of development, working with staff, leaders, and stakeholders alike.
Where project audits may stop at evaluating the software itself, an IV&V team will have the project management experience to take a big picture view – including budgets, timelines, customer/user expectations, update plans, and so much more. Where project audits are periodic, and only performed during development, IV&V continues after a software goes live.
Put briefly, IV&V is like a project audit on steroids. It will go far beyond a surface level audit of functions, and dig into the methodology and goals of development, the details of each function, and the large scale success of the entire project.
Collaboration vs. “Punishment”
Another thing to consider: how does your team feel about this process? The way your staff perceives the evaluation – whether that’s a brief project audit or full IV&V – will have an effect on how they respond to changes in protocol, recommendations, guidance, changing timelines, etc.
With project audits – which may be performed by internal staff or a third party – it can feel like an intruder coming in to look over shoulders and scrutinize employee efforts. At its worst, it can feel like punishment for making mistakes or not meeting deadlines. This does not foster a healthy, productive work environment.
While these feelings may also exist when an IV&V team comes on board, it will likely wear off as the IV&V specialists become embedded into the workflow, as they become trusted advisors and key team members, as their expertise begins to catch problems early and improve development.
Working with an IV&V team becomes a relationship of collaboration. This doesn’t mean a project audit team won’t also collaborate with your staff. They may, however, be perceived as “outsiders” or “intruders.”
This makes staff more resistant to their input and negatively impacting the workplace dynamic.
There are plenty of other differences between IV&V and project audits – mostly to do with the depth of analysis and sophistication of evaluation. Hopefully this helps you see the basic divide between the two. To learn more about IV&V, and how it can drastically improve the quality of your development projects, contact us today!
Share this Post
