MB0049
Project plan
1502006224
1 | Page
MB0049
implementation review is to be carried out to identify the extent of project success and
document review outcomes.
Rajiv Kalia
1502006224
2 | Page
MB0049
there are different interests, different values, and different physical and emotional
characteristics present in the organisation.
A strong diversity management programme encourages the development of skills and
talents of the employees. It boosts the communication among employees and in the long
run, increases the productivity of the department.
Rules for network construction
Every activity must have a preceding and a succeeding event. An activity is numerically
represented by the pair of preceding and succeeding events. In the dinner project, for
instance, the activity send invitation is designated as (1-2).
Each event must have a distinct number. The number specified to an event can be
chosen in any way, provided this condition is fulfilled. In practice, yet, events are
numbered in the manner that the number at the head of the arrow is greater than
that at its tail.
There must not be any loops in the project network; a situation similar to the one
is not permissible.
The preceding and succeeding events are not same for the same than one activity.
This signifies that every activity is represented by a uniquely numbered arrow and
a situation depicted is not permissible.
Question (3):- What are key steps for effective risk management? Explain any
five risk identification techniques?
Answer:The first thing to understand in risk management is that it's an on-going activity. It's not about
identifying risks upfront and then forging ahead regardless. It's too easy to forget the risks once
the project is started and fail to recognize and raise new risks when the project is underway.
After the initial shock of seeing all the things that could go wrong, we had awareness. Half the
battle won. The other half, action didn't quite happen. Although the actions for each risk were
detailed, very few of them were followed up (the majority of the actions were the responsibility
of the client). When the risks started to impact on the project, the client wasn't happy. They had
accepted the risk, but hoped it would not surface and did not take any action to prevent it
occurring. Unfortunately when the risk did arise, it took more work to repair the damage done
than if preventative measures had been put in place. As the project manager, although I had
raised awareness, I hadn't continued to report on the risks so that the client was in a false state of
security assuming that the risk was no longer there.
Risk Assessment
Rajiv Kalia
1502006224
3 | Page
MB0049
The goal of risk assessment is to identify the risk factors that are a part of the activity being
undertaken. Basically, it's about working out what could go wrong. For example, the task could
be attending a client meeting. The possible risk factors would include
Availability of cabs
The more risk factors there are with a given task, the more that can go wrong.
Risk Evaluation
Once you have identified the risk factors, then you have to work out what impact they can have
on the task. Following the previous example, what would be the impact of arriving at the meeting
late?
In getting to our client meeting on time we could take the following actions
Rajiv Kalia
1502006224
4 | Page
MB0049
The idea is to avoid the risk altogether but if that's not possible, have plans in place that can
minimize the impact.
Risk Monitoring
Risk monitoring has two dimensions to it. Firstly it's about keeping an eye on the risks that
you've already identified to see if anything has changed, if the impact has increased or decrease,
which could require action. And secondly, to see if there are any new risks that have arisen
during the project.
For example, while we're on our way to the client meeting, we could be keeping an eye on the
time while listening to traffic reports for any potential traffic delays. The most important thing to
remember is that just because we have identified a risk upfront, that doesnt mean new ones
won't emerge.
Risk Reporting
Risk reporting is about ongoing awareness and the effectiveness of any actions or strategies
taken to contain or reduce risk. For example calling your colleagues about traffic delays or train
cancellations. The goal of risk reporting is to keep an eye on the existing risks to help any new
ones arising.
Following are the risk identification techniques:1. Brainstorming:- Brainstorming involves a group of people working together to identify
potential risks, causes, failure modes, hazards and criteria for decisions and/or options for
treatment. Brainstorming should stimulate and encourage free-flowing conversation amongst a
group of knowledgeable people without criticizing or rewarding ideas. It is one of the best and
most popular ways to identify both risks and key controls and is the basis for most risk
workshops.
2. Interviews:- During a structured interview, interviewees are asked a set of prepared questions
to encourage the interviewee to present their own perspective and thus identify risks. Structured
interviews are frequently used during consultation with key stakeholders when designing the risk
management framework. As an example, structured interviews are good to gauge risk appetite
and tolerance when developing risk appetite statements.
3. Checklists:- Checklists are pre-populated lists of hazards, risks or control failures that have
been developed usually from experience, either as a result of a previous risk assessment or as a
result
of
past
failures
or
incidents.
Rajiv Kalia
1502006224
5 | Page
MB0049
Auditors often prepare checklists of key controls to aid in their assessment of control
effectiveness and the internal control environment.
4. Structured What-if Technique (SWIFT):- This is a systematic, team based exercise,
where the facilitator utilizes a set of prompt words or phrases to stimulate participants to
identify risks. One organisation was looking at reducing service levels in a number of areas to
reduce its operating costs and SWIFT was used to analyze the impact of each reduced service
level. Risks were then identified and assessed. Where risks could not be reduced to a tolerable
level, the service level was maintained.
5. Scenario Analysis:- Closely related to SWIFT. Here a scenario is a short story or description
of a situation of how a future event or events might turn out or look like. For each scenario,
participants reflect and analyze the potential consequences and potential causes when analyzing
risk. Scenario analysis can be used to identify opportunities for fraud. For example, a scenario
could be A staff member has just admitted to defrauding or company of $50,000 over 8 years
through fictitious expense claimshow can this happen?
6. Fault Tree Analysis (FTA):- This method is similar to a form of creative thinking called
reverse brainstorming. This technique is used for identifying and analyzing factors that can
contribute to a specified undesired event (called the top event). Causal factors are then
identified and organized in a logical manner and represented pictorially in a tree diagram. For
example, if you want to improve customer service, state the objective in reverse e.g. How can
we really annoy our customers? and from this statement, use brainstorming to identify causes
that could annoy customers.
7. Bow Tie Analysis:- They say a picture is worth a thousand words and this method is a
perfect example. Bow tie analysis is a diagrammatic way of describing, linking and analyzing
the pathways of a risk from causes to effects/consequences. Unlike the risk register, there are no
numbers in this analysis i.e. there is no risk or control evaluation involved. This keeps the focus
on understanding the relationships between the causes, event and consequences.
8. Direct Observations:- Simply looking out for risks and being situational aware is not
included in ISO/IEC 31010 as a risk identification technique. This relatively simple technique is
used daily in the workplace by staff who may observe risky situations and hazards regularly. It is
also used by emergency services when attending to an emergency and is a form of dynamic risk
assessment. It is also heavily used by Workplace Health & Safety professionals during
inspections and audits. A risk aware culture and well trained staff will improve peoples ability to
observe potential risks and implement controls before the risk eventuates into an incident.
9. Incident Analysis:- Incidents are risks that have now occurred. Recording incidents in a
register, conducting root cause analysis and periodically running some trend analysis reports to
analyze incidents, can potentially enable new risks to be identified. In addition, a high frequency
of like incidents can be a lead risk indicator to a potentially larger problem.
Rajiv Kalia
1502006224
6 | Page
MB0049
Procurement Process
A Procurement Management Process, or Procurement Process, is a method by which items are
purchased from external suppliers. The procurement management process involves managing the
ordering, receipt, review and approval of items from suppliers. A procurement process also
specifies how the supplier relationships will be managed, to ensure a high level of service is
received. This is a critical task in Procurement Management. In essence, the procurement process
helps you "get what you have paid for".
You need to implement a Procurement Process any time you want to buy items from external
suppliers. By using this Procurement Management Process, you can ensure that the items
provided meet your need. It also helps you manage the supplier relationship, ensuring that any
issues are resolved quickly. By implementing a Procurement Process, you can ensure you get the
maximum value from your supplier relationship.
Project teams responsibilities in project execution
The project team members are expected to assist in the management of the project as well; albeit,
at a more functional level. The critical project management elements for the project team to
provide assistance with include:
Performance monitoring: - Implement an execution plan to measure the actual
performance as compared to planned performance. For example, the actual project
Rajiv Kalia
1502006224
7 | Page
MB0049
Rajiv Kalia
1502006224
8 | Page
MB0049
Question (5):- What is the quality planning? Explain the inputs, tools and
techniques and outcomes of quality planning?
Answer:Quality planning is the process of identifying the quality standards that are related to the project
and determining how to these standards can be achieved. It is one of the significant processes of
project planning and should be performed on a continuous basis and in parallel with the other
project planning processes.
A good quality planning process starts with a clear definition of the goals of the project. What is
the product or deliverable likely to achieve? What does the product look like? What functions
will it perform? How do you evaluate customer satisfaction? What determines the success of a
project?
Answering these questions will help you in identifying and defining quality goals. It will also
allow you to discuss the approach and plans required to accomplish those goals. This includes
measuring the risks to success, setting high standards, documenting everything, and defining the
methods and tests to attain, control, forecast and validate success. You should make sure that you
include quality management tasks in the project plan and delegate the tasks to work groups
and/or individuals who will report and track quality metrics.
For example, the desired management quality may need cost or schedule adjustments, or the
desired product quality may need a detailed risk analysis of an identified problem. Before ISO
9000 Series was developed, the activities mentioned here as quality planning were broadly
considered as part of quality assurance.
Rajiv Kalia
Quality policy
Quality policy refers to the overall intentions and direction of an
organisation pertaining to quality, as formally expressed by top
management.
Scope statement
The scope statement comprises the key objectives of the project that are
needed by different stakeholders.
Product description
It includes the details of technical issues and other concerns which may
influence quality planning.
Standards and regulations
The project management team must acknowledge all the relevant
standards or regulations that may influence the project.
1502006224
9 | Page
MB0049
Benefit/cost analysis
The quality planning process should acknowledge benefit/cost trade-offs.
The benefits should cover higher productivity, lower cost and higher
customer satisfaction.
Benchmarking
In this, we compare actual or planned project practices to practices of
other projects to produce ideas for improvement and to find a suitable
standard to measure performance.
Flowcharting
It is a diagram that depicts how different elements of a system relate to
each other.
Design of experiments
It is an analytical technique that helps identifying which variables affect
the overall income the most.
1502006224
10 | P a g e
MB0049
Rajiv Kalia
1502006224
11 | P a g e
MB0049
Clarifying goals
Tracking progress
Reporting results
Rajiv Kalia
1502006224
12 | P a g e