Upgrade

PMP - Agile Project Risks and Issues

Study

PMP - Agile Project Risks and Issues

Leave the first rating

1) Risk

2) Issue

3) Where can we address risks?

1) An uncertain event that has not occurred

2) A risk that has occurred

3) Daily standup
- Remember one our questions - are there any problems
or impediments to the team?
1 / 16
  Flashcards
 Learn
 Test
 Match

Created by
nwspencer1
Terms in this set (16)
Original
1) Risk

2) Issue

3) Where can we address risks?

1) An uncertain event that has not occurred

2) A risk that has occurred

3) Daily standup
- Remember one our questions - are there any problems or impediments to the team?
1) Technical Debt

2) Refactoring
1) Backlog of work caused by lack of regular clean up / standardization ("t's the result of
prioritizing speedy delivery over perfect code.")
- Refactoring solves technical debt; this time should be included in story point estimates

2) A technique to improve the quality of existing code.

- It works by applying a series of small steps, each of which changes the internal structure of
the code, while maintaining its external behavior.
Agile terms:

1) Lead time

2) Cycle time

3) Project cycle time

4) Productivity

5) Defect cycle time

6) Defect rate
1) Amount of a time for a user story to through the full process

2) Amount of time for a user story to go from one stage to the next (i.e. coding to testing)

3) Average amount of work the team can get done a project

4) Rate of efficiency at which work is done (i.e. amount of work done by a team member)

5) Amount of time from when defect is discovered to when it's fixed

- Longer the time = more expensive (code built on bad code)

5) How many defects make it to the customer

- Measures the frequency / increase in this = signal of problem in process
- Most expensive to fix (could mean harm to reputation/brand)
Variance analysis
The difference between what was planned and what was experienced
- Cost variance
- Schedule variance
- Other tracking items (KPIs; i.e. scope)

Agile is concerned usually with performance and risks

Goal = predict performance or problems

Causes of variance (agile)
1) Day to day differences
- good days/bad days = ups and downs
2) Special causes of variance
- team mate gets sick / power went out
1) Trend analysis in Agile

2) Lagging Metrics

3) Leading Metrics
1) Begin to see a trend/repetition in performance
- Based on time series data
- Compare same data (time, money, user stories, etc) in each time period
- ID relationships (i.e. a team member and how they're performing)
- Predict future performance

2) Measurements of experience

3 Predicting future metrics (performance, risks, etc) using lagging metrics

1) Working with risk-adjusted backlog

2) Backlog grooming for risk

1) Items with greatest value in risk move to top of the backlog
- Goal = attach risk items early
- Risk = anti value

2) Done by the PO; stories are ranked on business value and risk level
- Ranking is subjective based on gut feeling/preference
- ROI for project can be broken down per item

"ROI is assigned to each item in the backlog and compared to risk of the user story"
EVM agile
The worth of a risk event
· EVM = risk impact (money) x risk probability
· Can be put out tin a probability matrix

Can be cardinal (actual numbers) or ordinal (h/m/l)

How do we make continuous improvement through problem solving?
We're looking to solve problems before they even happen through:
1) Problem solving games (XP)
2) Daily standup
3) Iteration reviews/retrospective
4) Sprint planning sessions

The team should be involved and solving real problems

Not all problems can be solves; these should be worked around (stakeholder that just hates
your project
1) Lessons learned (agile)

2) Kaizen
1)
- Captured in each iteration
- Allows lessons to be applied to next iteration
- Lessons are repeated until they are learned

2) Japanese word meaning small change over time for the better
- Small incremental steps towards improvement
- Plan Do Check Act
- Plan, develop, evaluate, learn
Project Pre-Mortem
Problem solving game that aims to find failure points before they happen

-Imagine critical failure points

-Generate the reason for failure

-Consolidate list (prioritize)

-Create some responses to mitigate

-Revisit the plan

Product reviews
Done in retrospective and demos
- Deming's PDCA cycle = plan -> do -> check - act
- Product feedback loops and learning cycles (lessons learned/retrospective)

Feedback methods:
1) Prototypes
2) Simulations
3) Demos
Ways to collect data in retrospective:

1) Triple nickels

2) Color coded dots

3) Mad, sad, or glad

4) Satisfaction histogram

5) Team radar

6) Location strengths
7) Like to like
1) group spends five minutes on five ideas for 5 times

2) use color-coded dots to track if energy was high and low through the duration

3) track emotions throughout the timeline

4) bar chart

5) an assessment of performance improvement

6) what went well, or not well, in the iteration

7) compares reactions to different iteration event

5 whys
cause and effect exercise
- Small group
- Ask why five times
- The goal is to find root cause
- Create a fishbone diagram
1) what should we do at end of retrospective?

2) Short subject

3) SMART

4) Circle of questions

5) Retrospective planning games

1) Create an action plan

2) Short subject - keep, drop, add

3) specific, measurable, attainable, relevant, timely

4) each person asks a question on how to improve on of the issues, next person of the
circle's answers in a question

5) how to reach process improvement goals

How do we close out a retrospective?

1) Plus / Delta

2) Help, hindered, hypotheses

3) Return on time invested

4) Appreciation
1) to do more of and what to do less of

2) feedback on the retrospective

3) the team discuss the benefit of the retrospective

4) the team give appreciation to other team members

About us

 About Quizlet

 Careers

 Advertise with us

 Get the app

For Students

 Flashcards

 Learn

 Solutions

For teachers

 Live

 Checkpoint

 Blog

Resources

 Help centre

 Honour Code

 Community Guidelines

 Privacy

 Terms

 Ad and Cookie Policy

Language
DeutschEnglish (UK)English (USA)EspañolFrançais (FR)Français (QC/CA)Bahasa
IndonesiaItalianoNederlandspolskiPortuguês (BR)РусскийTürkçeУкраїнськаTiếng Việt 한국
어中文 (简体)中文 (繁體)日本語

© 2023 Quizlet, Inc.