?

Risk
Missing Information

k New requirements
Ris

Poor data quality

Risk
 Agile Risk
Management
Navigating uncertainties for Project Success

By
A. Akhila
22031D2501
 Introduction

• What is the Risk?

• Risk is an uncertain event that could the
negative impact on the project.
• Risk Management is defined as the process
of managing the risks
 Generic Risk Management in Agile
Generic risk management in Agile refers to the systematic process of
identifying, assessing, and mitigating risks across all aspects of a project,
ensuring a proactive and adaptable approach to uncertainties.

Key Components
Continuous
Monitoring
Regularly
Mitigating
review and
Strategies
update risk
Collaborate on
Risk assessments.
strategies to
Assessment
address high-
Evaluate the
priority risks
Risk impact and
Identification likelihood of
Actively involve identified
the team in risks
identifying
potential risks.
 Agile Key Principles to Address Risks

• Adaptability - Emphasizes flexibility to respond to evolving project

requirements.
• Transparency - Expose everything we are doing so we can see risks
easily.
• Collaborative Planning - Harness the knowledge of the entire and
see more risks.
• Customer involvement - Mitigate customer risk by involving them
throughout the life cycle
 Risk management

Project Management Life Cycle(PMLC):

Project
Mgmt.
Life Initiate Plan Execute Close
Cycle
Initial Approved Estimates
Business Business
recruitment Estimates
SDLC: Case

Analysis Design Build Test

In our PMLC - usually once to initiate the project, then

revisit and update the risks after planning.
 Risk management in Agile

Project Management Life Cycle(PMLC):

Agile looks for risks thoughout the life cycle
Project
Mgmt. Initiate Plan Execute Close
Life
Cycle Initial Approved Estimates
Business Business
Case
recruitment Estimates

SDLC: Analysis Design Build Test

Look for Risk Look for

Risk
Look for
Risk Look for Look for
Look for Risk Risk
Risk
 In the Generic Risk Management

• Every project faces a set of common risks: employee turnover, new

requirements, work disruption, and so forth. These risks act as a
multiplier on your estimates, doubling or tripling the amount of time
it takes to finish your work.
• Generic risk management principles applicable in Agile methodology
focus on adaptability, continuous assessment, and collaboration
 Project Specific Risks

• Using the XP practices and applying risk multipliers will

enhance the risk containment in software development
projects and these are common to all projects.
• The generic risk multipliers include the normal risks of a
flawed release plan, ordinary requirements growth, and
employee turnover. In addition to these risks, you
probably face some that are specific to your project.
• To manage these, create a risk census that is, a list of the
risks your project faces that focuses on your project’s
unique risks.
 Project Specific Risks
• [DeMarco & Lister 2003] suggest starting work on your census by brainstorming
catastrophes.
• Gather the whole team and hand out index cards. Remind team members that
during this exercise, negative thinking is not only OK, it’s necessary. Ask them to
consider ways in which the project could fail. Write several questions on the board:
1. What about the project keeps you up at night?
2. Imagine it’s a year after the project’s disastrous failure and you’re being interviewed
about What went wrong. What happened?
3. Imagine your best dreams for the project, then write down the opposite.
4. How could the project fail without anyone being at fault?
5. How could the project fail if it were the stakeholders’ faults? The customers’ faults?
Testers? Programmers? Management? Your fault? Etc.
6. How could the project succeed but leave one specific stakeholder unsatisfied or
angry?

• Write your answers on the cards, then read them aloud to inspire further thoughts.
 Example to Project-Specific Risks
Identifying Catastrophes and Scenarios

• Example: Online Application Development

• Catastrophe: Extended Downtime
• Scenario: Excessively High Demand
• Root Causes: Denial of Service Attack, More
Popular Than Expected

Brainstorming Risks as a Team

Team Brainstorming Session
• Encourage Team Collaboration
• Cross-Sectional Team Approach
• Identify Potential Risks in Online Application Development
Risk Assessment Parameters
• Estimated Probability: High, Medium, Low
• Impact on Project: Dollars Lost, Days
Delayed, Project Cancellation
• Informed Decision Making

Discarding Unimportant Risks

• Prioritization is Key
• Discard Unlikely Risks with Low Impact
• Generic Risk Multiplier Addresses Less
Significant Risks
 Risk Management Strategies

• Options for Addressing Risks

1. Avoidance 2. Containment 3. Mitigation

Steering Lessening
Preventing
clear of the severity
the escalation
identified of problems. or impact of
risks. challenges.

• Flexibility to Combine Actions based on the nature of challenge

• Comprehensive Approach to Addressing Potential Challenges
 Making a Release Commitment

• Making a release commitment in

Agile means promising to deliver a
specific set of features or a product
within a certain timeframe.
• It's crucial because it helps teams
plan, set expectations, and work
towards a common goal.
BUSINSS INFOGRAPHICS
Key Steps:
Risk Identification
Actively involve the team in identifying
potential risks.

Continuous
Improvement
Regularly review and update Risk Analysis
risk assessments. Evaluate the impact and
likelihood of identified risks

Collaboration Risk Mitigation

Teams working closely
Collaborate on strategies to
together, fostering open
address high-priority risks
communication and quick
responses to challenges.
 Importance of Release Commitment

Predictability: Enables predictability in

project timelines and deliveries.
Stakeholder Communication: Facilitates
clear communication with stakeholders
about what to expect and when.
Team Alignment: Aligns the team's
efforts, ensuring everyone is working
towards the same objectives.
 Success Over Schedule

• Prioritizing Success Metrics

• Balancing Quality and Timeliness
• Emphasizing Customer Value
• Examples of Successful Agile Releases
• Agile Principles: Responding to Change
 When Your Commitment Isn't Good Enough?

• It's crucial to identifying Challenges

and reasons for Commitment
Shortfalls
• This could be due to various reasons
such as unexpected issues, changes
in requirements, resource
constraints
• Adjusting Commitments Mid-Project
 Results

• Measuring Success
• Delivering Value
• Customer Satisfaction
• Key performance indicators and team/stakeholder feedback play a
vital role in assessing the outcomes of our release commitments.
 Contradiction
• Balancing commitment and flexibility is a constant challenge in Agile.
• Managing Expectations
• Adapting to Change
• Challenges Faced in Balancing Commitments
 Alternatives

• Flexible Planning Models

• Continuous Deployment
• Lean Principles
• Hybrid Approaches
• Choosing the Right Approach for Your Team
Navigating Success with Agile Risk Management

• Proactive Risk Mitigation: Identifying and addressing risks proactively

ensures a smoother project journey.
• Adaptability in the Face of Change: Agile's flexibility allows for effective
adaptation to unexpected challenges and changes.
• Continuous Improvement: Iterative feedback loops drive continuous
improvement, refining risk management strategies for future projects.
• Collaboration Fuels Success.
Thank You All!