Please enable JavaScript.

Coggle requires JavaScript to display documents.

PMI Agile Certified Practitioner Chapter 6. (Understanding Problems (How…

- - - - Variance Analysis
        
        The measure of how far apart things are
      - Lead time
        
        Measures how long something takes to go through out the process
      - Cycle time
        
        Is
        
        A subset of lead time that measures how long something takes through part of the process (Eg. From development to deployment)
        
        Project cycle time
        
        How long the entire project will ttake
      - Defects
        
        Catch and fix defects as quickly as possible to minimize re-work
    - - Tool to see or to think what might happen on the future.
    - - Limits can help us diagnose issues before they occur or provide guidelines for us to operate within.
        
        can use
        
        Kanban board
- - - - Stacked area graphs of cumulative project risk severity
        
        It makes easier to
        
        Interpret the overall risk status and trends of the project
        
        To construct them, you need to
        
        Plot severity scores for each risk on top of another
        
        And they show
        
        The cumulative severity profile
  - - - to calculate
        
        EVM(Expensive money value) = Risk Impact (Dollars) x Risk Probability(as a percentage)
  - - - to calculate
        
        Risk Severity = Risk probability x Risk impact
        
        is
        
        A rank from 1 to 3 (low, medium and high respectively) to each input and severity score is from 1 to 9. Inputs are rankins.
  - - - We need to
        
        Get the team members aligned with each other for team problem solving to be most effective.
    - - We need to
        
        Recanvas the team to make sure they are still on board with the approach that was chosen.
    - - We should use the team to
        
        Solve real problems only, not only to make decisions
    - - You need to consider
        
        Once you ask the team for solutions, make sure you follow through on
        executing them.
    - - The team should has
        
        First-hand knowledge of the problem and what types of actions are practical to solve it.
- - - - Identify the the problem as soon as possible.
  - - - 2. The later we are in the development cycle, the more stakeholders will be impacted by the defect.
      - 1. Over time more work may have been built on top of errors, so more work will need to be undone.
    - - Because of the cost of change curve.
  - - - The backlog of work that is caused by not doing regular clenup, maintance, and standarization while the prouct is being built.
      - An inflated cost of the change curve.
    - - Refactoring (Simplify & standardize the code)
  - - - So people feel conmfortable to admit their failures and mistakes, ask for help and the project can recover quickly.
    - - Reinforce the importance of asking for help.
        
        Avoiding catastrophies delays, as it is about protecting people feelings.
  - - - We are creatures of habit
      - We prefer to fail conservatively
        
        People tend to revert back to what they know, even if they are aware that it might not be the optimal approach.
      - We are inconsistent
        
        Most people are very inconsistent at following a process
      - We make mistakes
        
        Recognize that mistakes happen and to quickly recover from them
      - We prefer to invent rather than research
        
        Tendency to rely on inventing new ways of doing things, rather than researching options that have already been invented and reusing them.
    - - We are malleable
        
        this means
        
        we do have the ability to change and
        accept new ideas and approaches.
      - We take pride in our work
      - We are able to learn
      - We are good at looking around
      - Succes Strategies
        
        are
        
        strategies for overcoming the failure modes.
        
        Balance discipline with tolerance
        
        establishing a standard way of doing things
        and also building some capacity for tolerance and forgiveness into the approach
        
        Start with something concrete and tangible
        
        We solve a problem in our mind first, and then turn the solution into reality.
        
        Copy and alter
        
        It is often easier to modify a working design to fit our needs than to create something from nothing.
        
        Watch and listen
        
        We learn by watching others and listening to them.
        
        Support both concentration and communication
        
        Knowledge work requires both concentration and communication.