RAID is a very powerful and most effective Project Management tool that you can create for your project. Good to create a RAID log at the start of each project so you can track anything impacting you now or in future.

1. Guidelines for RAID
Management
1
Risk
• Identify
them to
protect
yourself
Assumption
• Identify
them to
make
decisions
Issue
• Identify
them to
solve real
problems
Dependency
• Identify
them to
remove
impediments

2. 2
WHY RAID
• Easy & Effective
• Structured way of Project Planning
• One Central Place rather than four different documents
• Catalogue for all the issues Identified throughout the Life Cycle of the Project
• Monitoring Tool for Impacts (Present & Future)
• Action Oriented & Endorsing Results
• Acts as Source of Accountability, Ownership & Responsibility
**Keep your log Up to Date

3. 3
CONTENTS
• RAID
• Risk Management Across Products
• Assumption Management Across Products
• Issue Management Across Products
• Dependency Management Across Products
• Types of Dependency Relationships

4. RAID (Risk, Assumption, Issue, Dependency)
4
RAID
TO BE TRACKED
(Possible Project Factors)
TO BE MANAGED
(Existing, known Project Factors)THREATSRELIANCES
Dependency exists when an
output from one piece of
work or project is needed as
mandatory input for another
project or piece of work
Anything which arises on your project
which you have to deal with in order to
ensure your project runs smoothly. Issue
differs from risks in that they exist as a
problem today unlike risks which might turn
into issues in the future
Specific event which might occur and thus
have a positive or negative impact on your
project. Each risk will have probability
associated of occurrence along with an
impact on your project if it does
materialize
Something we set as true to
enable us to proceed with our
project. Typically this happens
during the planning and
estimation phase of the
project
RISK ISSUE
ASSUMPTION DEPENDENCY

5. Risk Management Across Products
5
• Mitigate
• Contingent
• Update
Register
• Risk Impact
• Probability
• Identify Risk
• Record Risk
REGISTER EVALUATE
RESPONDCLOSE
Risk Management is a continual process, not an independent event

6. Assumption Management Across Products
6
Identify &
Challenge
Assess Incorporate Control Review
Activities
• Examine & verify
assumptions to get
as close to certainty
as possible
• Evaluate
assumptions from a
long term
perspective.
• Impact of incorrect
assumptions must
be determined.
• Incorporate
assumptions into
the relevant portion
of project plan.
• Track and monitor
assumptions
throughout the
project to ensure
the constant state of
readiness.
• Review assumptions
as part of ‘post
project’ review
process to evaluate
all steps taken for
identification,
assessment,
incorporation and
control.
Assumption Management has a huge impact on decision making

7. Issue Management Across Products
7
Issue Management is all about solving real problems
Identification
Analysis
EvaluationAction
Monitor
&
Review
Research
Judgement &
Priority setting
Strategy
SelectionImplementation
Performance
Evaluation

8. Dependency Management Across Products
Identify Agree Plan Validate
Monitor
& Control
Activities
• Identify dependency
during Project
Planning
• Facilitate in
identifying External
& Internal
Dependencies
• Host a workshop
with your team and
decide what and
when do you need
from external
• Contact the External
party
• Ensure they
understand what
and when you need.
• If they are able to
deliver Great! If not
negotiate
• Write down what
has been agreed.
• Record each
dependencies as
miles stones and
give a reference
number for unique
identification.
• Make sure that
dependency is
linked into the rest
of schedule so if
does slip impact
would be known.
• Have a baseline date
• Manage the series
of dependencies and
their impacts on
project
• Rate according to
the impact they
could have
• Monitor it on a
regular basis
• Contact the external
party if they are still
on track to deliver
the dependency on
agreed date
8
Communication

9. Types of Dependency Relationships
9
Type Examples Descriptions
Finish to Start(FS) The dependent task (B) cannot begin
until the task that it depends on (A) is
complete.
Start to Start (SS) The dependent task (B) cannot begin
until the task that it depends on (A)
begins.
Finish to Finish (FF) The dependent task (B) cannot be
completed until the task that it depends
on (A) is completed.
Start to Finish (SF) The dependent task (B) cannot be
completed until the task that it depends
on (A) begins.
A
B
A
B
A
B
A
B

10. 10