PresentationWith the increased use of independent verification and validation (IV&V) in large ERP projects, there seems to be some common misconceptions about the real value that IV&V is meant to bring to public sector ERP implementations.

IV&V is considered a “best practice” within the technology industry. The primary value of IV&V in the public sector is in identifying high-risk areas early in the project which allows the organization to either mitigate risks or prepare contingencies. It also provides project managers and IT staff with an objective analysis that helps them deal with system development issues and offers improved visibility into the progress and quality of the development effort.

Despite these benefits, organizations should pay careful attention to the perception and the dynamics of the internal project team and IV&V team. Some project managers feel threatened by the IV&V team, believing they are only there to spy on them, undermine their authority or quite simply point fingers. In reality, the IV&V team should be a welcome presence as it can actually provide more time for the project manager to think more strategically about the project as a whole.

Following are five common areas that an IV&V team can address during an ERP implementation and change initiative:

  • Correctness – Is each deliverable correct in respect to its methodologies, conclusions and logic? Is each deliverable accurate with respect to facts and computations?
  • Completeness – Is each deliverable complete in respect to objectives and scope?
  • Consistency – Is each deliverable internally (within the deliverable) and externally (across related deliverables) consistent?
  • Compatible – Is each interface/integration aligning with the solution?
  • Traceability (and Testability) – Can each requirement be independently, repeatedly verified and validated? Are there objective acceptance criteria that the purpose and objectives of the demonstrated results are in the final product?

Independent Verification & Validation is typically brought in for testing efforts. While this is a very critical activity, it should not be the only reason to engage an IV&V team. Our experience and research shows that “cutting corners” to minimize short-term cost actually increases long-term cost. IV&V should provide a 360-degree assessment of the entire implementation.

An ERP implementation should be a partnership between the organization and the IV&V team, where the IV&V team provides tangible measurement and alternatives and helps identify issues which may not be immediately visible. The IV&V team is ineffective if it simply tries to tell the project team what to do – it must engage the project team and help the organization understand that IV&V is essential for systemic change.

IV&V is a time-tested methodology that should be carefully considered as a relatively low-cost insurance policy at the outset of any public sector ERP implementation. Learn more by listening to our on-demand webinar, How to Spot ERP Implementation Warning Signs and Integrate Quality Assurance Into Your Project.

Schedule a Free 30-minute Consultation with an ERP Project Management Expert!

Posts You May Like:

ERP vs EPM: Do You Know the Difference?

ERP vs EPM: Do You Know the Difference?

While there are many different enterprise solutions on the market, enterprise resource planning (ERP) software and enterprise performance management (EPM) software are two solutions that many companies, across industries, consider for their business.  While these two...

HRIS vs HCM vs HRMS: What’s the Difference?

HRIS vs HCM vs HRMS: What’s the Difference?

According to a recent global report, nearly 50% of companies are currently using some form of HR software-as-a-service (SaaS) or platform or a hybrid solution. In 2019, only 20% of companies had adopted such strategies.  Are you thinking about implementing HR...