You are on page 1of 8

ASSIGNMENT#3-SPM

Software Project Management

FYP Group Members

Muhammad Moaz Ahmad SP20-BCS-141-G4


Muhammad Ahsan SP20-BCS-103-G4
Ayesha Bibi SP20-BCS-152-G3
Mam Fareeha P

MAY 27, 2023


COMSATS UNIVERSITY ISLAMABAD, LAHORE CAMPUS
Question:
The assignment is based on your FYP. Give a detail analysis on your FYP to identify risk.

➢ List all possible risk,

➢ categories them,

➢ show the likelihood of risk,

➢ calculate impact of risk,

➢ and then give a tentative RMMM plan.

Note: You can use table given in lecture slides.

Answer:
Category:
PS = project size risk, BU = business risk, CU=Customer,
TE= Technology, DE= Development environment, ST= Staff

Impact:
Catastrophic
Critical
Marginal
Negligible

Possible Risk Category Likelihood Impact RMMM Plan

Inadequate system PS Moderate Critical Mitigation:


requirements Conduct thorough
requirements
gathering and
analysis.
Monitoring:
Regularly review
and validate
requirements with
stakeholders.
Management:
Implement a change
control process to
handle requirement

1 of 8
changes effectively.

Insufficient ST Moderate Critical Mitigation:


development expertise
Provide training and
resources to
enhance the team's
skills.

Monitoring:
Regularly assess the
team's performance
and address skill
gaps.

Management:
Consider
outsourcing or
hiring additional
expertise if required.

Technical constraints TE High Critical Mitigation:


and limitations Perform feasibility
studies to identify
potential limitations

Monitoring:
Regularly review
and update the
technical
constraints.

Management:
Explore
workarounds or
alternative
technologies when
necessary.

Poor data security and TE Moderate Critical Mitigation:


privacy Implement robust
security measures,
including encryption
and access control.

Monitoring:
Regularly conduct
security audits and

2 of 8
vulnerability
assessments.

Management: Keep
security protocols
up to date with
industry best
practices.

Integration challenges TE Moderate Critical Mitigation:


with existing systems Conduct thorough
integration testing
to identify and
resolve issues.

Monitoring:
Regularly monitor
system integrations
and address any
failures promptly.

Management: Use
compatible
technologies or
develop appropriate
interfaces.

User resistance to CU High Critical Mitigation:


adopting a new system Conduct
comprehensive user
training sessions.

Monitoring: Gather
user feedback and
address concerns or
difficulties.

Management:
Provide ongoing
user support and
ensure clear
communication of
system benefits.

Inadequate testing and TE Moderate Critical Mitigation:


quality assurance Implement
comprehensive
testing processes,

3 of 8
including unit,
integration, and
acceptance testing.

Monitoring:
Regularly review
and update the
testing strategies
and procedures.

Management:
Establish quality
assurance
checkpoints
throughout the
development.

Data loss or DE Low Critical Mitigation:


corruption Regularly back up
data using reliable
and secure
methods.

Monitoring:
Perform routine
data integrity
checks.

Management:
Implement data
recovery
mechanisms and
disaster recovery
plans.

Unavailability of PS Moderate Critical Mitigation: Identify


required resources resource
dependencies and
plan for
contingencies.
Monitoring:
Regularly assess
resource availability
and address any
shortages
proactively.

4 of 8
Management:
Consider alternative
resource options or
backup plans.

Scope creep and PS High Critical Mitigation: Clearly


changing requirements define and
document the
project scope.

Monitoring:
Conduct regular
scope reviews and
obtain stakeholder
agreement on any
changes.

Management:
Implement a formal
change control
process to manage
scope changes
effectively.

Unreliable third-party BU Low Critical Mitigation:


service providers Perform thorough
evaluations of
potential service
providers.

Monitoring:
Monitor service
provider
performance and
conduct periodic
reviews.

Management:
Maintain backups or
alternative options
in case of service
provider failure.

System performance TE Moderate Marginal Mitigation:


issues Regularly monitor
system performance
and conduct

5 of 8
performance testing

Monitoring:
Implement
monitoring tools
and alerts for
performance issues.

Management:
Optimize system
resources and
configurations as
necessary.

Legal and regulatory BU Low Marginal Mitigation: Stay


compliance challenges updated with
relevant regulations
and consult legal
experts.

Monitoring:
Regularly review
and assess
compliance
requirements.

Management:
Implement
compliance
measures and
processes to ensure
adherence.

Natural disasters PS Low Catastrophic Mitigation:


affecting system and Implement data
data backup and
recovery plans.

Monitoring:
Regularly review
and update disaster
response protocols.

Management:
Establish
procedures for data
restoration in case

6 of 8
of natural disasters.

Inadequate project PS High Catastrophic Mitigation:


management Implement effective
project
management
methodologies and
tools.

Monitoring:
Regularly review
project progress
and identify any
potential issues.

Management:
Establish clear roles,
responsibilities, and
communication
channels for
effective project
management.

7 of 8

You might also like