GRC advisor Webinar, Part 3
We have launched our GRC Advisor webinar series to strengthen and extend our existing, successful cooperation with consultancies. Both sides profit immensely and complement each other with a wealth of invaluable experience. This post summarizes the key messages in Part 3 of our GRC Advisor webinar series.
Different models of cooperation
There are various ways that tool vendors and consultancies can work together in this phase. In the classic variation, the tool vendor joins the project at a set point in time and spearheads the implementation. The GRC advisor continues to provide expert advice and is responsible for select topics on behalf of the client.
Another tried-and-tested scenario in one in which the GRC consultant heads the implementation project. You take over responsibility for managing the tool project, whereby avedos still provides certain support services on a point-for-point basis. This primarily refers to tasks involving reporting, dashboarding and customized developments that must be performed by our experts. There are certain requirements for this model. In particular, we place great value on building the infrastructure within your organization so that you can work independently. You will also need to complete our partner onboarding training.
We have designed this onboarding concept based on our initial projects and experiences with partners. In a mere ten days, you will be trained in everything that you need to know to implement projects at your client sites. The training covers a solid mix of theory and hands-on learning, starting with basics such as the scorecard concept or specification sheets and working up to the actual configuration in the product. Day 6, for example, focuses on the action matrix, which covers visibility controls. Day 10 provides a review of the complete training contents.
The first project usually begins as soon as onboarding has been completed, with you as our partner taking on project leadership. We, of course, are there by your side - especially at the beginning - and are available to answer your questions at any time.
Alternative project approaches
Once the project management responsibility has been clarified, the project implementation is the next big question to address. Currently, agile methods are all the rage. Here it is extremely important to align client expectations to this agile approach. In a waterfall approach, for instance, project objectives must be clearly defined and remain stable. Agile projects, on the other hand, have clear time and budget guidelines while the project objectives have somewhat more leeway. When working on a client project together, we recommend making this decision as a team, defining a certain working style, and ensuring that everyone involved stands behind this decision.
Important features of the project approach
Aside from budget issues and working with more variable targets, we feel it is essential for clients to understand that they will need to involve themselves more fully (although less intensively) in agile projects.
Beyond waterfall and agile approaches, individual hybrid approaches can also be a sensible option.
Special aspects of the analysis and design phase
Documentation: Following the sales phase and internal project handover through our team, a meticulous documentation is essential - especially when the requirements have changed. If the project management does not lie in our hands, documentation is even more critical for support and other downstream project phases.
Availability of the client contact: The respective contact people are extremely important - both for our cooperation and in workshops. It is also beneficial to get key decision-makers on the client side involved in order to get fast, reliable answers to decisions that lie ahead.
Ongoing project communication: Project communication is another important point that, in our opinion, can never start early enough. For us, it means informing the entire organization about the project and its meaning for the organization early on. We have also had good experience in integrating select end users at an early stage. Users, for example, who reflect local views, can help simplify the later stages of the project especially heading up towards the roll-out.
risk2value library is a collection of GRC components that can be used in implementation projects. There are three main reasons why we launched this new product:
- We want to make our implementation projects even better through higher standardization and deliver faster, more agile results to our clients. The growing demands to quickly produce prototypes were a key driver.
- Once we have built the first system together, we want our clients to develop it further on their own. This includes enhancing the system itself (e.g. refining an ERM system or adding quantitative evaluations to qualitative ones) as well as adding related GRC processes or completely new use cases.
- Finally, we want the library to serve as a platform that encourages the knowledge exchange among clients, among partners, and among clients and partners.
Our long-term goal is to add business components to our technical ones in the future. For more information about risk2value library, please contact Claudia Howe.