What to expect from Iceberg’s PMO

We established a formal Program Management Office (PMO) at Iceberg in 2016, with a mandate to ensure a predictable client experience across all projects and programs. I wanted to provide this outline to give prospective clients an idea of what to expect when working with Iceberg from a program management perspective. Over the years, we’ve tailored our approach to match the unique expectations and requirements of organizations when it comes to GRC solutions. Our methodology is designed to keep your project on track, while ensuring that stakeholders remain focused on the strategic outcomes for the program.

Our team approach
A typical project team is comprised of five roles: account manager, senior consultant, program manager, developer, and tester. Each role encompasses very defined responsibilities which, when joined together, result in the output of a successful GRC roll-out.

Once a Statement of Work (SOW) has been executed between you and Iceberg, a Program Manager (PM) is assigned to your engagement. This PM is charged with overseeing the total success of your project or program by working hand-in-hand with the Account Manager (AM) and defining success criteria.

Iceberg’s methodology is very much one of constant collaboration. At Iceberg, we follow a Waterfall-Agile project methodology which has proven to be the strongest concept when rolling out GRC solutions. This concept allows us to define Agile iterations (backlog, revisions, QA) on an iterative basis but all within the constraints of overarching Waterfall milestones (start & end dates, defined milestones, schedule controls, and so on). On average, we find that our engagements span three iterations with defined start and end dates.

Throughout your engagement, you can expect your PM to send you regular project reports which provide at-a-glance visibility into overall health, burn rate, potential issues, and upcoming milestones. This information is presented clearly and concisely with the idea that it can be communicated to curious senior management teams with brevity and simplicity.

Here’s a sample project schedule which you’ll find within your project report. (An MS Project Gantt is also an option should you prefer that format.)

Sample project schedule

Sample GRC project schedule

 

A series of iterations
Since Iceberg’s project methodology follows a highly predictable iterative structure, it is simple to understand how your requirements translate into the software configuration. Each iteration follows a similar structure:

gather requirements → demonstrate the configuration → implement revisions

This gives all stakeholders regular intervals at which they can verify that we are on track in accurately manifesting their business requirements within the GRC solution. This approach gives you the opportunity to make small adjustments early in the process, which helps you avoid potentially costly changes later on. Here’s a diagram that shows a more detailed view of the iterative steps in a typical GRC configuration project.

Solution Development Lifecycle Diagram

Sample of Iceberg’s Solution Development Lifecycle

 

Once a demonstration has been reviewed and your feedback implemented, we ask you to sign-off on the configuration indicating your agreement that what you have seen in the demonstration fulfills your business requirements as defined in the SOW.

Testing, training, and user adoption
Once sign-off is received, we move onward to the following iteration until we reach the User-Acceptance Testing (UAT) phase. It’s at this point that we recommend a UAT Preparation Workshop which is a half-day session walking your team through what’s been configured in order to convey a deeper understanding of the solution which they will be testing.

UAT is comprised of thorough functional testing by the business group coming together with guidance and feedback from the Iceberg developer and tester. The culmination of this phase results in the deployment of the solution into your production environment and signifies the start of a 30-day “warranty period” where Iceberg provides support to resolve configuration defects. Most clients opt to have a “lite” end-user training session at this stage which, again, walks your team through the configuration and includes modifications made during the UAT phase. This training helps further user adoption and position you for success now that your solution is in production.

Driving deployable success
Our approach has been tested and refined through many years of experience of driving deployable success for clients in a variety of industries, on projects big and small. Whether you’re an existing customer or you’re considering working with us, I would be happy to answer any questions you may have about what to expect when engaging with Iceberg. You can reach me at dammura@icebergnetworks.com.

Share this post:

Derek Ammura

About the author

Derek is the Senior Program Manager and Director of Iceberg's Project Management Office. Through the PMO, he leads the development and implementation of consistent, effective, and reliable project methodologies which promote project delivery excellence for GRC customers.

Subscribe To Our Newsletter

Subscribe To Our Newsletter

Sign-up to our Risk Intelligence Newsletter for updates on new content, resources and events from the Iceberg team.

We promise to respect your time and inbox!

Thank you! Please check your email to confirm your subscription.