Raid alert issues software#

Should you spend time on a RAID analysis? In order not to loose overview we also track dependencies in a RAID spreadsheet. In complex projects there are many more dependencies. This is a very obvious case because every child knows that you can only paint a house once its built. If we take a house building project as example, we can’t paint a house before the actual construction is finished. Dependencies:Įxample of a dependency: Dependencies exist where one activity can’t start before another activity is completed. This is a simple example but now you understand why a RAID analysis is a good thing. You had ASSUMED that the client would bring their laptop.Īnd your client’s staff had assumed: we’ll have a great time there 🙂 And what you see is not good: Lots of happy people behind their desk, but no laptops! What a nightmare. The next day you arrive at the training site. The night before the event you wonder: “I hope everyone will bring their laptop“. Due to the lack of properly-sized meeting rooms the training takes place at a hotel outside of town.

Raid alert issues software#

Now imagine this scenario: You’ve organized a staff training for a client’s new software system. That’s a serious issue! You need to find a workaround for that … maybe carry out the work remotely. Which means: you can’t get into the country! Due to political tensions the Kwabala government has restricted entry from the US. You had planned several business trips to the site which is in – let’s say – Kwabala (a fictitious country). Imagine you are managing an overseas project. There are a ton of other risks that can harm your project, and it makes sense to spend some time gathering and analyzing project risks while you kick off a new project. That’s just one example of a project risk. The project can’t move on without this guy. A common risk has struck your project: You’ve run into a resource issue. Sorry I can’t support you this week.”ĭamn. They are having issues and I need to help.

He’s left a note: “Hi, I got called over to my other project. While wandering around you note that your key team member is missing. Imagine one day you come into the office. Risks, Assumptions, Issues and Dependencies

The RAID analysis is performed during the initiation phase, and the findings are documented in a RAID log and monitored over the course of a project. Its goal is to identify key risks (R), assumptions (A), issues (I) and dependencies (D) in a project. RAID analysis is a popular method in project management. dependencies – tasks being locked to each other.(false or hidden) assumptions – any assumptions your project is based upon.