IT Management - eWeek




How to Simplify Your Governance, Risk Management and Compliance Process





  Table of Contents:
  1. How to Simplify Your Governance, Risk Management and Compliance Process
  2. Roadblocks of Traditional Maturity Model
  3. Process-Only Technologies Can't Scale
  4. A Better Deployment Maturity Model
  5. Benefits of Vertical Maturity Model

To comply with various standards and regulations, companies have traditionally adopted governance, risk management and compliance technologies in a commonly accepted maturity model. But here, Knowledge Center contributor Pravin Kothari challenges that traditional governance, risk management and compliance adoption maturity cycle and proposes a new model for governance, risk management and compliance technology adoption.

Print Version Sponsored By
How to Simplify Your Governance, Risk Management and Compliance Process - Benefits of Vertical Maturity Model
( Page 5 of 5 )

Benefits of vertical maturity model

This vertical maturity model has the following three benefits:

Benefit No. 1: Demonstrate vision and success quickly

A long-running project timeline is one of the top reasons for IT project failures. By piloting a narrowly defined use case, the project team can show success and vision quickly. By demonstrating to the organization what the automated end state looks like in a miniature scale, it validates the business case and generates excitement for continue investment.

Benefit No. 2: Minimize change management

Change management is often the most difficult part of any new technology adoption project. It takes tremendous time and effort to change how people do things. By achieving the final automated end state in one phase, the project team can avoid repeatedly asking users to change process and adjust to new tools.

Benefit No. 3: Validate technology selection early

By implementing full automation in Phase 1, the project team can fully test out the automation capabilities of the chosen technology platform. If the right technology has been selected, then the project team has reduced the risk of technology failure for future phases. If the wrong technology has been selected, then the project team can still cut its losses and make a change without too much lost investment. In other words, if you want to go to the moon, you better figure out early if you bought a car or a rocket.

Pravin Kothari is founder and Chief Technology Officer at Agiliance. Pravin is responsible for product vision, product strategy and engineering at Agiliance. Pravin has over 20 years of success at bringing new products to market in information security, compliance, enterprise software, software as a service, and large-scale software infrastructure. Prior to founding Agiliance, Pravin was the founding vice president of engineering at ArcSight, where he led the product development for five years from inception to market dominance. Prior to ArcSight, Pravin was the founding chief architect at Impresse Corporation. Previously, Pravin held technical leadership positions at Verity, Attachmate, and Tata Consultancy Services.

Pravin holds a Master's degree in Computer Science from the Indian Institute of Technology (IIT), Bombay. He is a Certified Information Systems Auditor (CISA), a Certified Information Systems Security Professional (CISSP) and Charter Member of TiE, a global organization dedicated to the advancement of entrepreneurship. He can be reached at pkothari@agiliance.com.



 
 
>>> More IT Management Articles          >>> More By Pravin Kothari
 

FEATURED SPONSOR MESSAGE

Microsoft Sponsored Resource Center

Increase Your Microsoft Office 365 Knowledge! Dig inside this suite of cloud-based collaboration tools.

Watch the video >>

Brought to you by





Advertisement
eWEEK Quick LInks

 
Close this advertisement