Putting the Extra A in RAAID

Posted in Latest News, Migration, Stonegate Team, Tech News On December 20, 2017
Putting the extra A in RAAID

Stonegate has been in the IT field for nearly 15 years, delivering countless projects in DC and cloud migrations, service design and support and server virtualisation. As hardcore geeks, our team often like to automate repetitive activities through scripting, however, this time with an exception.

But with Project management, communication, interacting, and customisation are key resulting in variable input, which is something that cannot translated into  Bash or PowerShell script input (as much as they have tried!). So, they decided  to develop a Project Methodology that represents standardisation for executing projects, more like a framework and script for creating a great theatre play or blockbuster movie.

Documentation

Templated documentation is a crucial part of every successful methodology.

With every project we have delivered over the years, we have perfected ways of performing migration and transformation activities in the business environment. Each contributed to our methodology, with improvements then reflected in our documentation, so that forthcoming projects could be delivered more effectively.

The A

The simplest and most attractive example of improved methodology is Stonegate “putting the extra A in RAAID”.

But why?

Every PMO uses a RAID log to track Risks, Assumptions, Issues and Dependencies. It is a bold way to capture and log dependent project shaping events. We need to be aware of risks and take actions to prevent them from becoming an issue.

To lower project complexity and costs, we make assumptions and take Actions to confirm them or appropriately react upon disapproval. Why not track the actions too?

To remediate issues, we delegate the actions required. Finally, dependencies are created among all segments of the project and these are influencing all actions taken.

Many PM Officers track actions in separate action logs, alongside meetings minutes or combination of both. This approach however leads to confusion because of decentralization of project controls.

In expanding classic RAID by adding Actions and amending the acronym to RAAID, we save PMO time and effort.

Aall the way to Z

Creating RAAID is just one of many customization of project methodology documentation for server migrations we at Stonegate use. Our documentation includes visual all-in-one Plan on a Page, extended PID, interactive Wave Plan, customized RASCI Matrix, standardize HLDs & LLDs, straight forward reporting and many more.