Project Management

Projects can be linked to many modules in eramba as a way of recording actions required to improve or fix GRC items which are not working optimally.

Projects have one or more Tasks associated. Projects and not tasks are linked to other modules as shown in the diagram below.

The following are examples that show how Projects can help you keep track of improvements or fixes on different modules: 

• Internal Controls and/or their Audits: controls are very important and often tested; projects can be linked to audits when they fail (to record and track the corrective actions) or the parent controls.
• Compliance Analysis: projects can indicate that the organisation intends to transition from non-compliant to compliant with a particular compliance requirement and record and track the actions taken to become compliant. 
• Risks: when describing the treatment of a Risk, Projects can be used to indicate the willingness of the organization to mitigate the risk.
• Data Flows: projects are used to describe that for a particular flow there is not enough treatment and additional controls must be put in place.
• Policies: projects are used when documents are not mature enough and require improvements.