Please enable JavaScript.

Coggle requires JavaScript to display documents.

PMI Agile Certified Practitioner Chapter 2 (Value Driven Delivery (is (A…

- - - - are
        
        Deliver Value Early
        
        it means
        
        aim to deliver the highest-value portions of the project as soon as possible
        
        Minimize Waste
        
        it means
        
        minimizing waste and other nonvalue-adding activities
  - - - finacial assesment Metrics
        
        like
        
        Net Present Value
        
        The present value of a revenue stream (income minus costs)
        over a series of time periods
        
        Internal Rate of Return
        
        The discount rate at which the project inflows (revenues)
        and project outflows (costs) are equal.
        
        Return on Investment (ROI)
        
        has
        
        Present Value
        
        a way of calculating the value of a future amount in today's terms
        
        measures
        
        The profitability of an investment
        
        The ratio of the benefits received from an investment
        to the money invested in it, expressed as a percentage :checkered_flag:
        
        Used to
        
        assess the value of a project
      - Earned Value Management (EVM)
        
        used
        
        to monitor the delivery of value while a project is in progress
      - ussusaly assessed
        
        in financial terms
  - - - Adaptability
      - Risk
      - Visibility
      - Business Value
- - - - deliverables
      - ranking the value of change requests against the remaining work items
      - reprioritizing the backlog
  - - - Focuses on
        
        Fit for business purpose
      - is used primarily in the United Kingdom and other areas of Europe
    - - Early termination options
      - Flexibility in making changes
      - Fixed-price contract that includes time and materials for additional work
      - 'change for free' option clause
        
        can only use this clause if they work with the team on every iteration
        
        the client has the ability to request a new feature if he drops another feature previously requested
      - 'Money for nothing' option clause
        
        allows the customer to terminate the project early when they feel there is no longer sufficient ROI in the backlog to warrant further iterations.
      - The product stays efficient without code bloat (for software projects) or unnecessary features
    - - both parties share some of the risk and reward associated with schedule variance
        
        if the supplier delivers on time, they get paid for the hours worked at their standard rate.
        
        If they deliver early, they get paid for fewer hours, but at a higher rate
        
        if the supplier delivers late, they will get paid for more hours, but at a lower rate
    - - mitigate the risks of underestimating or overestimating a chunk of work
      - Reducing the scope and costs involved in the work being estimated
      - breaks down the projects statements of work (SOW) into individual work packages, each with its own fixed price.
        
        allows the customer to reprioritize the remaining work based on evolving costs
        
        Gives the supplier the ability to update their costs as new details emerge
        
        removes the need for the supplier to build excess contingency funds into the project cost
        
        The changes are then localized to small components (the work packages)
        
        If extra funding is required, it is easy to identify the need and justify it.
    - - Different types of agile contracts can be pieced together to create a customized contract
- - - - Doing Tests
        
        .
      - Writing Code
        
        The code pass all the tests
  - - - Distill
        
        We get the tests ready to be entered into our acceptance test tool
      - Develop
        
        During development, the tests are hooked up to the code and the acceptance tests are run
      - Discuss
        
        We ask the product owner questions that are designed to gather acceptance criteria
      - Demo
        
        The team does exploratory testing using the automated acceptance testing scripts and demos the software.
  - - - Test tools
        
        Unit tests are run to ensure that the basic functionality operates
      - Scheduler or trigger
        
        Builds might be launched every time the system detects a change to the source code.
      - Build tools:
        
        Most integrated development environments (IDE) serve as a build tool to compile the code.
      - Notifications
        
        If a build fails, the team needs to be notified so they can correct the build as soon as possible.
      - Source code control system
        
        This is the software that performs version control
  - - - Release
        
        Iteration demo
        
        Acceptance test
        
        Stand-up meeting
        
        Costumer collaboration
        
        Unit Test
        
        2 more items...
        
        This provides feedback on whether
        the team's designs are correct and the customer's objectives are being met
        
        The team will validate who is working on what and when the code should be done and ready to integrate.
        
        The customer and verify that they are building the right product so far.
        
        At the end of each release, the customer reviews the deliverable to verify
- - - - How the economic models of agile projects work
    - - are
        
        Rate of progress
        
        How much work is being accepted by the product owner
        
        Remainingwork
        
        How much work is left in the backlog
        
        Likely completion date
        
        How much work is left to do divided by the current rate of progress
        
        Likely costs remaining
        
        The salaray burn rate for the team multiplied by the remaning weeks left
    - - PMBOK Guide Risk Managment Process
        
        is
        
        Plan risk mangament
        
        Identify risks
        
        Perform qualitative risk analysis
        
        Perform quantitative risk analysis
        
        Plan risk responses
        
        5.Control risks
    - - Two approaches
        
        Weave it into regular development work
        
        Undertake the regulatory after creating product
    - - Work on the items that yield the highest value to the customer first.
    - - Simple schemes
        
        Label items
      - Monopoly Money
        
        Prioritizing business features
      - 100-Point Method
        
        Vote for most important features
      - Dot Voting or Multi - Voting
        
        Collective wisdom emerges through individual priorities
      - Kano Analysis
        
        Classify customer preferences
      - MoSCoW
        
        Must have
        
        Should have
        
        Could Have
        
        Would like to have
      - Requirements Prioritization model
        
        Features are rated on a scale of 1 (lowest) to 9 (highest)
    - - Understanding the priority of features
    - - The team regulary deploys working increments of the product
    - - Package of functionality that is complete enough to be useful
- - - - implemented through
        
        Task/Kanban Boards
        
        with
        
        No WIP Limit
        
        WIP Limit Too Low
        
        WIP Limit Just Right
        
        Cumulative Flow Diagrams
        
        can be used
        
        Littles's Law
        
        Bootlenecks and the Theory of Constrains